Bugzilla – Bug 10439
Bitrate limiting does not work
Last modified: 2009-01-22 13:54:37 UTC
+++ This bug was initially created as a clone of Bug #10392 +++ Created an attachment (id=4477) Regular log Hello The problem is described in forums (see url) After upgrade to 7.3 I tried to stream to my SS. First thing I noticed CPU on SC went 100% for about 20 seconds (taken by lame process). The audio started. About 30 sec before the track end lame kicked in again. However, the first track did not finish - it was cut off about 10 seconds before the end, and the next track started to play. This went on with every track. I rolled back to 7.2.1 - everything perfect again. To test I've started the server from command line with player.source=debug. I was unable to capture the console messages into file, so I only have part of them (as log2.txt). Regular log is attached as log.txt. Here is what seems to indicate a problem: SW: 2008-12-19 12:01:33.923 MoveDataThreadProc for step 2 got 4096 bytes, about to write data. SW: 2008-12-19 12:01:33.923 MoveDataThreadProc for step 2 about to call ReadFile . SW: 2008-12-19 12:01:33.938 MoveDataThreadProc for step 2 got 1311 bytes, about to write data. SW: 2008-12-19 12:01:33.938 MoveDataThreadProc for step 2 about to call ReadFile . SW: 2008-12-19 12:01:34.017 MoveDataThreadProc for step 2 failed reading with er ror 109. SW: 2008-12-19 12:01:34.017 MoveDataThreadProc for step 2 ending. SW: 2008-12-19 12:01:34.017 Timeout Process/Thread for step 2 died. SW: 2008-12-19 12:01:34.017 Tidying up SW: 2008-12-19 12:01:34.017 Process/thread 2 stopped SW: 2008-12-19 12:01:34.017 Watchdog expired SW: 2008-12-19 12:01:34.017 Waiting for process step 0 to terminate SW: 2008-12-19 12:01:34.017 Waiting for process step 1 to terminate SW: 2008-12-19 12:01:34.032 Thread for step 2 streamed 1306 blocks totalling 0 051951F (5346591) bytes SW: 2008-12-19 12:01:34.032 Socketwrapper has terminated. For me it looks like something makes transcoding work on the whole file at once (hence the high CPU in the beginning), and this is failing. My version is: Version: 7.3.1 - 24367 @ Thu Dec 18 10:00:25 PST 2008 Operating system: Windows Server 2003 - EN - cp1251 Platform Architecture: 586 Perl Version: 5.8.8 - MSWin32-x86-multi-thread MySQL Version: 5.0.22-community-nt I'm streaming flac to softsqueeze 3.7 on another machine. Bitrate limiting is configured to 160K, level 4.
SoftSqueeze has the same issues, see bug 10392, comment 5
Alan, does this make sense to you?
My guess is that something horrible is happening when using the socketwrapper on Windows. I have checked in a change in with bug 10451 to revert to 7.2 behaviour which makes less frequent use of Pipeline/socketwrapper.
James, can you test with 7.3.1 to confirm that you can reproduce this and then again with 7.3.2 to see if that fixes it?
Yuly has verified this is fixed with Change 24415
Verified fixed in SqueezeCenter 7.3.2 r24679 Controller 7.3 r3852
Fixed - Closed Message (SC) This bug has been fixed in the 7.3.3 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Correction: SqueezeCenter version is 7.3.2