Author Topic: Don't forcibly write ENCODER tag when saving any settings in a file  (Read 2686 times)

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34361
For the next v3.5 update, the encoder wont be written as a tag but any existing tag for wont be deleted. Its now display only in the tag editor, but if a tag did exist it could be updated/ deleted in the tag inspector

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34361
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files

note that its been updated to now use .NET 4.8
if you have any issues please let me know
Last Edit: April 10, 2022, 11:29:13 AM by Steven

SonicRings

  • Sr. Member
  • ****
  • Posts: 277
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files

note that its been updated to now use .NET 4.8
if you have any issues please let me know
What wonderful news to wake up to! Thank you so much, Steven, as always!

There is one issue that doesn't bother me at all, but I think it's worth mentioning in case anyone cares: the encoder seems to be getting cut off due to being too long.



I don't mind whether or not it's fixed, but yeah, that's the only thing I noticed regarding this. Otherwise, great update, and I'm very grateful for this change!

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9356
... the encoder seems to be getting cut off due to being too long.
Does the full path appear if you hover the cursor over it?
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

SonicRings

  • Sr. Member
  • ****
  • Posts: 277
... the encoder seems to be getting cut off due to being too long.
Does the full path appear if you hover the cursor over it?
Doesn't seem like it does. Again, not that I care to see the encoder, but that is the behaviour, yes: there's no way to see the full encoder.