howto keep a pipe active

[Esperanto]

Anyone can tell me how I can make sure a pipe stays on/active even after the normal devices stop using it? So some kind of parallel dummy device that uses the pipe and stays active until stopped manually.

[Marie.O]

what do you want to achieve?

[Esperanto]

I want my amp to stay on if I still use it (parallel to lmce via pulseaudio)

[Marie.O]

Remove the off command from the device template of your amp, or change the timeout of turning the device off. Or do the right thing and create a device for your application that is part of LinuxMCE.

[Esperanto]

Or do the right thing and create a device for your application that is part of LinuxMCE.

Thats what I meant when I asked for 'some kind of parallel dummy device that uses the pipe and stays active until stopped manually. I have no idea how to do that or if that is at all possible. Any suggestions on how to realize that? (is there an example template I can use to base it on?) I _think_ it needs to create a media entry on the orbiter (to turn it on and off), be able to use (audio) pipes and be able to function parallel to the other activities.

[Marie.O]

I did not say dummy device, but a REAL device that controls whatever you want to run.

[Esperanto]

There is not really anything that has to be controlled since it just using pulseaudio and not changing anything. However for that the Audio pipes need to stay active.

[Marie.O]

It has to start something, and end something. So it needs to do stuff. Create such a device and everything else falls in place.

[Esperanto]

That's what I have been trying to say: it does not need to do anything (since all is configured by default at startup, that is the audio system is started) except making sure that the pipes are still in use.

[Marie.O]

Do not take a shortcut. Create a new device <--- that means: Coding! that will call what ever you need to call that needs audio pipes set up. There is no shortcut to it.

[Esperanto]

I am not taking any shortcuts. I just want to know how to create the device I described. The device will do nothing (since there is nothing to be done for the device) except setting the pipes as used. And it needs to do that without interfering with the other media playing on the MD. This is no shortcut, this is all that I need. But I still have no idea if it is possible and/or where to start.....

[pigdog]

Hi,

If you are trying to respond to an event type of thing...

http://wiki.linuxmce.org/index.php/Respond_to_Events

...maybe that'll help.

[Esperanto]

It's not really events.

What I envision is:

- an off/on button in the media menu on the orbiter
- a entry in the A/V Equipment list so the pipes can be configured (that get set active/inactive by the on/off buttons)
- be able to use it parallel to/simultaneously with other media (so it should not block the MD)

Beside this there is _no_ functionality, so nothing that needs to be controlled or done.

Is this possible? and if so where to start?

[bulek]

Hello,

I'm not sure, but quite some time ago I did few devices as GSD devices (you write few pieces of code in Ruby)...

You have Initialize, Release, and then IDLE method that gets called every few seconds... You can specify which commands you'll receive with your device, you can register to receive events, ....

Few links :
http://wiki.linuxmce.org/index.php/GSD

This is what I did (probably outdated info):
http://wiki.linuxmce.org/index.php/Marantz_SR5600#Pipes_can_be_connected_only_to_one_device

There is also some work done with external Perl script that connects to LMCE and performs as device...
http://wiki.linuxmce.org/index.php/Misterhouse (probably outdated too)...


HTH,
Regards,
Bulek.