Bug 274 - Transcoding mp3 files results in intermittent problems accessing web interface
: Transcoding mp3 files results in intermittent problems accessing web interface
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: unspecified
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-04-23 03:58 UTC by John Gorst
Modified: 2009-09-08 09:28 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 John Gorst 2004-04-23 03:58:54 UTC
Server: 5.1.5, Windows XP,
Client: softsqueeze or winamp

Happens when:  transcoding is enabled (through new web interface setting or by
stream.mp3?bitrate= settting)

Causes: Intermittent failure of web interface elements to load up. Particuarly
affects 'handheld' skin, especially when clicking on 'next' on the status page.
Sometimes nothing will happen when 'next' is clicked, sometimes the webpage will
refresh but the album art will fail to load. The browser just dispalys
'connecting to 127.0.0.1....'. Happens with a range of browsers.

Tried: virgin install, not using itunes play file, upgrading to latest lame
version, installing lame within slimserver directory tree

Dubug log: The following error occurs in the debug log when using 'handheld skin':
Error writing mp3 output 
ID3v2 found. Be aware that the ID3 tag is currently lost when transcoding.
The following error occurs when 'default' skin is used, however the fault
happens very rarely in this skin:
file error - 1: not found
Error writing mp3 output 
file error - 1: not found
ID3v2 found. Be aware that the ID3 tag is currently lost when transcoding.
Comment 1 Vidur Apparao 2004-06-05 14:41:51 UTC
*** Bug 336 has been marked as a duplicate of this bug. ***
Comment 2 John Gorst 2004-06-07 23:51:43 UTC
Update: 
- nothing now appears in the debug log when this error occurs so I suspect that
was a different bug that has now been fixed in a recent )actually quite an old)
nightly.
- this error occurs when converting from flac --> wav as well as downsamping MP3
files
Comment 3 Vidur Apparao 2004-06-11 10:45:47 UTC
This is a really curious one. I was able to recreate it and trace it to the way
we're doing HTTP keepalive. I can see what's happening at the packet level, but
why it happens only when we're transcoding and only with specific skins is
beyond me.

Either way, I just checked in a fix to our HTTP keepalive implementation (with
help from Dan Sully). This seems to fix the problem.

I'm closing this bug with my 6/11/2004 checkin to HTTP.pm. John, please confirm
that it works for you with the latest from CVS or tomorrow's nightlies.
Comment 4 John Gorst 2004-06-11 12:37:30 UTC
Seems the bug has settled on teh SlimServer_v2004-06-11.exe  nightly which I
assume does not include your patch? Strange! I will keep a close eye out for it
over the next few days!
Comment 5 John Gorst 2004-06-12 11:09:11 UTC
SlimServer_v2004-06-11.exe seems to have resolved all problems.

Playback on softsqueeze and Winamp (via strem.mp3) for flac-->wav, flac-->mp3
and mp3-->mp3(lower bitrate) all seem to work. The problems with the web
interface not loading up are all sorted!

Thaanks
Comment 6 Chris Owens 2007-05-24 15:54:09 UTC
This Slimserver bug was fixed a very long time ago, and is now being marked as Closed.  If you're still experiencing this issue, please verify you are running a current version of Slimserver and re-open the bug.