Newly Added Files Unplayable After Editing Tags

[cooperbh]

Tagging WAV files is supported by MB but its not well supported with other players.

@cooperbh, could you send me a link to a zip of a wav file (before you edit it)?
Also what MB version are you using?

I'm using 3.3.7115. Here's an unedited WAV file...

https://www.dropbox.com/s/g1edjtmbdk0dpxa/01%20Satellite%20Skin.zip?dl=0

Just to reiterate, WAV files that have had metadata edited with Audacity or WMP play without issue in MB, WMP and Groove. WAV files that had metadata edited with MB before June play without issue in MB, WMP and Groove. It is only in the last several days that metadata edits of WAV files using MB have resulted in playback failure/corruption error messages in all the aforementioned players.

[Steven]

yes there is a bug for the way that file is arranged. This should fix the issue:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee files

[cooperbh]

yes there is a bug for the way that file is arranged. This should fix the issue:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee files

Just to make sure I don't muck anything up, I should extract and paste that in the 50072StevenMayall.MusicBee_kcr266et74avj\ folder, correct?

[sveakul]

Unlike other players, I get no indication at all that Musicbee is ever aware of when there is a CD in the drive. Could it be because my drive is external? Do I need to add a tab or something?

When you drop the menu and select Tools-->Rip CD, what do you see?

[Steven]

yes there is a bug for the way that file is arranged. This should fix the issue:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee files

Just to make sure I don't muck anything up, I should extract and paste that in the 50072StevenMayall.MusicBee_kcr266et74avj\ folder, correct?

It looks like you are using the store version, in which case you will need to wait until the next official release which might be some time away or uninstall and install the standard desktop version and then apply the patch

[sveakul]

I wonder if it would be a good idea to add something like "cannot be updated manually" to the Windows Store description on the download page?

[cooperbh]

yes there is a bug for the way that file is arranged. This should fix the issue:
https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee files

Just to make sure I don't muck anything up, I should extract and paste that in the 50072StevenMayall.MusicBee_kcr266et74avj\ folder, correct?

It looks like you are using the store version, in which case you will need to wait until the next official release which might be some time away or uninstall and install the standard desktop version and then apply the patch

Gotcha. Think I'll just stick with FLAC for now while waiting out the next official release. Thanks so much for your attention on the matter.

[phred]

I wonder if it would be a good idea to add something like "cannot be updated manually" to the Windows Store description on the download page?

And perhaps adding a prefix or suffix to the Store's version number. The OP was asked what version (number) was being used, but s/he wasn't asked, nor were we told, that it was the Store version. Having something in the version number might avoid this in the future.

[cooperbh]

Unlike other players, I get no indication at all that Musicbee is ever aware of when there is a CD in the drive. Could it be because my drive is external? Do I need to add a tab or something?

When you drop the menu and select Tools-->Rip CD, what do you see?

I had forgotten I tried that already. The issue was that all album info fields were blank and had to be filled manually, including all track titles. Quicker and easier to just rip in WMP and import to MB library.