Squeezeplay Linux

[Wiredcharlie]

I'm running Squeezeplay on an O2 Joggler. What I would like to do is run Squeezeslave in the background and merely use Squeezeplay as an occasional controller. How do I disable the PLAY part of SqueezePLAY?

OR

To look at it another way, is there a way of running the PLAY part of SqueezePLAY in the background?

Much appreciated

Tony

[aubuti]

Not sure I follow you, but what's wrong with using regular Squeezeplay, and using Choose Player to choose the squeezeslave player? That's the usual way to separate the controller function from the player function.

[Wiredcharlie]

This is the Joggler:

http://yourfamily.o2.co.uk/o2familyjoggler/

It doesn't have a multitasking interface, but I want it to be available to play all the time without having duplicate players on the same machine.

[MusicManiac]

There really isn't a way to "disable" the playback ability of Squeezeplay.

Your mention of running Squeezeslave in the background and then controlling it with Squeezeplay will work fine. Just use the "Choose Player" option in Squeezeplay to pick Squeezeslave - it will remember what player you used last when you open it back up.

-mm

Edit: ah, two players showing up for one machine, yeah I don't think you're going to be able to get around that. Not to my knowledge anyway.

[ralphy]

There really isn't a way to "disable" the playback ability of Squeezeplay.

Your mention of running Squeezeslave in the background and then controlling it with Squeezeplay will work fine. Just use the "Choose Player" option in Squeezeplay to pick Squeezeslave - it will remember what player you used last when you open it back up.

-mm

Edit: ah, two players showing up for one machine, yeah I don't think you're going to be able to get around that. Not to my knowledge anyway.

Change the MAC address using the -m option when you start squeezeslave and you'll be all set.

squeezeslave -R -M/var/tmp/ss.log -m00:00:00:00:00:99 sbshostname

Would be my recommendation.

See squeezeslave -h for all the details.

EDIT: You could also use /dev/null in place of /var/tmp/ss.log if you don't care about errors.

[Wiredcharlie]

Thanks guys. But please understand that my difficulty is not making Squeezeslave work or Squeezeplay. I can do that. What I want, is to allow squeezeslave to run in the background, and simply use Squeezeplay as an occasional controller without it running a second player on the same machine.
ie How do I disable Squeezeplay's player?

Tony

[MusicManiac]

Thanks guys. But please understand that my difficulty is not making Squeezeslave work or Squeezeplay. I can do that. What I want, is to allow squeezeslave to run in the background, and simply use Squeezeplay as an occasional controller without it running a second player on the same machine.
ie How do I disable Squeezeplay's player?Tony

Sorry Tony, like I mentioned before, I don't think you can do with Squeezeplay what youre asking. As long as Squeezeplay is running it will always show up as an avalible player.

I'm not aware of anyway to disable playback or modify to do so. (I've never looked at the code though).

Your best bet is going to be to follow Ralphys instructions, and then rename the two running players distinctively. Then just ignore the 'dead' player.

[aubuti]

I'm not aware of anyway to disable playback or modify to do so. (I've never looked at the code though).

It's may be possible to do it, just as playback can be enabled/disabled on the SB Duet Controller, which like Squeezeplay, is a SqueezeOS device. But it would probably take a good bit of hacking the SqueezePlay code to achieve that.

[JohnSwenson]

Why do you want to "get rid of the player"? If the player part is not playing anything its not using up network or CPU resources. The only issue is that it shows up in the list as an available player. If you absolutely can't live with that the easiest way prevent it showing up is to turn off the discovery part of the code so the server won't see it. I haven't looked at it recently so I can't tell you exactly how to do that, but its probably accessible through the lua code somewhere so it should be easy to modify (once you find out where it is).

If your objective is to cut down on the code size, that's tough. Squeezeplay is one program that does it all, to cut down on the size of the program you have to hack away at the source code and recompile, not a trivial task.

John S.