![]() The point might be moot because I am planning to change this to remove the error message and treat each consecutive run of tracks as a separate group. The problem is that I have 7 different albums with that exact title. For instance, one log line said the error was "in album Bach: Das Orgelwerk". However, the "tracks that aren't consecutive" error could contain a little more detail, such as a path. Quote:(1) Thanks to the log, I was able to correct a few tagging errors. they play the tracks in that group, then stop. (4) Unfortunately, several control points interpret the GROUP container as a stand-alone container. The GROUP tag for all these tracks is "Act 1", and I could find no error, but MinimServer recorded a "tracks that aren't consecutive" error. For instance, in a recording of Parsifal, Act 1 begins on CD 1 and concludes on CD 2. (3) In a few cases, the error seems to be thrown by the GROUP tag extending over multiple discs. And I have quite a few other instances of the same thing. Naturally, that throws the GROUP tags out of sequence. (2) While the MinimServer concept of GROUP works well most of the time, it doesn't do so always.įor instance, I have two versions of the Monteverdi Vespers in which orchestral works by other composers were inserted between movements of the Monteverdi score. (1) Thanks to the log, I was able to correct a few tagging errors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |