Bugzilla – Bug 15381
flac problems after upgrade from 7.3.3
Last modified: 2010-02-24 08:36:11 UTC
hello - after upgrading from 7.3.3 to the 7.4 series my flac files with embedded cuesheets and imported cuesheet tags are no longer readable. it appears to be related to a change in how the "FILE" line from the "CUESHEET" portion of the tags is used (created w/--set-tag-from-file="CUESHEET=image.cue"). here is some example output from /var/log/squeezeboxserver/server.log: [09-12-29 16:59:42.1836] Slim::Player::Protocols::File::open (99) Error: could not open /srv/Music/plastikman-consumed_bonusCD_(jp)/dummy.wav: No such file or directory [09-12-29 16:59:42.1856] Slim::Player::Song::open (461) Warning: stream failed to open [file:///srv/Music/plastikman-consumed_bonusCD_(jp)/dummy.wav#0-946.28]. and here is the metaflac information from that file: % metaflac --export-cuesheet-to=- ./plastikman-consumed_bonusCD_\(jp\)/consumed_bonusCD_\(jp\).flac FILE "./plastikman-consumed_bonusCD_(jp)/consumed_bonusCD_(jp).flac" FLAC TRACK 01 AUDIO INDEX 01 00:00:00 REM FLAC__lead-in 88200 REM FLAC__lead-out 170 41731536 % metaflac --export-tags-to=- /srv/Music/plastikman-consumed_bonusCD_\(jp\)/consumed_bonusCD_\(jp\).flac ARTIST=plastikman ALBUM=consumed bonusCD (jp) TITLE=consumed bonusCD (jp) DATE=1998 GENRE=Techno TRACKNUMBER=01 CDDB=0203b201 REPLAYGAIN_REFERENCE_LOUDNESS=89.0 dB REPLAYGAIN_TRACK_PEAK=0.96563721 REPLAYGAIN_TRACK_GAIN=-4.48 dB REPLAYGAIN_ALBUM_PEAK=0.96563721 REPLAYGAIN_ALBUM_GAIN=-4.48 dB CUESHEET=PERFORMER "plastikman" TITLE "consumed bonusCD (jp)" FILE "dummy.wav" WAVE TRACK 01 AUDIO TITLE "intro \\ plasticene \\ untitled acid fill \\ untitled drum fill (live)" INDEX 01 00:00:00 please let me know if any additional information is required. thank you for your time and effort in making this software available for debian.
i believe this was the same issue as that reported in: Bug 15105 - NewScanner for 7.4+ intolerant of bad FILE value in embedded cuesheets this was fixed in 7.4.2 and my flac files are now working as expected. thank you.
*** This bug has been marked as a duplicate of bug 15105 ***