91
Users / Re: AV connections not being controlled
« on: March 17, 2010, 05:32:37 pm »No, what i'm saying is that after reload and regen, the amp turns on AND the correct input is selected.It sounds like you need to increase the "Number of miliseconds to wait for the device to warm up after sending a code to turn the power on" setting on the device template.
That's ok.
If i change the input (.i.e from Lasedisc to Tuner), turn the amp off and play an audio or video file, the amp turns on but the input does not change to Laserdisc.
If that doesn't do it, please detail exactly what steps you are taking to run into this issue. I want to know what buttons you are pushing and where they are for each step. Something like this:
Code: [Select]
1) reload orbiter from web admin
2) activate "Live TV Digital Cable" scenario from n810 orbiter - this causes TV to turn on and input is switched to AV3
3) Turn off TV using "Display Off" on on-screen orbiter
4) ... etc
The amp is controlled only via IR (does not have RS-232 connection). So, it doesn't matter if it's on or off, the IR always sends the "turn on" code.
Are you saying that you have separate and different On and Off IR codes? The bottom line is this - if LinuxMCE thinks a device is in the proper state (power and input selection) then it will not send any IR commands. If you don't have separate On and Off codes because your A/V gear doesn't support it, then On and Off look the same to the equipment, so the state will be confused. The same is true for input selection if you don't have discrete input codes. This is why you should avoid using your IR remote controls to control your AV devices.
Ok, got it. But i was thinking that also turnning the play/view OFF would do it, or at least at floorplan.LinuxMCE supports either behavior.
It means that if i leave the TV on, with the screen saver running and no media paying, the amp should stay ON. Is this behavior right?
The default is to leave A/V gear on (displaying the on-screen menu and screen saver) for a specified amount of idle time. If that time is exceeded, then everything is automatically powered down. You can configure the time on the "Orbiters" page in the web admin (Wizard --> Devices --> Orbiters, "Seconds before power off" setting). This setting has no effect for Orbiters other than "on-screen" orbiters, by the way.
The other mode will power everything down as soon as playback has ended. Activate this by un-checking the "Leave Monitor on for OSD" setting on the Orbiter's device page (Wizard --> Devices --> Orbiters, Advanced, "Leave Monitor on for OSD" setting).
You will have to reload the router and possibly regen the orbiter for these changes to take effect.