CBR or VBR

To many ads? Support ODJT and see no ads!
Media Monkey will tell you on the details page of the properties.

If you see an odd sized bitrate, it is most likely a VBR file. Common CBR rates are 128, 160, 192, 256 and 320. If for example you see 244, it's probably a VBR file.

Amazon files are VBR (at least every one I've gotten is).
 
Playing has been OK, but I have experienced weirdness when cueing deep into a VBR songs. Con't think of the songs off the top of my head, but I have a few that I cue 30-45 seconds in to start past transitional intros and they can jump in multi-second intervals rather than the typical smoothly which all CBR songs do. I think it's related to the nature of a CBR being 100% predictable but a VBR is unknown. I always rip 320 CBR, but friggin Amazon continues to use VBR. Disk space is cheap, why not use CBR?
 
Never had an issue with VBR; been ripping that way since 06

VBRs can be a problem when you're streaming them, e.g. your decoder is reading chunks of a file at a time. The decoder has to work much harder to figure out what is in each frame of the file.

It's usually no issue during simple playback, because the decoder simply decodes each frame, and sends it to your sound card buffer. Where the problem comes in, is seeking within the stream, because the decoder can't accurately predict the bitrate of the samples in a frame. So, the decoder has to "look ahead", or rely on a VBR header with seek table (which often does not exist), which obviously uses more resources, both in terms of memory and CPU.

IMHO, CBR is the much better choice for DJ work, where you might use different hardware or software, and you don't want to worry about inconsistencies across those platforms.
 
VBRs can be a problem when you're streaming them, e.g. your decoder is reading chunks of a file at a time. The decoder has to work much harder to figure out what is in each frame of the file.

Where the problem comes in, is seeking within the stream, because the decoder can't accurately predict the bitrate of the samples in a frame. So, the decoder has to "look ahead", or rely on a VBR header with seek table (which often does not exist), which obviously uses more resources, both in terms of memory and CPU.

And therein lies my problem. I can't FF using RockIt for tracks I've bought through Amazon.

But tracks bought through I Tunes (once you switch them to mp3's) are at a 320 bit rate. So I assume that's a CBR file.

Well d*mn, after all these years, no more tracks from Amazon for me. It's all gonna have to be all from I Tunes.

Thanks for all the replies and answers.
 
And therein lies my problem. I can't FF using RockIt for tracks I've bought through Amazon.


Yes you can.

Use either the FF/RW shortcuts, or a skin with a seek slider. It's much more accurate than the wheel... ;) :)
 
VBRs can be a problem when you're streaming them, e.g. your decoder is reading chunks of a file at a time. The decoder has to work much harder to figure out what is in each frame of the file.

It's usually no issue during simple playback, because the decoder simply decodes each frame, and sends it to your sound card buffer. Where the problem comes in, is seeking within the stream, because the decoder can't accurately predict the bitrate of the samples in a frame. So, the decoder has to "look ahead", or rely on a VBR header with seek table (which often does not exist), which obviously uses more resources, both in terms of memory and CPU.

IMHO, CBR is the much better choice for DJ work, where you might use different hardware or software, and you don't want to worry about inconsistencies across those platforms.

thanks Rick- the only issue I've ever encountered was with an early version of vdj - track length was wrong; never encountered any issues since then.....I'm not so inclined to re-rip thousands of tracks; I'd be retired before that
 
VBR since 2001. Not going to change now. Well, once my software supports FLAC tags, then bye bye MP3.

Reason #56 why I still get CDs vs MP3 DVDs.