bpa wrote:
> I don't use cue file but I got involved in a bug which started the
> recent cycle. It's been a while since I waded through CUE code.
>
> Some of the recent problem may come from "bad" applications like
> Ubuntu/Debian SoundJuicer which make it easy to rip a CD into a file per
> track with metadata etc - however it embeds a cuesheet into all the
> track files. !! So now after LMS changes, it is becoming clear to user
> that they have "bad" cue files in their library
>
> cur files are not a way to flag an error as can be seen in code below.
>
> IIRC
> LMS expects cue sheets (etiher embedded or separate) files to be used
> with a *single* WAV or Flac file as all comments talk of a basefile.
> LMS to handle cuesheet wth a single file so LMS creates virtual track
> which have a content type of cur (not 100% sure of this).
> I think the LMS code was written not expecting that there would be a
> different real file associated with the "virtual track" and so other
> parts of the processing such as displaying cur file may be a side
> effect.
>
>
> from LMS Formats/PlayliST/CUE.pm
> >
Code:
--------------------
> >
> # We may or may not have run updateOrCreate on the base filename
> # during parseCUE, depending on the cuesheet contents.
> # Run it here just to be sure.
> # Set the content type on the base file to hide it from
listings.
> # Grab data from the base file to pass on to our individual
tracks.
> if (!defined $basetrack || $basetrack->url ne
$track->{'FILENAME'}) {
>
> main::INFOLOG && $log->info("Creating new track for:
$track->{'FILENAME'}");
>
> $basetrack = Slim::Schema->updateOrCreate({
> 'url' => $track->{'FILENAME'},
> 'attributes' => {
> 'CONTENT_TYPE' => 'cur',
> 'AUDIO' => 0
> },
> 'readTags' => 1,
> });
>
--------------------
> >
Thanks for looking into this, bpa. I don't have any knowledge of the
code involved, so it's not at all clear to me just what the purpose of
the cur file might be, other than it's not supposed to be displayed. But
it looks like it is triggered by some sort of discrepancy between the
track and the basetrack. But of course, track and basetrack might mean
something very different to what I'm guessing they mean.
I do assume the scanner examines the file(s) referenced in the cue sheet
and reads any metadata found there. That seems to be what the comment
says. If the base file is a symlink, do you suppose it dereferences the
symlink? In other words, does it recognize that the actual path to the
file is not the path in the cue sheet? If so, using a symlink might
itself be a discrepancy.
It is certainly true that cue files were originally intended to define
multiple tracks in a single audio file. I used to use CDRWIN, which the
cue file format was developed for. I don't remember when the ability to
reference multiple audio files (but never more than one per track) was
added. But I am reasonably certain that LMS only supported cue sheets
that reference a single audio file, until the changes you were involved
in. That was about two years ago, perhaps? Since those changes, LMS can
use cue sheets with multiple audio files, although that might not have
been intended.
There are still rogue cue files, including some that start a track
definition before naming the audio file. I don't think they work with
LMS.
I'm sure I have failed to understand some of what you said, and I
apologize for that. Could it be that situation as simple as this: .cur
files are created for every file or track that the scanner finds
referenced in a cue sheet. As long as there are no errors, the .cur
files are not displayed. They are only displayed when there is some sort
of discrepancy.
LMS 8 nightly running on Raspberry Pi OS. Mostly virtual players,
occasionally with SB Radio, Boom or Classic.
------------------------------------------------------------------------
RobbH's Profile: http://forums.slimdevices.com/member.php?userid=67008
View this thread: http://forums.slimdevices.com/showthread.php?t=116062
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
