Code for Philips HDRW720

[The Robman]

A-ha, gotchya.

[cliefan]

I updated the upgrade file with the discrete codes that I found. It is now uploaded under DVD and PVR.

I do have a question now that i have discrete codes to work with... do have to have the discrete code assigned to a button to use it in a macro? i dont want to use up valuable buttons on discrete codes just for a macro....and i dont see any macro options in IR.exe to send specific codes, only already assigned buttons...

[The Robman]

Macros are just a sequence of keystrokes, so yes, you do need to assign the function to a button in order to use it. Go back to KM or RM, whichever you used to create the upgrade, and see if there are any more buttons available in the device mode that you are using. If there are, why not assign the discrete functions to those buttons.

Alternatively, if you have some keymove space available, assign the discrete codes to phantom keys or shifted keys.

Finally, there is one way that you can use them in macros without assigning them to buttons, to do this you would include the SETUP button in the macro followed by the 3-digit EFC code. This method would use up 4 steps in a macro instead of one, and would use up 4 bytes of keymove/macro memory instead of 6 bytes, so it's not really saving much.

[cliefan]

how about this:

i create a fake upgrade and just use the External Functions from RM. Each of those functions can be a different discrete function.
For example, Discrete off for the HDRW720 would be device type DVD, setup Code from the upgrade i made(2004), then whatever EFC used for discrete off (062 in this case). Then assign that External Function to button 1 or something.
After adding all of the External Functions for more discrete codes and assigning the upgrade to one of my unused Device Buttons(SAT for example), I could create a macro for SAT > 1 > 2 > 3, etc, etc.

It would be like one Device Button dedicated to discrete codes.

Would this work or am I lost?

[cliefan]

how about this:

i create a fake upgrade and just use the External Functions from RM. Each of those functions can be a different discrete function.
For example, Discrete off for the HDRW720 would be device type DVD, setup Code from the upgrade i made(2004), then whatever EFC used for discrete off (062 in this case). Then assign that External Function to button 1 or something.
After adding all of the External Functions for more discrete codes and assigning the upgrade to one of my unused Device Buttons(SAT for example), I could create a macro for SAT > 1 > 2 > 3, etc, etc.

It would be like one Device Button dedicated to discrete codes.

Would this work or am I lost?

i jus tried this, and mapping external functions is just creating keymoves. I guess key moves would work, since you can assign an efc to them...

[The Robman]

I'm not really following all of this, but it sure looks like you are looking for the most complicated way to do something that's really simple.

Maybe if you re-state what your end goal is I would have a better idea of why you're trying to avoid doing it the simple way.

[Capn Trips]

I do have a question now that i have discrete codes to work with... do have to have the discrete code assigned to a button to use it in a macro? i dont want to use up valuable buttons on discrete codes just for a macro.......

As Rob said, it seems you're trying to make something simple harder.

Yes, the discrete functions must be assigned to a button to be subsequently used in a mcaro. If you believe assigning them to a "valuable" button within the body of an upgrade is wasteful (or you simply have no free buttons available) then you MUST create a Keymove, to either a "free" button not in the button map for the device selected, or a shifted, x-shifted, or phantom button, and then use this button in the macro. If you still believe that the six (or so) bytes "wasted" on the Keymove isn't worth it, then you obviously don't think the function is important enough. Are you THAT squeezed for Keymove/Macro memory space? If you are, perhaps if you post your IR file, someone can suggest some ways to reduce the amount of Keymove/Macro memory space you are using.

Your choice.

[cliefan]

http://www.keithspace.com/cliefan.ir

theres my IR file.

I think I have everything the way i want it, for now.

I used keymoves for the discrete codes i plan on using and made macros based on those.

I thought that if I did it this way, all the discrete codes would be in one place, but now that i think about it, that probably doesn't make that much sense, and probably uses more memory.

[Capn Trips]

I am a fan of the theory "if it works, don't fix it", BUT... as you have NO reliance on learned signals, you might want to consider using the extender. Amongst its immediate benefits that you will notice is MUCH FASTER MACROS!

Further, you will have much more Keymove/Macro memory (at the expense of NO learning memory), and access to several special protocols, that after a while you might find useful (ToadTog, L/DKP, Custom mode name, others).

You might want to read the extender readme to see if this is something you want to try for the "next level".

And it costs you nothing (but time ) as you can always reload your current working IR configuration.

[cliefan]

Cool.

I had assumed an extender was a piece of hardware from the few times i've seen it mentioned.

Faster macros would be nice.
If i start using an extender, but then need to learn a new device, i can still go back to the original configuration to do so, right?

[underquark]

If i start using an extender, but then need to learn a new device, i can still go back to the original configuration to do so, right?

Yes, so long as you save your existing setup, you can just re-load it again.