Discrete on and off codes are desirable for macros. They make it easier and less likely to cause confusion when creating power on and power off macros. (A single power command can make it possible to for someone to run a "power on" macro when one device is already on and end up with a mess.) As an example, I have two macros that make my wife much happier about the system. One macro turns on everything she needs to watch TV: it turns on the TV, the cable box, sets the 950 to Video3 (which also turns the 950 on), and sets the remote to control the cable box. Another macro turns everything off: sets the TV to DVI (another discrete code, which makes sure the TV is on the right input when it gets turned back on later -- I initially tried including it in the "power on" macro, but the TV takes a few seconds after turning on before it will accept remote inputs), turns the TV off, turns the cable box off, and turns the 950 off. It is possible to do macros like this without discrete on and off codes, but the discrete codes make it a bit more foolproof.

Actually, I think Outlaw was pretty slick to make every input command act as a discrete "on" command. On the down side, the "POWER" button's role as "off" only can throw some people at first, but on the up side you're going to need to hit an input command button anyway.

------------------
gonk -- 950 Review | LFM-1 Review | Pre/Pro Comparison Chart | Saloon Links