Errors after updating to MinimServer 0.8.1

[ldzpmh]

Installed the update to MinimServer, and now a series of error messages appear in the log and various tracks/albums no longer appear when using Kinsky. There was no issue previously, and they all still appear (and play) when using Twonky rather than MinimServer as the Kinsky interface.

Most of the errors relate to 'unexpected end of file at offset xxxx', or else to 'ID3v2 TYER frame has incorrect value xxxx at offset xxxx'.

As an example, the album 'Almost Blue' by Elvis Costello showed just one track after the update. I tried re-ripping it (using XLD) and this time it shows just six tracks (all of them list the original composer in the metadata, but the ones with no value do not show. I tried adding composer data, but it made no difference).

Have attached a (long) file with the log info. Would be very grateful for any assistance, as I much prefer using MinimServer to Twonky, and don't want to be forced back the latter.

[simoncn]

(23-12-2013 08:31)ldzpmh Wrote:  Installed the update to MinimServer, and now a series of error messages appear in the log and various tracks/albums no longer appear when using Kinsky. There was no issue previously, and they all still appear (and play) when using Twonky rather than MinimServer as the Kinsky interface.

Most of the errors relate to 'unexpected end of file at offset xxxx', or else to 'ID3v2 TYER frame has incorrect value xxxx at offset xxxx'.

As an example, the album 'Almost Blue' by Elvis Costello showed just one track after the update. I tried re-ripping it (using XLD) and this time it shows just six tracks (all of them list the original composer in the metadata, but the ones with no value do not show. I tried adding composer data, but it made no difference).

Have attached a (long) file with the log info. Would be very grateful for any assistance, as I much prefer using MinimServer to Twonky, and don't want to be forced back the latter.

The TYER frame in ID3v2 can only hold a YYYY value, not YYYY-MM-DD. If your tagging software is putting YYYY-MM-DD values into TYER frames, this is a bug in the tagging software. You might be able to work around the problem by changing the tag format to ID3v2.4 and using the TDRC frame instead of the TYER frame.

For the other problem with unexpected end of file messages from your AIFF files, I will need to look at one of these files to see what it contains. Please upload the file

Contemporary - Rock/Elvis Costello/Almost Blue/01 - Why Don’t You Love Me (Like You Used to Do)??.aiff

to my FTP server. I will send you a PM with the server details.

[ldzpmh]

Thanks for the quick response. I suspected that the date format was behind the TYER error, though that does not seem to be connected to tracks/albums not showing at all when using MinimServer. I would be pleased to upload the file when you send me details of your server.

Incidentally, when I launched Kinsky this morning, it did not detect MinimServer at all (and nothing happened when I pressed Restart through MinimWatch). I then went into Apps in the QNAP (TS 421) and turned MinimServer off and then on again, and now MinimWatch is showing yellow for a long, long time (at least 10 minutes as I type this); previously it has only ever shown yellow for a matter of a few seconds whenever I ripped a new CD and restarted.

[simoncn]

(23-12-2013 08:31)ldzpmh Wrote:  Installed the update to MinimServer, and now a series of error messages appear in the log and various tracks/albums no longer appear when using Kinsky. There was no issue previously, and they all still appear (and play) when using Twonky rather than MinimServer as the Kinsky interface.

Most of the errors relate to 'unexpected end of file at offset xxxx', or else to 'ID3v2 TYER frame has incorrect value xxxx at offset xxxx'.

As an example, the album 'Almost Blue' by Elvis Costello showed just one track after the update. I tried re-ripping it (using XLD) and this time it shows just six tracks (all of them list the original composer in the metadata, but the ones with no value do not show. I tried adding composer data, but it made no difference).

Have attached a (long) file with the log info. Would be very grateful for any assistance, as I much prefer using MinimServer to Twonky, and don't want to be forced back the latter.

The 'unexpected end of file at offset xxxx' problem is now fixed in MinimServer update 13.

[ldzpmh]

Very many thanks. All now working well with MinimServer and MinimWatch 0.8.1. Much appreciated.