string index out of range: -1

[Cableguy]

When I restarted my computer (win 7 64 bit) I got this message and a red minim icon. Any clues?

I tried restarting, reinstalling java and updating minimserer but none of that helped.

Thanks.

[simoncn]

(20-01-2013 23:02)Cableguy Wrote:  When I restarted my computer (win 7 64 bit) I got this message and a red minim icon. Any clues?

I tried restarting, reinstalling java and updating minimserer but none of that helped.

Thanks.

There should be a crash dump file with more details. On Windows 7, this file is in the folder C:\Users\<username>\AppData\Roaming\MinimServer\data, where <username> is the user that did the installation. You should also see a minimserver.log file in the same folder.

This folder is hidden in Windows Explorer. To view its contents, you need to type the full path (as above) into the address bar.

Please zip the minimserver.log file and the most recent minimserver-crash-yyyymmdd-hhmmss.log file, and post them here.

[Cableguy]

Thanks, I will do this when I get home tonight.

[Cableguy]

Ok, here is the crash log and the most recent log as well, both mention the string thing at the end.
Have a nice day!

[simoncn]

(21-01-2013 16:34)Cableguy Wrote:  Ok, here is the crash log and the most recent log as well, both mention the string thing at the end.
Have a nice day!

Thanks for the quick response.

Are you using the tagUpdates property? If so, please attach your tag updates file here.

[Cableguy]

Well, thanks for your quick response!

No, I am not using the tag updates.

[simoncn]

(21-01-2013 17:42)Cableguy Wrote:  Well, thanks for your quick response!

No, I am not using the tag updates.

The problem is caused by a tag in one of your files that doesn't contain the correct syntax 'name=value'. There are two possible causes:

1) If this tag is in a FLAC file, MinimServer should detect this, produce a nice error message, and ignore the faulty file. It should not produce the exception that you're seeing.

2) If this tag is not in a FLAC file, the tag would be in a different format (ID3v2, iTunes, etc.), and MinimServer would translate it internally into the 'name=value' format. This internal translation should always produce a tag in the correct 'name=value' syntax.

If you're getting this exception, either 1) or 2) isn't working as intended. I'd like to understand how this problem is being caused so that I can fix MinimServer to handle it correctly without this exception and the red minim icon.

Can you think of any recent tagging change you've made that might be related to this error?

[Cableguy]

Hi Simon,

Well, actually I have added quite a lot of albums to the library since the last reboot (mostly 16 bit flacs, some 24 bit flacs and a few mp3's). If any of these contain a faulty tag they didn't cause any problems until I rebooted.

All albums contain tags from various origin, but I have had them all pass through mp3tag to make sure the tags match my minimserver settings.

How might an incorrect syntax breaching the 'name=value' rule look like? If you give me any pointers what to look for, I can load the library in mp3tag and have a look. Please let me know how else I can help out here. If you need names of recently added albums I can put that together.

Thanks.

[simoncn]

(21-01-2013 19:29)Cableguy Wrote:  Hi Simon,

Well, actually I have added quite a lot of albums to the library since the last reboot (mostly 16 bit flacs, some 24 bit flacs and a few mp3's). If any of these contain a faulty tag they didn't cause any problems until I rebooted.

All albums contain tags from various origin, but I have had them all pass through mp3tag to make sure the tags match my minimserver settings.

How might an incorrect syntax breaching the 'name=value' rule look like? If you give me any pointers what to look for, I can load the library in mp3tag and have a look. Please let me know how else I can help out here. If you need names of recently added albums I can put that together.

Thanks.

I'll send you a test version of MinimServer with extra diagnostics to identify the file that's causing the problem. Would you like this built for Windows x86 or x64? I should be able to do it later this evening.

[Cableguy]

Thanks! I installed the x64 build and mailed that to you!