News:

Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com

Main Menu

8.10 + SqueezeBox + Cant play audio via LMCE

Started by essem_9, April 15, 2012, 02:54:41 AM

Previous topic - Next topic

essem_9

Just received my new squeezebox yesterday and follow the instructions on the wiki to set it up (pretty much plug and play). The core configured it as soon as the box booted up (over Ethernet). I mapped it to the kitchen. From my core on-screen orbiter, choose kitchen-->audio-->selected music. There was no audio :(. Since my audio is on the NAS, i moved over a file to /home/public/data/audio/. Still no luck.

Under the Device Tree I see Slim Server Streamer (Registered). Under that i see SqueezeBox Player (it sure is mapped to the kitchen)

Navigated to Advanced-->Configuration-->SqueezeBox Server, it only shows Loading SqueezeBox Server. Navigated to 192.168.80.1:9000 and the UI did show up. I could play music on the box from /home/public/data/audio/. In the settings-->Information tab i do see the following:
Player Model: Squeezebox Radio
Firmware: 7.6.1-r9482
Player IP Address: 192.168.80.146
Player MAC Address: xx:xx:xx:xx:xx:xx

So it seems the Squeezebox is connected and can be controlled by the server. But not sure why i cant play music via the orbiter.

ps -ef |grep Slim
shiv     17578 23303  0 17:52 pts/32   00:00:00 grep Slim
root     20349     1  0 17:16 ?        00:00:00 /usr/bin/SCREEN -d -m -S Slim_Server_Streamer130 /usr/pluto/bin/Spawn_Device.sh 130 localhost LaunchSlimServer.sh
root     20352 20349  0 17:16 pts/19   00:00:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 130 localhost LaunchSlimServer.sh
root     20419 20352  0 17:16 pts/19   00:00:00 /bin/bash /usr/pluto/bin/LaunchSlimServer.sh -d 130 -r localhost -l /var/log/pluto/130_LaunchSlimServer.sh.log
root     20424 20419  0 17:16 pts/19   00:00:00 ./Slim_Server_Streamer -d 130

Any help will be appreciated Thanks!




Gangsingen

I had the same problem with my 10.04 install. The CLI (Command Line Interface) should be activated and set to port 9090.

essem_9

Gangsingen,
I have tried using 9090 as well as 7890 as recommended on the Wiki with no luck. However I did notice the following:

1. Navigating through Advance-->Configuration-->Squeezebox Server does not display the page. So i browsed via 192.168.80.1:9000
2. Navigated to Settings-->Plugins-->CLI
3. Here the Radio button is checked, however it is greyed out. Which means i can't enable/disable it. Is that expected?
4. I sure can click on settings and see that the port is set to 9090
But i am not sure if it is enabled since the radio button is checked but greyed out. Any thoughts?

Following is the SqueezeBox Server Info
Version: 7.6.1 - r33110 @ Wed Aug 17 18:50:10 PDT 2011
Hostname: dcerouter
Server IP Address: 192.168.2.199
Server HTTP Port Number: 9000
Operating system: Debian - C - utf8
Platform Architecture: i686-linux
Perl Version: 5.10.0 - i486-linux-gnu-thread-multi
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 1

Techstyle

I set mine up earlier tonight and have the same info as you in 1-4. with the following server info:

Version: 7.6.1 - r33110 @ Wed Aug 17 18:50:10 PDT 2011
Hostname: dcerouter
Server IP Address: xxx.xxx.xxx.xxx
Server HTTP Port Number: 9000
Operating system: Debian - C - utf8
Platform Architecture: i686-linux
Perl Version: 5.10.0 - i486-linux-gnu-thread-multi
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 1

My server IP address is my external address - is this the same for you?  is 192.168.2.199 listed under webadmin network settings under the external IP Address?

if you browse to 192.168.80.1:9000 and then start something playing on the orbiter can you see it start on the server web page?  in the top right hand corner is the player name listed?
Techstyle UK Ltd
[url=http://www.techstyleuk.co.uk]http://www.techstyleuk.co.uk[/url]

Techstyle US Inc.
[url=http://www.techstyleus.com]http://www.techstyleus.com[/url]

essem_9

Yes, 192.168.2.199 is the external IP address of my core. I am currently traveling and will test display on the server webpage this weekend and report back. Is the setup working for you?

Techstyle

Techstyle UK Ltd
[url=http://www.techstyleuk.co.uk]http://www.techstyleuk.co.uk[/url]

Techstyle US Inc.
[url=http://www.techstyleus.com]http://www.techstyleus.com[/url]

essem_9

The top right hand corner always shows "Squeezebox Radio". There is no other option in the drop down list.

I took wired traces and I can see the Slimdevice messages go by. I had deleted the device numerous times in the past. This time I deleted the device and added it to the Garage as opposed to the Kitchen. To my amazement it started to work. Not sure what was wrong setting it in the Kitchen. Probably some orbiter settings. Will probably dig a deeper later but for now I can at least enjoy some music. Thank you folks!

Marie.O

Did you already have a MD in the kitchen? Only one MD per room is allowed.
If I helped you, feel free to buy me a coffee: [url="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2VKASZLTJH7ES"]https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2VKASZLTJH7ES[/url]

essem_9

I do not have any devices in the kitchen. I had first installed the squeezebox in the office. When I started to play audio, it started on my core. It made sense that only one device is allowed since Audio is a generic button. Moved it to the kitchen by deleting it numerous times. I may have goofed up some where I guess.

Intially I thought it was because of my setup with eth0 and eth0.80. Using a single interface with VLAN tagging and eth0.80 being the internal network. I added another NIC and it still did not work.

Finally moving it to garage worked. So now I am back to using one NIC with vlan tagging and alls well so far. Have rebooted the core as well as the squeezebox and it works. Thanks!

essem_9

posde,
After your post, I took a closer look all my devices and found the issue. Your were right. While I was testing PXE Boot of a MD, I had assigned it to the kitchen. Even though the MD was a temporary test unit and not there anymore, it was in the devices list mapped to the kitchen. That solves the mystery. Appreciate your input. Thanks!

Marie.O

Nice! Thanks for reporting back.
If I helped you, feel free to buy me a coffee: [url="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2VKASZLTJH7ES"]https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2VKASZLTJH7ES[/url]