Bugzilla – Bug 10805
FF/REW (scanning) broken within .cue files (not FLAC)
Last modified: 2011-03-16 05:18:23 UTC
This is somewhat similar to bug# 10419, but it specifically happens to audio files with cues. I am running version 7.3.2 - 24695 and getting "CANNOT SCAN THROUGH REMOTE TRACKS" message on the display of my Sqeezebox3 when trying to fast-forward or rewind. But this only happens on mp3 files which have a .cue file associated with them (logical breakdown of tracks within a long mp3 file). This used to work properly in old SqueezeCenter version (6.x).
I might add that in the SqueezeCenter GUI, when such track is playing, it is also not possible to click on the progress bar in order to advance/go back within the track.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
For some reason Bugzilla did not change the target when I did this yesterday. Or maybe it was me. In either case, I'm trying it again.
Alan, is this functionality possible with new streaming?
Created attachment 5618 [details] Possible patch I think that the test for end-seek in canDoSeek() is unnecessary. This would require a chunk of testing to be sure.
Assessment of remaining effort
Update hours
== Auto-comment from SVN commit #30442 to the slim repo by ayoung == == https://svn.slimdevices.com/slim?view=revision&revision=30442 == Fixed bug 10805: FF/REW (scanning) broken within .cue files (not FLAC) No need to test if end seeking is needed in Song::canDoSeek() as transcoder selection will do this itself if necessary.
Update target and hours
Is there any chance of this ever getting resolved? I am now running 7.5.3 - r31792 and still having this issue. I guess I do not understand what I'm supposed to do with this patch that Alan posted...
The Target Milestone indicates the version it is fixed in, which is 7.6.