getmusicbee.com
General => MusicBee Wishlist => Topic started by: redwing on April 12, 2018, 05:41:44 PM
-
Currently if you use MB's default settings for converting 24-bit files, they get converted to 16-bit files.
Foobar defaults to keep the bit depth when converting as it has the following option and defaults to auto.
(https://i.imgur.com/ZuyzMeE.png)
So if it's set to auto, you can forget about bit depth for file conversion unless you want to change it.
-
+1
-
+1
-
+1
-
Currently if you use MB's default settings for converting 24-bit files, they get converted to 16-bit files.
is that comment based on observation from older versions of MB? I recently made the change to display the bit depth and as part of that the file converter should be preserving the bit depth on feeding data into the relevant encoder
-
Yes, I didn't know this was already addressed at the same time. Just tested with some 24-bit files, and they work perfectly with no differences in bit comparison test. Thanks!
-
Two issues regarding bit depth:
- Volume analysis clears bit depth info for the tracks. Bit-depth column shows nothing for the tracks until they get rescanned.
- At that point (with unknown bit-depth) if you convert those files, they get converted to 16-bit files. Shouldn't it check the bit depth before converting?
-
the bug is fixed for the next v3.2 update
for the second point, I dont see it being any different to tags that are out of synch with the MB cache - MB doesnt attempt to resynch all tags/ properties for every file operation it does. Irrespective if the cached bit-depth is correct or not, it will still generate 16-bit file file data correctly. However as i write this i realise MB probably isnt caching the new bit-depth value in the new file so i will fix that
http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip
-
Only the first issue is fixed. It still converts to 16-bit for files with unknown bit depth.
-
Now the second issue is fixed as well. Thanks!