Minimserver 0.8.3 albums missing

[lmitche]

(25-01-2015 20:25)lmitche Wrote:  

(25-01-2015 20:23)lmitche Wrote:  

(24-01-2015 21:58)simoncn Wrote:  

(24-01-2015 18:23)lmitche Wrote:  Hi Simon,

Having finally found the time to analyze the change in behavior from minimserver 0.8.2 to 0.8.3, there is an improvement with the 0.8.3 57 update. Thanks for this. The null characters show as question marks, but at least the files are loaded into the library. My guess is the the problem is caused by the issue outlined in this thread.

https://forum.minimserver.com/showthread.php?tid=2104

On the windows 8.1 running minimserver 0.8.3 57 there are over 192 thousand lines of warning messages related to 0x00 errors in my minimserver.log file. Do you know of a Windows mp3tag editor program that can read and rewrite the tags without nulls in a batch process? Modifying each tag, one at a time looks rather onerous.

My guess is that jriver is placing nulls in the tags. They are in almost every tag.

Many thanks for your advice and consideration,

Larry

MinimServer has been producing warning messages for NUL characters in tag values for a long time. The only difference in 0.8.3 is that the tag values are loaded (with the NUL characters replaced) instead of not being loaded.

The first step is to find out what is putting the NUL characters into your tag values. It would be very helpful if you could answer the following questions:

1) How were these file containing NUL characters created? For example, were they ripped from CD using JRiver?

2) If they were ripped from CD using JRiver, what version of JRiver was this?

3) What is the file type of these files (e.g., MP3, MP4. M4A, FLAC, WAV, AIFF)?

Many thanks for your help with this.

Hi Simon,

These files were ripped with Jriver or dbpoweramp or downloaded from HDtracks. However the library has been curated, and tags re-written using Jriver MC version 18.0.122. All are FLAC files.

The nulls seems to be replaced with a question mark character. Is this correct?

Thanks again for your help.

Larry

Also, the null character is always at the end of the tag string.

Also, it looks like there were releases of Jriver MC 16 and 18 both of which padded a null at the end of the tag string. This behavior was fixed in later releases.

This is documented at the bottom of this thread:

http://yabb.jriver.com/interact/index.php?topic=89267.0

Looks like the smoking gun to me.