1
Bug Reports / Re: Cannot load/save database due to "Destination array was not long enough"
« on: April 09, 2024, 04:09:55 PM »the issue might be with an associated file rather than the music file itself
This should stop the database corruption, but there is something going wrong while a new file is loaded, so could send me the startup error message "error loading associated files..." the next with the filename and activity message that appears after the error message
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files
After further testing, it seems to definitely be a problem with Windows's file path limit. I reorganized my library removing
Code
- "$Left(<Album>,25)"
Not sure why this really is a problem.
Because that fixed the issue (without the 35 patched version,) I'd suggest adding a setting somewhere to clip file names over the file path that doesn't rely on regex, or find a way to release the file path limit if possible. I also wasn't able to get the errors after this because I cleared my log. If this occurs again (since what I did was a temporary fix,) I'll get logs again.
I would also mention that I have ran into this issue multiple times before and just had to adjust my naming string to fix it and make it shorter, so it's reproducible if you just somehow get the file to have a full path over (i think? I don't know the exact number) 255 or like 258 characters on Windows using auto organize (or potentially from any source.) May be a sort of limitation on the programming language(s). You can use my string and make the tagging information really long to try and test this, scan the file in, close, and open it and it'll be corrupt. I am using the latest version of MusicBee at time of writing as well.