History: I was PMing with someone about something else entirely, when I suddenly thought (and typed) "wouldn't it be neat if I could just get a listing of file features, with problems flagged." I don't think everyone would need to use it all the time, it doesn't need to be tied into the uploader or anything, but I know I often wonder how my Db/volume looks, and peek into the validator to compare ... and I think it might be quite helpful for newcomers to have a very userfriendly-but-automated way to check themselves, if they're a bit self-conscious about launching into a sample. It'd be neat if people could check their own sound levels after changing mics or computers and so on, even if they've never been very clued up about what a "loud" soundwave should look like (and without being clippingly loud, either.) Of course people will still be encouraged to ask for help whenever they need it! This is an extra to the current processes. I floated this idea by a few other folks, none of whom told me I'm insane, and some of whom have made helpful amendments, incorporated below, so I'm putting this out to tender.
Spec: LibriVox recorders will upload an MP3 in a similar way to how we use the Uploader at the moment. Once the file is uploaded, a summary page will appear, which shows relevant tech. stats.
* bit rate
* sample rate
* a rough filename check (which would simply check for capital letters, spaces and evil characters)
* Db average
* visual readout on the whole file (or mebbe just the first X mins) - a graphic of the soundwaves - with some kind of two-word interpretation as to whether this is likely to be too quiet or loud or within listener-tolerance levels (aka. Good!)
The files are only stored temporarily, and can be deleted as soon as the summary is produced, or as convenient.
Design thoughts: needs to be completely different to the uploader. Because the feedback text is 'canned', it can also be translated into any language people are willing to port to. The design needs to accomodate this, and also have a language-switcher. A "friendly feel" is really important, along with a LOT of tool-tips & links to help features. Some sort of "dashboard / control panel" look would be cool (little analog dials! Brass gauges! Steampunk me, baby!)
Here's how it shouldn't look ... but I wanted to do SOMETHING to get across the ideas, esp. the visual chart at the bottom.
And here's a too quiet one. Yes, I know it's seriously un-colour-blind people friendly, but it's a proof of concept.
Discussion welcomed ... other features welcomed ... people who can actually make this happen especially welcome! Initially, we may have to work out some kind of sandbox somewhere off LibriVox, but hopefully once it works and is roadtested, it'd be integrated somewhere here. "Preview / Test your file".
I'd appreciate any help! And if we end up getting two tools developed, then that's fine too -- they might suit different platforms, or be blendable in some way.
. So go with what you're comfortable with. PHP would certainly be a good choice - the catalog system is PHP, and it represents the future for the LibriVox backend. I'd treat the validator as legacy code!