Question about LKP on 8910

[Jon]

I'm pretty new to this whole JP1 thing & I'm not setting anything fancy up here, actually I think for the most part I've got my remote set up the way I want it. I'm using the ext1 extender on the remote which is great but I have three buttons set up to use the LKP feature (DVD, CD, CBL) but when I press them once (regardless of time) it just selects the device, if I press it again it works the macro I want. Is this how this should work? The way I would like it to work is if I just press once normally (quickly) it selects, but if I press & hold (the first time) it would run the macro. I uploaded my .ir file if someone would like to look at it & tell me what I'm doing wrong. Thanks.

http://www.hifi-remote.com/forums/dload ... le_id=3584

Jon

Would just like to add that without the amazing knowledge/help on this site I would've thrown this remote out the window a day after I had it, along with my sanity!!

[pH7_jp1]

Key moves are device specific, so if you are in a mode other than CBL and press the CBL button, the keymove (with LKP) is not seen and the macro on CBL is found and executed. After that happens and you press the CBL button again, since you are in CBL mode then the keymove is found first and executed as you expect.

Instead you want the macro on the CBL button to force the mode with DEV_CBL and execute a key that has the LKP. This will require that the current macro on CBL be moved somewhere else and used in the Long portion of the LKP.

[ElizabethD]

Is this how this should work?

Freedom reigns here. But if that's what it does, then, well ... You know how it is with computers. They always seem to do what you coded, not what you want.
Yeah, it's one of the classic designs, with power included on the device buttons.

Instead of coding CD/CD=LKP(4)... in the Special Protocols keymoves, put your LKP on a phantom key or some xShift key, making it:
CD/xShift-Phantom3 = LKP(4)...
Then call that at the end of the CD macro:
CD = DEV_CD ....Set_Vol_Keys;xShift-Phantom3
That way, when you press the CD button quickly, you'll get the key sets, otherwise you'll run the long side, precisely what you describe you want.

Suggestion: if you're using the same SET commands in all devices, you can save a heap of space if in the device macros you just call xShift-phantom1, which already contains your custom name shift-phantom3 job, so your device macros macros could be:
CD = DEV_CD;xShift-phantom1;xShift-Phantom3

Repeat the same idea for the others devices. And keep up the notes, this was a joy to read

You may need to tweak that idea, however, if slightly different key sets are needed for each device. The point is to reuse what you coded once before (to the extent possible).

[Capn Trips]

The two answers above are correct, but perhaps you're not seeing your problem clearly (no offense, Liz and Ph7 )

You have TWO COMMANDS (coonflicting? intentional?) assigned to your device buttons.

You have a (1) Device Selection Macro, and a (2) LKP on each one.

Liz has explained that the MACRO will normally get executed when you first press a device button, and the LKP will only be executed AFTER you are in the applicable device mode.

It sounds like you want BOTH the device selection to occur AND the LKP to run when you prepss a device button, correct?

Liz's solution is correct.

[Jon]

Liz's solution is correct.

...and they say women don't understand men..lol

Thanks for your quick responses, you guys are the best!
This seems to have done the trick, however.... not sure if this is normal but I had to put the 'dev_cancel' function in before the 'phantom' call for it work (without that it never executed the LKP portion). But now with it, when I just press to select say the 'CBL' button instead of just the one quick blink of the light it does a couple little flashes also, it doesn't seem to cause any other real actions as far as the components are concerned, but I was just wondering if this is normal, otherwise it seems to work correct.

The only other problem I seem to have now is the lack of a real discrete code for the power on function of the Toshiba DVD player, pressing the play button turns it on but then it starts playing the disc after it comes on. I had tried putting a 'pause' in between pressing the play button & the stop button but it's not nearly long enough, I think it has to be a good 10 seconds or so otherwise it's not seen while the DVD player is still starting up. Obviously the actual discrete code would be the best for this but I can't seem to find it & contacting Toshiba's tech support they tell me I need to be a professional installer (what kind of bs it that?). I will be posting looking for the code elsewhere on the site though to see if someone else may have it to share. And yes I checked on the www.hifi-remote.com/ofa/adv-codes.shtml page.

My updated .ir file has been uploaded if you want to check out the changes & see if you have any ideas on the DVD power issue or anything else.

Thanks again!

Jon

[ElizabethD]

Many DVDs do not have discrete power. I gather from this forum that Toshiba is a poster child. Play or Open tray plus Stop can be used instead. Delay in the DVD listening to a command can cause problems, as I think you're reporting. Use the Pause Protocol from KM or RM instead of the one in the extender which is just too short.

For Off on DVD, you can use Play + power. Here the problem might be that DVD won't remember where it stopped, but it might be just my situation.

If you want to work really hard now and redesign a bit, use ToadTog protocol to simulate discreteON/OFF. It's probably the biggest step to figure out and use. You'll use the Power code from upgrades, but the clever extender software will be watching it and, for the most part, doing the right thing. The price is that you will need to build new keymoves, replace them in the LKP side, and replace Power commands by DiscreteOFF in the Power macro.

Examples:
>> Special protocol keymoves for CD here on Shift-0/1, use anything you want instead, phantoms are good (same for other devices, just change the ToadTog number from 3 to any 0-7)
CD SHIFT-0 ToadTog(3,ForceOff) [On/Off]:SHIFT-Power [Already Off]:< Blank >
CD SHIFT-1 ToadTog(3,ForceOn) [Already On]:< Blank > [Off/On]:SHIFT-Power

>> Macro on Power (you need just one of those, as common code, on any old key if you don't like phantom3).
Power DEV_AUD;Phantom3

>> Special Protocol on Phantom3 to use in the macro above (one for all devices, use DSM for exceptions)
RCVR/AMP Phantom3 LKP(3)
LKP sections:
[Short]:Dev_Cancel;SHIFT-Power
[Long]:<here list all your power off discretes for all/most devices, ex. Dev_CD;SHIFT-0;Dev_TV;SHIFT-0 ...;DEV_AUD;SHIFT-0>

Dev_Cancel on the short side is essential to toggle the calling/active device only (I have one on both sides, but I think is not needed).
Short press is used, in this scheme, for just toggling the power in case it falls out of synch (remote thinks it's on but the DVD is off 'cause you got two remotes or too many people messing with the equipment)

Re Your second file:
I was going to help, but got lost in your second file. Sorry. I get lost in my own. These thing are tough to learn to read.
I decided it's simpler to think about the earlier one. Fewer changes to try.
So, looking at your original file, I would retain your set,set,set phantoms, at least the first one, and have macros along these lines

Code: Select all

#	Key	Macro Keys	Note
XSHIFT-Phantom1	SET_TRANS_KEYS;SET_VOL_KEYS;SET_CHAN_KEYS;SET_MENU_KEYS;SET_PIP_KEYS;SET_OTHER_KEYS;SHIFT-Phantom3
	
TV	DEV_TV;XSHIFT-Phantom1	Hitachi TV
VCR	DEV_VCR;XSHIFT-Phantom1;DEV_TV;SET_VOL_KEYS;Dev_Cancel	Sharp VCR
DVD	DEV_DVD;XSHIFT-Phantom1;DEV_TV;SET_VOL_KEYS;Dev_Cancel	Toshiba DVD

etc for others,
with the DEV_TV;SET_VOL_KEYS;Dev_Cancel possibly isolated into its own keymove - you can check if the space tradeoff is worth it.