I have an audiobook project I’m working on, and I keep having trouble with ACX’s requirement that the files be at least 192kbps. When the engineer sends them to me (by posting them in a Dropbox directory) he told me the first batch was encoded at 192kbps, but when I tried to upload them, ACX said they weren’t high enough. I looked at them in iTunes and they showed up as 112-114.
He sent me a new set of files encoded at 256, but these show up as 177-181. (I tried uploading a chapter to ACX before I put them in iTunes, in case iTunes was doing some kind of compression I wasn’t aware of).
He can’t figure out what’s going on–they’re fine on his end, and compressed on mine. I tried uploading them from both my Mac and my PC, and got the same problem. The file size on his end and my end are the same (for example, Chapter 1 is 10.9 MB for us both). Originally I downloaded the files as one big .zip file, but I tried downloading individual files and get the same result.
Does the bit rate change when they’re in a zip file? If not, then have him zip them before uploading (you can zip individual files). That said, I’m skeptical that Dropbox is changing file contents.
If the files really did get reencoded to a different bit rate, the size of the file would be different. Check the size of your files and compare them with the size of the sender’s files.
there are a few different ways to encode an MP3 file. “constant bit rate” means just that, it uses a constant number of bits per second. So, an MP3 encoded at 192 kb/s constant-bit-rate will use 192,000 bits for every second of music, period. “variable bit rate” means the encoder will use a different number of bits per second depending on what’s required to meet the desired sound quality. “average bit rate” means the encoder will target an average bit rate, but may go higher or lower depending on how complex the segment of music is.
some older tools for working with MP3 files can get confused with files using VBR or ABR. if they look at a particular “frame” within the file, they might see a lower number than desired.
Assuming you both have access to gmail have him send you a chunk that’s 25 megs or less so you can use gmail for the transfer and test. I would say chances are 99.99% it’s not dropbox but how the different programs are reading and writing bit rates. Have you tried a different media play or assembly program to see what it says? What does simply right clicking on the file “properties” then “details” in windows explorer say about the file?
Does that mean my system is choking on it too? Because as I said, when I import it into iTunes (the only way I know to be able to look at the bit rate), it shows up as 177, not 256.
Well, it didn’t work on the Mac (which is what I’m primarily using). I will check it on the PC.
However, the engineer sent me some new files (encoded at 320kbps this time) and, go figure, they didn’t change at all. I got them at 320, and ACX accepted them, so I think I’m good to go.
Whatever transfer app you’re using, email or FTP etc., it may be detecting the type of file and re-encoding it to save bandwidth (without asking first). Similar to how MS Outlook will ask for a ‘quality’ setting when you attach picture files (.jpg, .bmp etc.) to email messages.
A simple way to check would be to change the file’s three letter extension before sending it. Instead of soundfile.mp3 change it to soundfile.old then the app won’t recognize it (you have to change it back before trying to open it)…
If the file size is the same, then obviously it’s not being re-encoded. I’m guessing the file is encoded as VBR (variable bit rate); when you use VBR, you specify the maximum and minimum bit rate, and the encoder varies the actual bit rate as needed. I’m guessing one software/OS is reporting the maximum bit rate (256 is typical) and the other is reporting the average actual bit rate (177).
I think this is the correct answer. If the file size is the same then it’s likely the same file. And I don’t think Dropbox is messing with it, re-encoding someone’s file would pretty much defeat the purpose of cloud storage.
Have the author ensure it’s a constant bitrate file because ACX specifically asks for that.
