Bugzilla – Bug 273
streaming audio skips under 5.1.5
Last modified: 2008-09-15 14:37:04 UTC
after upgrading to 5.1.5 (from 5.1.1) I found that streaming to a software mp3 player now exibits significant skipping in the audio. (It worked fine in 5.1.1) This happens regardless of streaming rate, and even with "magic downsample" disabled (no re-encoding). It happens when streaming to localhost, suggesting it's not a bandwidth issue. There is no significant load on the cpus either. I typically use xmms under linux, but I tested with a few other players as well just to verify it (probably) isn't a client issue. Latest cvs (as of April 22nd) exibits this same problem. This has been mentioned by some people on the mailing lists as well. Please let me know if I can provide any additional information that would help in fixing this.
as an extra datapoint, I tested the 5.1.3 server today, and it exibits the same bug that 5.1.5 does. So this bug seems to have crept in between the 5.1.1 and 5.1.3 releases.
To help narrow this down some, I've been checking the code out of cvs for various dates between the 5.1.1 and 5.1.5 release. The problem seems to have crept in between 2004/3/5 and 2004/3/6. I couldn't help but notice that this is also the same time that bug 272 showed up. Perhaps something in the networking/streaming code?
I had same problem with xmms and 5.1.5 on FreeBSD 5.2.1. Version 5.1.1 was the last that worked reliably for me. Seems my xmms didn't like the capitalisation on some of the HTTP headers being sent back when the stream is started. You can try commenting out line 114 of CPAN/HTTP/Headers.pm or putting a line that says $data =~ s/^(Icy-.+\:)/\L$1/mg; at line 834 (before the return $data;) in Slim/Web/HTTP.pm to see if that fixes it for you. Either fudge worked for me.
Wow, thanks for that Greg. I'll add that patch to CVS. Michael: can you test it?
I just updated from cvs, and it's working great again. Thanks!
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.