Bug 5987 - Pause doesn't stick for short compressed tracks
: Pause doesn't stick for short compressed tracks
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: unspecified
: PC Windows XP
: P2 normal (vote)
: 7.3.3
Assigned To: Squeezebox QA Team email alias
: MOV123
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-31 17:19 UTC by Bryan Alton
Modified: 2009-06-17 09:35 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Alton 2007-10-31 17:19:42 UTC
When testing for gapless AAC playback using test files (very short files) from bug 4544 converted to m4a which use mov123 to playback. While playing back if you Pause/Play/Pause with web interface - usually after a few cycles SC ignores the Pause and keeps playing. Sometimes it will play and then stop playing but Web interface and SB interface says tracks are playing.
Comment 1 Chris Owens 2007-11-07 10:31:33 UTC
The depth of the changes required for this behavior is risky.  We will try to do this in the future.
Comment 2 Alan Young 2009-05-05 06:15:40 UTC
I think that his should be fixed somewhere in the 7.3 series, certainly by 7.3.3. Bryan, can you confirm?
Comment 3 Bryan Alton 2009-05-08 00:24:33 UTC
I need to do more testing but the basic symptom has gone but when pause/play/pause a playlist of short tracks - but if paused in the middle of a track it keeps going back to the start of the track and so never plays the all the tracks in the playlist.

This was always an artificial situation (v. short track - typically 5 secs) and I am not sure if it is worthwhile doing more work unless you think there is an underlying bug.
Comment 4 James Richardson 2009-06-17 09:35:05 UTC
This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.