kdf Wrote: > Quoting Xantia38 <Xantia38.1sl0kb (AT) no-mx (DOT) > forums.slimdevices.com>: > [color=blue] > > > Does this seem on track? > http://bugs.slimdevices.com/show_bug.cgi?id=656 > > Take a look at the first few comments, as the later ones started > getting into a > different issue. > > If this is applicable, please re-open or file a new bug (referencing > the old one > as the cause, if applicable) > > -kdf
KDF, Thanks for your reply, but I am not sure this is the same bug. They may be related though. In my case, all tracks are listed in the SlimServer listings, including the last one. What is strage is that the errors shown in d_parse are genered by processAnchor because either start, end or "SECS" is missing. Given that the d_parse log shows start and end times as part of the track URIs, I assume the "SECS" piece is missing. Normally this piece is added by calling updateOrCreate when there is no END statement for the last track (line 314 in the Parse.pm file). However, at line 438, sub readCUE calls updateOrCreate just in case before it calls processAnchor, so the information should be there, but it isn't. This is where my knowledge of the system stops. A possible fix may be to call updateOrCreate in any case while still in the parseCUE subroutine. Wolfgang. -- Xantia38 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
