Minimserver crash - fixed in Release 72

[Pastim]

(10-11-2015 20:14)simoncn Wrote:  

(10-11-2015 18:27)Pastim Wrote:  I think I know the triggering cause, consistent with the albums I have that failed.

When what minimserver thinks of as 1 instance of a Group is spread across multiple folders, it crashes.

With 'Stabat Mater', each one was by a different composer and in a different folder. With the Symphony in 2 versions, each version was in a different folder.

So, I moved one track from another Symphony (Beethoven 1 by Abbado) on a perfectly good album to the previous folder in the hierarchy. Minimserver crashed when I played it.

So all tracks in one Group, on one Album, must be in the same folder when the Group.displayFormat includes Album.

I think.....?

I wouldn't mind if this was a constraint, like other issues that minimserver reports in the log on scanning.

Thanks for this. It is the vital clue that should enable me to fix the problem. I don't see any reason why this should be a constraint.

I have never seen this problem myself because I use one folder per album.

When I first started storing digital tracks on a computer I figured that even if all the music servers had poor searching capabilities and weak databases, filing my classical stuff by composer, work and performer would always enable me to find the performance of a piece I wanted to play and play it with a simple flac player. Finding an Album with what I want would take much longer, requiring a good memory, something I lack.

For non-classical I file by Album.

Having made that decision several moons ago I've seen no reason to change it. There are occasions when I want to re-tag an Album that makes this slightly awkward since I'm not always sure what's on an Album. Minimserver helps a lot here, with it's excellent indexing system. The other tool I use to find out is foobar2000, where I've developed many different filters to find stuff and do simple tag changes where necessary (eg correcting the name of an Artist).