Author Topic: 16/24bit depth column  (Read 4549 times)

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 32034
This is what I had when using a custom tag and Mp3tag to write the value.
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"
Because of the last change i made, i wont be able to do 1
I agree 3 is a good idea, so i will add a tooltip in the main bit-depth column where applicable - not implemented as i am not sure users would think to hover the mouse over the field

Also when <bit depth> is used in virtual tags, rather than saying "Unknown Bit Depth", i will change it to stay blank
Last Edit: April 02, 2018, 10:20:49 AM by Steven

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 32034
fix for rescanning some lossy m4a files incorrectly setting the bit depth to 16

http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip


sveakul

  • Editor
  • Hero Member
  • *****
  • Posts: 1637
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>)

Between the default for lossy now being "blank", and access to the code above (thanks redwing!),  all bases are covered! 8)