View Full Version : Can stream MP3 but not WMA to Squeezebox

2005-07-17, 19:00
I've been searching the forums for a similar problem, but haven't found anything similar outside of AlienBBC problems.

From SlimServer 6.0.2 (and 6.1b2) on Windows XP SP2, I am able to stream MP3 but not WMA from the internet to my SB. There seems to be a problem when passing the stream from wmadec.exe to lame.exe.

Since it's an SB, MP3 (from http://radioio.sc.llnwd.net:8465/) is streamed directly. However, when I stream WMA (from http://radioio.wm.llnwd.net/radioio_70sPop_med), it involves socketwrapper, wmadec and lame. Both streams do work in Windows Media Player.

The debug log for the mms streaming looks good until:
2005-07-17 19:35:30.9768 Pipeline reader connected
2005-07-17 19:35:30.9839 We need to send 0 seconds of silence...
2005-07-17 19:35:30.9841 sending 0 bytes of silence
2005-07-17 19:35:30.9845 would have blocked, will try again later
[repeats until]
2005-07-17 19:35:35.3888 readlen undef: (Unknown error)10054

And the command line output:
Assuming raw pcm input file : Forcing byte-swapping
Error writing mp3 output

I have two Windows XP Pro computers, and this only happens on the one with SP2.

2005-07-20, 13:10
Could it be that firewall settings on your SP2 machine is preventing outgoing connections from wmadec?

2005-07-20, 16:05
I turned off the firewall and got the same results. I set wmadec.exe as an excepted application and still had the problem.

The following command actually created an mp3 file for me, so I may be having some problem with socketwrapper:

C:\PROGRA~1\SlimServer\Bin\MSWin32-x86-multi-thread\wmadec.exe -r 44100 -b 16 -n 2 "mms://radioio.wm.llnwd.net/radioio_70sPop_med?MSWMExt=.asf" | C:\PROGRA~1\SlimServer\Bin\MSWin32-x86-multi-thread\lame.exe -x --resample 44100 --silent -q 9 -b 320 - - > file.mp3

2005-07-25, 18:42
I'm still having problems with a fresh install of 6.1.1. Any ideas?

2005-08-05, 06:55
I'm still having problems with a fresh install of 6.1.1. Any ideas?Could this be related to the issue described in the bug I filed this morning?