Bugzilla – Bug 10237
Momentary sound cut-out at 10 seconds from end of track
Last modified: 2009-10-05 14:29:13 UTC
Every track played via SqueezePlay has a momentary sound cut-out with 10 seconds left in the track. Steps to Reproduce: Start SqueezePlay, play a track. It happens on every track. Actual Results: All tracks have a momentary sound interruption at the point where there are 10 seconds left in the track. Expected Results: Smooth playback, no perceptible sound issues. Build Date & Platform: Date and platform of the build in which you first encountered the bug. Since first version of SqueezePlay tested (Oct 1, 2008) Additional Builds and Platforms: n/a Additional Information: Any other useful information. Server is XP (SP3) computer, using Version: 7.3 - 24206 @ Fri Dec 5 03:04:18 PST 2008 SqueezePlay client is on second XP (SP3) computer, using Dec 5 version. All tracks are FLAC. Looking at the network data transfer, normal transfer rate is about 1 Mbps. At about 35 seconds from end of track all data transfer stops, while track plays normally. At the 10 second from end of track mark there is a data transfer spike to 10+ Mbps. This is where the sound cuts out. Transfer then continues at 1 Mbps. Wireless network reports excellent connection, normally 48 to 54 Mbps. SoftSqueeze has no problem with 7.3 and playback on my client computer. With SoftSqueeze, data transfer also stops at about 35 seconds from end of track. There is a data spike at about 16 seconds from end of track with no sound issues. I don't have any mp3 files in my library but I will add a few to test (this just occurred to me)
I see the same problem with AAC files, about 7 seconds from the end of each track.
*** Bug 10497 has been marked as a duplicate of this bug. ***
Created attachment 4590 [details] SqueezePlay crash Windows appcompat file I think this might be related. I not always hear the "10s before end" interruption but sometimes. But SqueezePlay will usually only play a few songs, then crash with a Windows message like "squeezeplay has detected a problem and must be terminated" (rough translation from German Windows message "squeezeplay.exe hat ein Problem festgestellt und muss beendet werden.") exactly 10s before the end of a song. The crash is shown as: AppName: squeezeplay.exe AppVer: 1.0.0.1 ModName: portaudeio_x86.dll ModVer: 0.0.0.0 Offset: 0000410b I include the "564d_appcompat.txt" file Windows generates, for whatever it may be worth. SqueezePlay is version from 2009-01-07 (still has no version number!) German Windows XP Home+SP2 SqueezeCenter v7.3.2 - 24541 This happened with earlier 7.3 SC and SP versions, too. I don’t see any real reproducability except that it ALWAYS crashes 10 or 11 seconds before the end of a song, in this case at song #11 of 20 out of a "Random Mix".
I would say this is variable--not always 10 seconds, but always close to the end. Could it be the gapless playback implementation?
(In reply to comment #4) > I would say this is variable--not always 10 seconds, but always close to the > end. Could it be the gapless playback implementation? > For me it occurs at the exact same point with every track (all tracks are FLAC). Watching the network traffic, I note that it coincides with a large data spike sent by SqueezeCenter. It could be a buffer issue related to gapless playback and your time variation might be due to differences in hardware and/or systems configuration. MP3 tracks (LAME VBR -v2) exhibit the same sort of behavior - sound blip at 10 seconds from end but streaming data stops being sent at about 90 seconds from end of track.
Interestingly, there is a bleep towards the end of each track when using Softsqueeze 3.7 as well--at about the same point where Squeezeplay exhibits this "drop-out." Reverting to Softsqueeze 3.5 resolves that problem. Still wondering if this problem is somehow related (perhaps distantly) to gapless playback implementation.
I find that Squeezeplay also "has a momentary sound cut-out with 10 seconds left in the track." This happens on virtually every track: all the files are .flac. This is still happening with version of Squeezeplay downloaded on Jan 29th, 2009: (7.4r3899m?). Platform is Windows XP Pro SP3. Laptop has 2 gigs of RAM. Winamp does not suffer the same dropout.
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.
Whether you fix it now or in 7.4 depends on the importance you place on audio quality in the products the bug impacts. If it were impacting my squeezebox I would be yelling my head off: it's really annoying. I don't listen to softsqueeze as much, so I cringe a little, but I still use it occasionally. I would suggest you not call softsqueeze anything beyond beta quality with this bug on the list.
I am running Squeezeplay on a pc with a digital (SPDIF) connection to my receiver. The receiver has a "light" that lights up when a digital connection is established. This light blinks off and on again at about 10 seconds before the next song (which is when the other commenters also says the experience the sound dropout). My theory is therefore that Squeezeplay turns it's internal sound-output off and on again and that is what's causing the dropout.
I experience the same issue, a hickup at approx. 10 seconds before the end of the song. Playing mp3's on both OSX and Windows Vista.
I too experience the sound cutout just before the end of each FLAC.
Does the crossfade/fade in/fade out/fade in & out settings have any influence on this problem?
(In reply to comment #13) > Does the crossfade/fade in/fade out/fade in & out settings have any influence > on this problem? No, I've tried them all and the sound always disappears
Just wanted to also confirm this bug running on Win7 - happens on both flac and MP3 files both, and is 100% consistent (occurs in same place 100% of the time)
Reset priority before triage.
I have reviewed the latest (unreleased) code in 7.4 and think this should now be fixed. QA to verify when testing the 7.4 release.
Just wondering when this will be implemented in the 7.4 nightly? I've installed the latest on occasion including the latest build of today and I still have the problem occuring at 10 seconds. It seems to be less prevalent but it's still there.
hello?
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.