Bug 1231 - Browser refresh causes AAC cut-offs
: Browser refresh causes AAC cut-offs
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Audio
: 6.0.0
: All All
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-29 11:07 UTC by Michael Robinson
Modified: 2008-08-18 10:54 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 Michael Robinson 2005-03-29 11:07:39 UTC
I get audio cut-offs on AAC files when the browser displaying the SlimServer
web interface does a refresh � either the default 30 second browser refresh
or a manual refresh.

The problem happens with Safari, Firefox and Internet Explorer.

System is:- G4 iMac OSX 10.3.8, SlimServer 6.0.0 using iTunes 4.7.1,
Squeezebox (using wireless)

The problem happens when playing an AAC file � it doesn't happen
when playing a MP3 file.

The problem doesn't appear to be related to the size of playlist � it
happens with one file in the playlist.

Looking at the Mac activity monitor, when a refresh happens, the browser
seems to grab well over 50% of the real time and the CPU maxes out.

The cut-offs only appear to happen when the SlimServer web interface is
refreshed � I don't get cut-offs when refreshing another web-pages.

Problem occurs on 5.4.0, 5.4.1 and 6.0.0.

Problem has also been posted on Discuss bulletins see:-

http://lists.slimdevices.com/archives/discuss/2005-March/046254.html
http://lists.slimdevices.com/archives/discuss/2005-March/046349.html (contains debug info)
Comment 1 Dan Sully 2005-04-07 18:49:30 UTC
I'm going to have another pass at optimizing this further.
Comment 2 Blackketter Dean 2005-06-10 16:20:02 UTC
Dan thinks that putting the playlists in the database will improve this.
Comment 3 Dan Sully 2005-06-24 11:03:18 UTC
Michael - can you please see if this has been fixed in the 6.1 branch?

Thanks.
Comment 4 Chris Owens 2008-03-11 11:28:03 UTC
This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!