You can check your own Technical Specifications!

WoollyBee · Post by **WoollyBee** » February 14th, 2013, 4:25 am

Just joined; going to be a DPL...

This is going to be SO awesome! Thanks!

ArielX · Post by **ArielX** » March 17th, 2013, 9:13 am

I have an idea, and it's a shame that I don't know anything about programming or I'd try this myself: what about a program like the Checker or maybe just writing a plugin for Audacity, that can take any file people have recorded and automatically converts it to the specifications required? Checker does a nice job checking the specs of files, but imagine if you'd just open a program that takes any file someone has recorded, and converts it to the 128 kbps mono -0dBs spec automatically? This would facilitate the process for everybody, and there'd be another dedicated program that all LibriVox users would be making use of. No more fussing, trials and errors trying to get the audio file to standard--the program would do it automatically. Who should I run this by?

Post by **TriciaG** » March 17th, 2013, 9:24 am

There are some problems with that.

1. Plosives. If you have plosives, they cannot be cleaned up automatically. You must readjust your mic, etc., to prevent them.

2. Background noise. Some doesn't automatically clean up well, so it's best to prevent it.

3. Quality. If you export at 32 kbps rather than 128 and have something adjust it to 128, your quality is going to stink because you're going from poor quality to start with.

There are other issues like that as well.

That said, there is Auphonic.com, which does a good job at some of those corrections that CAN be done automatically.

ppcunningham · Post by **ppcunningham** » March 17th, 2013, 10:02 am

You can also use "chains" in Audacity to automate several jobs. ( go to File, Edit Chain) It's basically an automatic que, where you set up a list of things you want it to run, with the correct specs. Then when you are ready, you apply the chain to the file.

My chain for instance, consists of:
Normalize at -3
Compress
Equalize
Normalize again at -3 (from advice from sound editors)
Bass Boost at 8 ( since I am female and have a cheap mic )

I usually noise clean first and check for clipping, but I suppose I could add that to the chain as well.
Afterwards, I run it through Checker (which is AWESOME, by the way) to check the sound level, and Amplify + or - as necessary. This has given me very good results, and I don't have to try and remember how I did it "last time". This is very helpful when you have to go back and edit a finished file due to PL notes. You can run the chain on just the bits you've fixed, so they match the rest of the file.

Patti

RuthieG · Post by **RuthieG** » March 17th, 2013, 10:48 am

I must admit that I am a bit of a dinosaur, but my regime - which comprises:

Analyze | Plot Spectrum to get the precise frequencies for the Single Band Parametric
2 x Single Band Parametric
Noise Clean
Compress
Noise Clean

takes about 2 minutes to do. Why would I automate it, even if I could? (I can't because those precise frequencies can vary between 134-137 and between 264-269.) I'd have to Effect | Noise Removal |Get Noise Profile separately anyway, as the profile isn't saved (and it's a good thing it isn't, because I don't know many people whose noise is always identical).

Ruth

ppcunningham · Post by **ppcunningham** » March 17th, 2013, 8:37 pm

RuthieG wrote:
Analyze | Plot Spectrum to get the precise frequencies for the Single Band Parametric

I had to look that one up -
I couldn't figure out why you would use it.

The article talked about mains hum - which I guess I don't have, because my section of town has no overhead wires.

Good to know about though - might be useful later.

P.

RuthieG · Post by **RuthieG** » March 18th, 2013, 2:44 am

The article talked about mains hum - which I guess I don't have, because my section of town has no overhead wires.

A goodly percentage of readers here have mains hum to a greater or lesser extent - I can tell if someone is in the USA just by looking at their waveform, because the USA uses an electrical mains frequency of 60 Hz, while in Europe and many other places it is 50 Hz. It doesn't just come from overhead wires, but from anything electrical in the vicinity. Often readers who record on a laptop can get rid of it entirely just by recording on battery power.

I don't have mains hum, but my computer (quiet though it is) does produce noise from the fan at two specific frequencies (one is the harmonic of the other) both of them at frequencies used by the voice. Single Band Parametric whips out those very precise frequencies without affecting my voice at all, which is why I use it. Notch Filter does the same thing, but has only limited settings.

Ruth

ppcunningham · Post by **ppcunningham** » March 18th, 2013, 7:42 am

Is there a video?

RuthieG · Post by **RuthieG** » March 18th, 2013, 8:42 am

I don't know, to be honest. Phil (philchenevert) will be able to tell you if he has made one.

SBP is also brilliant for taking out particularly sibilant esses. You can see in Plot | Analyze Spectrum the very obvious spike in the 3000s Hz and take it out, leaving a perfect s.

Ruth

ArielX · Post by **ArielX** » March 30th, 2013, 7:17 am

Many thanks for the replies, everyone; great points made. ppcunningham: the chain idea is a great one! will try that. I just figured there's got to be a way to automate some of the processes in the path from our mouths to the resulting audio files, for everyone's sake--and yes, my own! Even though I'm learning about audio production on my own, there's a lot I've still no idea about, and the technical aspects are always a challenge for me. RuthieG, I think I'm going to camp at your feet, my dear--there's alot I can learn from you!
It took me quite a few tries to get my first introductory file polished to standard--I believe RuthieG will attest to this since, if memory serves, she was the kind person who advised me if it was up to snuff, and did so a few times (til I got it right; for your patience, I thank you). I then realized, if I had such a tough time with it, and I've been learning audio production, I can imagine how much more frustrating the process must be for folks just coming into it, handling the processes on both ends of the mike (the performance, and the production). Hence the suggestion for some automation facilitating the process, where possible. Besides, a little automation never hurt anyone. Wait--I don't know that for sure....

Post by **smijen** » June 18th, 2013, 4:03 am

Just an FYI for those who haven't seen it - an updated version of checker was posted about a month ago:
-now gives a warning if volume is too loud (rather than just too quiet)
-changed DC bias threshold so it won't give a warning if DC bias is tiny
-background noise checker is disabled by default
-fixed/change wording on several help files
-other stuff too; see version history if interested

And as always, it will remember your tab preference and open accordingly. So if you like the "Information" tab rather than the "Validation" tab, just stay there and it will open there next time.

Post by **TriciaG** » June 18th, 2013, 5:42 am

YAY! Thanks for letting us know!

I've updated the Wiki page.

Post by **smijen** » August 18th, 2013, 7:20 pm

smijen wrote:Just an FYI for those who haven't seen it - an updated version of checker was posted about a month ago:
-background noise checker is disabled by default

For anyone who is using an old version, please do download the new one, and leave the background noise thing-y disabled if you are a newbie. It's there for the truly geeky who want some numbers to guide their post-processing, but checking background noise absolutely requires a human ear. You can't just look at a number and know if the background noise is OK.

Archeanassa · Post by **Archeanassa** » May 24th, 2016, 10:36 am

Hello. I'm trying to install the Checker but everytime I get this message:

http://prntscr.com/b7xqu3

can anyone help me please? why is this happening.

Archeanassa · Post by **Archeanassa** » May 24th, 2016, 10:56 am

I tried to install again the Checker and now I got this message:

http://prntscr.com/b7y0y9

I'm not lucky with this application....