Threaded Mode | Linear Mode

Bart · 07-04-2016, 15:00

(06-04-2016 23:17)asiufy Wrote: As it is, I'm going to have to simply dump MinimServer, as I'm not going to convert 1000s of albums just because.

Why would you have to (re)convert thousands and not just the (few) that give you the error?

asiufy · (This post was last modified: 07-04-2016 22:58 by asiufy.)

I have 12Tb of music. 14000+ albums. I still don't know exactly how many are affected by the MinimServer bug, but a cursory look at the log, it's going to be a lot.

simoncn · 08-04-2016, 09:13

(07-04-2016 22:57)asiufy Wrote: I have 12Tb of music. 14000+ albums. I still don't know exactly how many are affected by the MinimServer bug, but a cursory look at the log, it's going to be a lot.

It's not a MinimServer bug, it's a bug in the software that was used to rip the bad albums.

Martin H · 08-04-2016, 12:28

(07-04-2016 22:57)asiufy Wrote: I have 12Tb of music. 14000+ albums. I still don't know exactly how many are affected by the MinimServer bug, but a cursory look at the log, it's going to be a lot.

As a layman reading the posts etc. it looks like you have incorrectly formatted files that surely it's in your interests to correct. It may be that some programs will serve/play these files despite these format errors but why would you expect or even want that?

You would surely want the converting program to be fixed so there are no future format errors and you would want to fix your current files and reconversion will do that. How long it might take is driven by your faulty ripping program and how many files it has incorrectly formatted. But batch them up and let it run overnight while you sleep using something like DBPoweramp. At least that way you can be sure that your files are correct.

Each to there own I guess but it's difficult to understand your stance - perhaps there is missing information.

asiufy · 08-04-2016, 18:52

My "faulty" ripping program is the one that's recommended here and everywhere else, XLD. I have reported this issue to the XLD developers too, but I haven't heard back from them.

Again, I'm using a standard app to convert, that lots of other people use (seems to be more popular than dBPowerAmp) and every single other app out there will play these files without a hitch, UPNP servers or regular playback software (JRiver, iTunes, Audirvana, etc.) I know because I have other UPNP software running on the same NAS, and they can see these files and play them just fine.

Do you know for sure that if I convert everything using dBPowerAmp (an expenditure of $ and time), MinimServer still won't throw a fit and refuse these files?

Again, seems far easier for the developers to just allow these files to go through, maybe with a warning in the log. The files are not defective, proof being that they actually play, with embedded artwork, etc. Seems to me MinimServer is the one that can't handle AIFF properly...

simoncn · 08-04-2016, 22:50

The OP on this thread converted the files again with XLD and this fixed the error messages. Can you try doing an AIFF-AIFF conversion with one file using the current version of XLD and let me know whether the converted file still produces an end-of-file message?

asiufy · 08-04-2016, 23:36

I did, and MinimServer now sees the file. My point is that I've been using XLD all along, I've never used anything different to rip my AIFFs.

simoncn · 09-04-2016, 08:41

(08-04-2016 23:36)asiufy Wrote: I did, and MinimServer now sees the file. My point is that I've been using XLD all along, I've never used anything different to rip my AIFFs.

Was the file ripped with the same version of XLD that you used for the conversion or with a previous version of XLD?

simoncn · (This post was last modified: 09-04-2016 16:04 by simoncn.)

(08-04-2016 18:52)asiufy Wrote: Again, seems far easier for the developers to just allow these files to go through, maybe with a warning in the log.

This depends on what kind of format error is causing the problem.

There is one specific (and common) case where MinimServer could produce a warning and attempt to recover from a format error. This is the case of a form size field that extends past the end of file. For this specific case, MinimServer could produce a warning and make an internal adjustment of the form size so that it matches the file length. This could cause problems if the form size is correct and the file has been truncated but these problems should be picked up by other checks within the MinimServer file reading code.

With this change, the log would still contain a message for each file that has this format error but it would be a warning instead of an error. Changing it to a warning means that the file would be processed instead of being ignored.

Ther would be no change to other error messages for file format errors as it is difficult to recover from these and continue reading the file.

A couple of points to note: There is a good chance that this change would allow files ripped by XLD to be processed by MinimServer but I can't be certain without having seen the faulty files. Also, MinimServer would not change the form size in the file, so the incorrect form size would be sent to the renderer and it is possible (but unlikely) that this might cause some renderers to have a problem with playing the file.

What do people think of this proposal?

asiufy · 10-04-2016, 01:15

I can supply the files, and test a beta version, if you want!

Thanks,
Alex