RobbH wrote:
> It appears that .cur files are only created when the LMS scanner thinks
> it encounters errors in a cue file. It could be an old .cue file that
> points to files that no longer exist, for instance. Or (I think) it
> could be the target file contains tags that do not match the metadata
> defined in the cue sheet. One recent report involved an embedded cue
> sheet that was malformed. It defined several empty tracks, so .cur files
> appeared in the library.
>
> Thanks for replying. I appreciate having some discussion about this,
> because I am very aware that I might be entirely wrong. It's also very
> possible to regard the .cur files as a useful service that informs users
> when there are hidden problems in their libraries. But it also seems to
> be true that if the .cur files were not visible to the user, there would
> be no problem with them in LMS.
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,
});
--------------------
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=116062
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
