arfur
Morning all,
When scanning my collection, the bitrate field doesn't seem to get filled in. I have visible columns for BPM, key, bitrate and Excaliber, and all fill out fine apart from bitrate. Pretty much all my tunes are encoded in 320kbs constant bitrate, so VBR is not a plausible explanation.
The field does get filled out after I play a tune though, and the information is retained within the library database. Anyone seen this?
Thanks,
Arf
When scanning my collection, the bitrate field doesn't seem to get filled in. I have visible columns for BPM, key, bitrate and Excaliber, and all fill out fine apart from bitrate. Pretty much all my tunes are encoded in 320kbs constant bitrate, so VBR is not a plausible explanation.
The field does get filled out after I play a tune though, and the information is retained within the library database. Anyone seen this?
Thanks,
Arf
geposted Sun 30 Nov 08 @ 6:02 am
arfur
Or could it perhaps be down to MP3s that don't have ID3 tags? I'm pretty sure all my tunes have tags anyway...
On the same track: Do you guys find mp3's below a certain bitrate start sounding rubbish on a big PA?
Of course you do, but at what bitrate, thats the question. I always encode at 320kbs, am happy with tunes down to 192, but at 128kbs I start thinking twice about playing it over a PA.
On the same track: Do you guys find mp3's below a certain bitrate start sounding rubbish on a big PA?
Of course you do, but at what bitrate, thats the question. I always encode at 320kbs, am happy with tunes down to 192, but at 128kbs I start thinking twice about playing it over a PA.
geposted Mon 01 Dec 08 @ 3:32 am
DJ-ALF
Yes, 192 is the lowest quality to give good sound at CBR. I avoid VBR and never used it.
About that problem, not sure what is happening, after scanning it should be displayed. But then again, I don't remember does it should display as I don't use that column, I know that all of track are at 192 as I ripped them ;)
About that problem, not sure what is happening, after scanning it should be displayed. But then again, I don't remember does it should display as I don't use that column, I know that all of track are at 192 as I ripped them ;)
geposted Mon 01 Dec 08 @ 7:11 am
Sonido Alto Voltaje
arfur wrote :
Morning all,
When scanning my collection, the bitrate field doesn't seem to get filled in. I have visible columns for BPM, key, bitrate and Excaliber, and all fill out fine apart from bitrate. Pretty much all my tunes are encoded in 320kbs constant bitrate, so VBR is not a plausible explanation.
The field does get filled out after I play a tune though, and the information is retained within the library database. Anyone seen this?
Thanks,
Arf
When scanning my collection, the bitrate field doesn't seem to get filled in. I have visible columns for BPM, key, bitrate and Excaliber, and all fill out fine apart from bitrate. Pretty much all my tunes are encoded in 320kbs constant bitrate, so VBR is not a plausible explanation.
The field does get filled out after I play a tune though, and the information is retained within the library database. Anyone seen this?
Thanks,
Arf
I experience the same symptom.
geposted Wed 03 Dec 08 @ 4:00 pm
was a fix ever found for this? My bit rates don't show up on newly scanned songs until they are played at least once.
geposted Fri 20 Mar 09 @ 5:23 pm