Quoting Xantia38 <[EMAIL PROTECTED]>:
>
> Hello,
>
> after further investigation I believe to have found the problem. Maybe
> someone with better understanding of Perl and the SlimServer code can
> help me with this:
>
> All my cue file entries have an END statement for each track, including
> the last one. This is done by the program which generates the cue
> files.
>
> In SlimServer, the code in Parse.pm reads the cue file with sub
> readCUE, which calls parseCUE and later on processAnchor. This latter,
> processAnchor, will check whether $attributesHash->{'SECS'} has a
> value, which can only have been generated by the line 314:
> my $track = $ds->updateOrCreate({
> 'url' => $filename,
> 'readTags' => 1,
> });
>
> However, this line gets only called when at least the last track in a
> cue sheet doesn't have an END statement and the length of the wav file
> needs to be read from that file itself.
>
> To test the "theory" I removed the last END statement from my cue file
> and indeed, this solves the problem.
>
> I think this is a bug, because the code makes false assumptions. It
> also makes the code behave differently from previous versions of
> SlimServer. And last, but not least, this removes a nice feature, which
> allows to have multiple cue sheets for a given wav file.
>
> Can someone with better understanding of all this please check this. I
> can then file a bug report.
I believe this is an existing bug. I think there used to be a problem with the
last track in cue files, which was solved by the special case you mention
above. Clearly this is resulted in a problem for the cue sheets that are
generated by your application.
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
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
