Editing Tags: "Unable to save file" Error

[OrthoCube]

Hello, it's my first time posting here.

Just started using MusicBee since two months ago, but I recently encounter problems when I migrated from FLAC to WavPack.

I'm a neat-freak when it comes to my music collection, and I retag all files.
However, I get problems whenever I tag WV files.

I get this error (translated from Japanese, since I'm running Japanese Windows 10. However, MusicBee is set to English):

Original:
Error
Unable to save file:
******************.wv
オブジェクト参照がオブジェクト インスタンスに設定されていません。

Translated:
Error
Unable to save file:
******************.wv
The Object Reference is not set to an Object Instance.

I'm also an aspiring programmer, and it looks like the .NET version of Java's "java.lang.NullPointerException" or something XD

Anyway, as for recreating the error, this is where the problem happens.
I spent significant time trying to make the error consistently appear, but it seems to happen on random. (Yes, I know nothing happens on random when it comes to programming, but still...)

Checking the files on Mp3tag shows that the files have normal APEv2 tags.
Changing one tag or multiple tags then clicking "Save" sometimes triggers the error, sometimes not.

When the error occurs, it seems that the APEv2 tag becomes corrupted (Mp3tag shows it as "(!bad APEv2)" or something similar). Sometimes, the tag is still readable even if it is corrupted, sometimes, it is no longer recognized, causing the tags to be completely lost from the file (fortunately, the tags are still in MusicBee's database, so the "Synchronize tags..." command becomes useful.)

Unfortunately, I don't have specific ways to reproduce the bug--sometimes, it happens, sometimes not.
However, I'd really appreciate it if someone can look into this.

I know I'm asking too much, and I really won't even complain--MusicBee is an awesome program, and this is just a minor thing.

Thanks for creating this program and sharing it with everybody! Wishing you more success in the future

[Steven]

i would need a single instance of the full stack dump which will be in the error log (help/ support/ view error log)

[OrthoCube]

Thank you very much for the reply.

Unfortunately, no error log is produced.

I opened the error log, which showed several errors at first, so I searched for the error I'm facing and it isn't logged in the file.

So I deleted the file and tried to reproduce the error again.

I was again able to reproduce the error by tinkering with the tags then saving. However, checking the logs after the error was shown revealed an empty file. A completely empty file. I tried to reproduce the error again, it happened, but checking the logs again did not reveal anything.

Until now, I am not able to reproduce the error consistently--it happens like, 50% of the time, and I can't determine conditions on how to make it reproduceable 100% of the time.

Screenshot of the MsgBox:
https://imgur.com/yPFDSou

[OrthoCube]

Tried again, successfully reproduced the error, and now, MusicBee says "No errors have been logged"

[Steven]

in that case can you confirm you are happy to run a debug version which will log more info to the error log

edit:
actually it might be easier and quicker if you could PM me a link to a zip of one of the .wv files

[OrthoCube]

Sure, thanks, I'll PM you.

Thanks again!

[Steven]

yep, its a bug with APE v2 tags. This should fix it:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip

unzip and replace the existing musicbee application files

[OrthoCube]

Thank you very much, you're awesome!

I still haven't tested if it will work, but I believe it will 

Anyway, I hope this fix becomes included in the next release.

Thanks again!

[Steven]

please re-download the patch as i discovered one more circumstance with APEv2 tags that causes this error