Roj
05-15-2004, 02:24 PM
I hadn't noticed this before, so I thought I'd relate it here.
I use EncSpot Basic 2.0 to have a look at the encoders used in creating various files. Yes, I know it has its quirks and inaccuracies. This one is funny.
I ripped a bunch of tracks from various CDs for a project I'm working on for my car and I set CDex to encode on the fly at 192 CBR q=0. I also set it to not create any tags (I use the excellent MP3Tag to do that). So, here I am with a folder full of files and I run EncSpot against it out of curiosity. It reports a bitrate of *191*. That's right fellow illustrious chilibeans, not *192*. For each and every file. I'm puzzled. I rip and encode at various variations in quality of 192 CBR and get the same results out of EncSpot each time. I check encodes I downloaded known to be 192 LAME 3.92 (which is what I'm using in CDex) and they are 192.
Then I had a brainwave. What's the obvious difference? I added a tag to my freshly encoded files.
Voila!
EncSpot now sees them as 192.
Wazzup wid DAT???
I use EncSpot Basic 2.0 to have a look at the encoders used in creating various files. Yes, I know it has its quirks and inaccuracies. This one is funny.
I ripped a bunch of tracks from various CDs for a project I'm working on for my car and I set CDex to encode on the fly at 192 CBR q=0. I also set it to not create any tags (I use the excellent MP3Tag to do that). So, here I am with a folder full of files and I run EncSpot against it out of curiosity. It reports a bitrate of *191*. That's right fellow illustrious chilibeans, not *192*. For each and every file. I'm puzzled. I rip and encode at various variations in quality of 192 CBR and get the same results out of EncSpot each time. I check encodes I downloaded known to be 192 LAME 3.92 (which is what I'm using in CDex) and they are 192.
Then I had a brainwave. What's the obvious difference? I added a tag to my freshly encoded files.
Voila!
EncSpot now sees them as 192.
Wazzup wid DAT???