Actually, discrete codes are more simple than Tony's explanation. A discrete ON code can ONLY turn a component on and a discrete OFF code can ONLY turn a component off.
So, your TV is already on and you send it a discrete ON code, it will remain on. It will not toggle off as it would with the standard power button the factory remote. Likewise, if the TV is off and you send it discrete ON code, it will turn on.
Reverse it for the discrete OFF code. It will only turn off a component that is already on because that code can do is turn it off.
Discrete codes are very important for Macros. A Macro is a string of different commands sent via a single button press. For instance, you might set up a Macro to:
1) Turn on the TV
2) Set the TV to Digital Input 1
3) Turn on the A/V Receiver
4) Set the A/V Receiver to DVD
5) Turn on the DVD player
6) Eject the DVD disc tray, readying it for a DVD disc.
If you don't have discrete codes for your components, in the above example, if the TV, AV/Receiver or DVD player is already ON before you send the Macro, the standard power toggle would turn those items off.
Conversely, with a discrete ON code for each component, the TV or other component could be ON and when it receives the discrete ON code it would simply remain on.
Now, the reason this is all very important to the discussion of URC's software policy change is this.... Very very few factory remotes have discrete ON or OFF codes in them. In most cases, you get those discrete codes from the DATABASE of IR codes that URC supplies with their software. Said database is the thing that gets updated when you use "Live Update" in the URC MX Editor software. No "Live Update" feature means you can't get access to any newer codes that URC might have added for newer components.
Yes, there are other ways to get the discrete codes. But much of the "power" of the URC software and the PC-programability of their remotes lies in that extensive collection of IR codes in that database. A database that is constantly being updated. A database who's updates are NOT available to folks saddled with the "No Live Update" version of the software.
Mark
So, your TV is already on and you send it a discrete ON code, it will remain on. It will not toggle off as it would with the standard power button the factory remote. Likewise, if the TV is off and you send it discrete ON code, it will turn on.
Reverse it for the discrete OFF code. It will only turn off a component that is already on because that code can do is turn it off.
Discrete codes are very important for Macros. A Macro is a string of different commands sent via a single button press. For instance, you might set up a Macro to:
1) Turn on the TV
2) Set the TV to Digital Input 1
3) Turn on the A/V Receiver
4) Set the A/V Receiver to DVD
5) Turn on the DVD player
6) Eject the DVD disc tray, readying it for a DVD disc.
If you don't have discrete codes for your components, in the above example, if the TV, AV/Receiver or DVD player is already ON before you send the Macro, the standard power toggle would turn those items off.
Conversely, with a discrete ON code for each component, the TV or other component could be ON and when it receives the discrete ON code it would simply remain on.
Now, the reason this is all very important to the discussion of URC's software policy change is this.... Very very few factory remotes have discrete ON or OFF codes in them. In most cases, you get those discrete codes from the DATABASE of IR codes that URC supplies with their software. Said database is the thing that gets updated when you use "Live Update" in the URC MX Editor software. No "Live Update" feature means you can't get access to any newer codes that URC might have added for newer components.
Yes, there are other ways to get the discrete codes. But much of the "power" of the URC software and the PC-programability of their remotes lies in that extensive collection of IR codes in that database. A database that is constantly being updated. A database who's updates are NOT available to folks saddled with the "No Live Update" version of the software.
Mark

















