Threaded Mode | Linear Mode

AndrewS · (This post was last modified: 08-09-2022 15:05 by AndrewS.)

Doh! Should have spotted that! Got it. Attached.

simoncn · 08-09-2022, 15:35

Thanks for this. The problem is in lines 881 and 882 of this file. It looks like your library contains a file named

Code:

/Volumes/flac 2 Library/flac library 2/Soft Machine/2022-05-13, Teatro Caupolicán, Santiago, Chile (flac HD)/05 - Heart Off Guard - Broken Hill[cr]-.flac

where the [cr] is a carriage return (line ending) character. The code in MinimServer that reads the added-dates.txt file doesn't expect a filename to contain a line-ending character and this is the cause of the error.

You can work around this issue by renaming this file to (for example)

Code:

/Volumes/flac 2 Library/flac library 2/Soft Machine/2022-05-13, Teatro Caupolicán, Santiago, Chile (flac HD)/05 - Heart Off Guard - Broken Hill.flac

and using TextEdit to update lines 881 and 882 in the added-dates.txt file to match this new filename. Any filename that doesn't contain a [cr] character would work.

I will think about how to fix this error with filenames containing a [cr] character in a future update.

AndrewS · (This post was last modified: 08-09-2022 16:00 by AndrewS.)

Ahha! That's cured it. I don't know how that errant return got in there. All running OK now.

Thank you so much Simon, for both great software (use it every day) and your patient support. I appreciate it.

simoncn · 09-09-2022, 17:49

I have done some more investigation into this issue. The current version of MinimServer already has a fix for the [cr] problem. If MinimServer finds a [cr] (carriage return) or a [lf] (line feed) in a file path, it writes a special escape sequence into the added-dates.txt file do that this file can be read back without errors. This didn't happen for you because your added-dates.txt file was written by an older version of MinimServer without this fix.

AndrewS · (This post was last modified: 10-09-2022 00:36 by AndrewS.)

Just curious - Do you think that [cr] precipitated the original issue requiring the upgrade, and persisted as it was already written into the added-dates.txt file? Would certainly explain the issue.

And do these kind of errors/warnings get listed in the log? It'd be good to be able to check after a rescan to identify and address any tagging issues.

simoncn · 10-09-2022, 19:00

(09-09-2022 23:23)AndrewS Wrote: Just curious - Do you think that [cr] precipitated the original issue requiring the upgrade, and persisted as it was already written into the added-dates.txt file? Would certainly explain the issue.

Yes, exactly as you say.

Quote:And do these kind of errors/warnings get listed in the log? It'd be good to be able to check after a rescan to identify and address any tagging issues.

All errors should be shown in the log but this might not happen if the error is caused by a bug (as in this case).