Hi,
I've almost got a JP1.x flash Atlas 1056 OCAP sig 3A333 setup for the main HT, but need some advice. It's a 5 device remote and I have 5 devices TV, CBL, AUD, DVD and VCR (I put my 300 disc CD changer on VCR for now).
What I need advice about is how to deal with an alternate usage of my CBL and have it "fit" with the way I've gotten used to using extenders on remotes. Also I'm getting some consistent issues getting my first solution to work, see below.
I use LKP on a device key as follows: short is usual device key setup, long fires a macro that sets up the HT for watching signal from that source and then does key selection. e.g. long keypress on CBL turns on AUD, selects digital input 1 from the CBL box, selects input CBL on the TV and sets C, M, O, P to CBL and V to AUD.
Because of my TV and the way it handles 1080i/480i input, in order to watch standard cable, not HD content, it's better to have the box output 480i via s-video on input S-VIDEO to the TV.
I tried to select that configuration as shift+CBL using a standard macro. This set the TV input to S-VIDEO, mutes AUD with a toad-tog and sets keysets.
HOWEVER, I'm consistently not able to get the macro, shift+CBL, to fire when the last keypress was either a short or long keypress on CBL. If I make any other keypress then press shift+CBL it works. It's totally consistent. You can see it as the device lights blink.
shift+CBL will show AUD - TV - CBL (AUD fires only if AUD needs to mute according to toad-tog) when working correctly.
IR file is HERE.
How am I confusing the remote with this standard macro? Is it the shift key? Mixing standard macros and special protocols?
Thanks and sorry for the long post.
Best,
jeff
Need one more device on Atlas and...
Moderator: Moderators
I don't have an explanation, but a possible work-around. You say any normal key press enables shift+CBL to work again. Try adding a bogus real key to the end of your CBL DSM, like an arrow or pip key that would have no real effect. X_Cancel might also do the trick.
This has nothing to do with your problem, but may simplify things a little. Since both sides of you LKPs call phantom1, you may as well put the contents of phantom1 in the main device button macros before calling phantom2. Then you can remove the phantom1 DSMs entirely and remove their calls from both sides of phantom2. That would make the short side completely blank. If you do this, the fix above for adding a real key would have to be added to the end of both sides of your LKPs of course.
This has nothing to do with your problem, but may simplify things a little. Since both sides of you LKPs call phantom1, you may as well put the contents of phantom1 in the main device button macros before calling phantom2. Then you can remove the phantom1 DSMs entirely and remove their calls from both sides of phantom2. That would make the short side completely blank. If you do this, the fix above for adding a real key would have to be added to the end of both sides of your LKPs of course.
-
greenough1
- Posts: 658
- Joined: Sun Jan 30, 2005 12:20 am
Thank mdavej.
Your second paragraph on how to simplify my setup is a good one and I think you've suggested this before
. It can't hurt and is straightforward to do.
I did try X_Cancel with no effect and I tried temporary device selection thrashing at the end (X_TV, X_AUD, X_CBL) to get past it the failure to fire. I did not try a real key as you suggest, and that might solve it. I need to determine if I have to use a key that has something defined on it or not to get things to work.
Thanks,
jeff
Your second paragraph on how to simplify my setup is a good one and I think you've suggested this before
I did try X_Cancel with no effect and I tried temporary device selection thrashing at the end (X_TV, X_AUD, X_CBL) to get past it the failure to fire. I did not try a real key as you suggest, and that might solve it. I need to determine if I have to use a key that has something defined on it or not to get things to work.
Thanks,
jeff