I'm with Kelly and prefer to not use variables. When using IR only remotes, sometimes even with the best of programming, sometimes a device misses a code. Then when hitting on again to correct it, the variable causes a problem. And the only way to fix it is press off and then start over.

Then sell a rf base.

And it's still not perfect. Interference can cause an RF signal to be lost, the device just missed the signal from the flasher, crap happens. Variables are great, but don't let a system self correct if something goes wrong.

Sell rf base and set it up properly. No rf interference and reliable control system.

Disclaimer: helps to be sober during setup ;-D

If you aren't at least using variables to cut out long delays in macros when they aren't necessary, then you are doing a disservice to your clients.  Nobody wants to wait 20 seconds between switching back and forth between sources.  If you can't make that reliable, then you need to work on your programming skills.

Other than projectors, most products now have very quick turn ons. So long delays are rarely needed. Even with a projector, if I put a short 1 or 2 second delay to handle switching AVR inputs, or no delay at all, if the projector is already hot, then great, everything keeps moving. But if the projector is warming up, still fine too, because the projector forces the client to wait, even if the remote is already at the device page.

I've had brand new TVs in the past year that had over 10 second power on delays.

I've seen 18 seconds on a 24" samsung.

No, not fine in many cases. If the projector is warming up, it probably will not respond to an input change command. If the client has already selected a source, and that macro changes the projector input, he will be sitting with the wrong input on the projector but the input controls he wants on his remote.

The few times I've used variables it has been to solve exactly this sort of problem. It has worked with no flaws. I don't get the objection to variables.

If you are changing inputs on a projector, you are designing antiquated systems.

When Ernie is the one making sense, it's time to pack up and head for higher ground.

so now we are talking system design?  what makes you think that we all design the systems we are tasked with controlling?  variables serve a purpose.  if you can't agree to that, then you are working with an antiquated brain.

In some situations, variables are the only option.

Here, I fixed it for you:


Maybe I'm not good at programming, and as a result I've tried the programs so many times by the time I'm finished that I seem to be able to weed out the occasional bad codes... or something. Anyway, my customers' systems somehow don't miss codes unless their big dog walks between them and the system.

I use variables on nearly all of my configurations. But probably 95% of that usage is to minimize delays on changing the input to the display device. It's not like it is that difficult. Probably adds 3-4 mins to the entire programming (especially with copy and paste available)

I never use variables to track TOADS. If you guys are successful at that, bully for you. I've never been able to make it work. I tell the customer that I simply can't automate power to a toad device. I guess I must be lazy.

As to the original poster...I think he is spoofing or punking us. Why you guys bother, is beyond me...well...I know why Ernie bothers. Because he has no life.