I was interested in getting Onkyo TX-SR702 and was wondering if I
needed to insert a pause after discreteOn before sending the discrete
input select. (ie some devices will not accept IR commands for a brief
period after they are first turned on) Also how long of a pause.
I already have some devices which behave this way on my current remote
and have cobbled together a mesh of toadtogs and pause macros to
handle it and would prefer a nice simple device for once.
Newer Sony receivers treat the discrete input select button as both input
select and discrete on, so that results in nice quick response in my system
all on macros.
I figure most newer Onkyo's will behave similar so any comments from
Onkyo users would be appreciated.
Thanks.
Do Onkyo rcvrs need pause after discreteOn for input select?
Moderator: Moderators
Re: Do Onkyo rcvrs need pause after discreteOn for input sel
In case anyone is curious, the Onkyo TX-SR702 behaves just like the Sony.sfhub wrote:Newer Sony receivers treat the discrete input select button as both input
select and discrete on, so that results in nice quick response in my system
all on macros.
The input select has dual function of "DiscreteOn" and input select.
Thus if you choose "discrete input - DVD", the unit will perform
1) discrete On
2) select DVD input
There is also an independent DiscreteOn. I didn't test whether it requires
a pause or not before the unit will recognize a discrete input select.
I didn't scan the entire IR range, but I don't believe the unit has a power
toggle function, only DiscreteOn and DiscreteOff, so if you want power
toggle, it needs to be simulated with toadtogs.
I have the Onkyo TX-SR700 which is similar but a couple of revisions older than the 702.
I have not seen the need to insert any delays between power up and selecting an input. I have several macros that put these right next to each other, and nary a problem.
I tried to see if mine also had the behavior described above that the discrete input selects also include a power on; but based on my testing it does not do this.
I have not seen the need to insert any delays between power up and selecting an input. I have several macros that put these right next to each other, and nary a problem.
I tried to see if mine also had the behavior described above that the discrete input selects also include a power on; but based on my testing it does not do this.