Any file that is not 16 bit will display the bit depth in the track info panel (for the playing track not selected track)
I cant see anything more than that being implemented
$If($Contains(<Type>,", ")=T,$Split(<Type>,", ",2),)Any file that is not 16 bit will display the bit depth in the track info panel (for the playing track not selected track)
Any file that is not 16 bit will display the bit depth in the track info panel (for the playing track not selected track)
I cant see anything more than that being implemented
If we had access to that 'read-only' tag than you could use a virtual tag like:@ StevenCodeto use just the bit depth.$If($Contains(<Type>,", ")=T,$Split(<Type>,", ",2),)
As this has come up quite often, i have now added database support for bit depth.
The value will be automatically saved for new files, but for your existing files, you will need to rescan them (right click/ Send To/ Rescan Files)
The new "Bit Depth" field can be displayed, sorted, filtered as any field
http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip
As no lossy compression format has an associated bit depth, shouldn't they be blank or have N/A?While you are correct, i felt most users wont know that and have the idea that its 16-bit. So less "bug" reports if its stated as 16-bit
for the next update i have changed it to show blank for lossy files. The value for filtering/ sorting purposes is 0
Hmm, before last update all my mp3 and m4a files was showing correct bit depth - 16 bit. Now it's Unknown Bit Depth :-\the change made is technically correct in that lossy files have an undefined bit-depth. But i suspect most people dont know that and think its 16-bit. I will leave it a day to allow for other's comments but i am inclined to revert it to show 16 bit for lossy files
Audacity refers to MP3 and AAC files as "32-bit float." I suppose that's as accurate a description as any. But I really don't know if there's an industry standard. "Float" might be a good option, but I suspect the goal with this implementation is to keep the value down to two characters for nice, thin columns.
if a two-character designation is a must, perhaps either "FL" or "3F", if 3 characters then "32F" would be good.
For me both mp3tag and foobar show nothing for lossy format files when the field is added to a column.
I think MB could do the same thing.
$IsNull(<Bit Depth>,,"Bit Depth: "<Bit Depth>)For me both mp3tag and foobar show nothing for lossy format files when the field is added to a column.
I think MB could do the same thing.
I think that "16 bit" looks better than "Unknown Bit Depth" even if it's not correct.
$IsNull(<Bit Depth>,,<Bit Depth>)$IsNull(<Bit Depth>,16,<Bit Depth>)for the next update i have changed it to show blank for lossy files.
AAC files still show 16.only if MB thinks its an ALAC file. Is it the same if you rescan it?
Hmm, before last update all my mp3 and m4a files was showing correct bit depth - 16 bit. Now it's Unknown Bit Depth :-\are you using the field in a virtual tag, or can you explain how you are using the field?
Hmm, before last update all my mp3 and m4a files was showing correct bit depth - 16 bit. Now it's Unknown Bit Depth :-\are you using the field in a virtual tag, or can you explain how you are using the field?
would you mind sending me a link to the file?
PMed an iTunes-purchased one.yes i get the same and its fixed for the next update
This is what I had when using a custom tag and Mp3tag to write the value.Because of the last change i made, i wont be able to do 1
Since MB is automatically populating the field on file import, maybe the best outcome would be;
1/: "Unknown" for any older unscanned files
2/: Bit Depth for lossless formats
3/: Leave it blank for lossy formats with the tooltip; "Only lossless formats have fixed bit depth"
Also if you prefer to see 16 (or whatever) instead for all files with the field blank, use this.Code$IsNull(<Bit Depth>,16,<Bit Depth>)