First Timer Needs Help w/ Power All Off Macro

[ElizabethD]

Capn Trips is likely asleep on the other side of the pond, so I thought I'll give you few things for starters, then he can fill in the holes.

Miliseconds are listed in the readme file. A setting of 2-3 is what most people find useful. 1-2 seems better for Double key press.
If you really really really really need miliseconds, let me know. I use IRSA and can tell you time between signals exactly. Bear in mind that includes the time of the remote finding the LKP, or macros, base codes or keymoves and so on. Just to trigger the first signal in a LKP involves an observable pause, and sometimes that latency is too long. Trial and error.

Last step of a macro is a cool thing. Whatever the last real IR signal is, it'll repeat so long as you hold the macro key or more specifically the button that triggers a sequence of codes. The first one, if nested, like device keys in your setup. Few examples:
Put next track as a last step of some macro and watch the DVD advance tracks.
Put ch+ at the end, and watch the TV channels advance
Put tuning up for the receiver and it'll walk the scale.
In 8910 I use it for volume up when switching from non-DVD to DVD, down the other way, and for tuning.
Last step does need to be a real signal. Don't try some command that just goes to the remote (Dev_TV or DEV_Cancel or Pause), it won't work.

Volume and channel buttons for the most part repeat anyway, I think, so code it on others.

[Capn Trips]

Thanks ElizabethD for that thread. It explains the weird behavior that I was getting. I guess I just missed it since the subject of that thread would not have alerted me to the problem given I was using the OFA 9910 instead of the 6131.

Capn Trips,

Would you know what the duration/threshold values in the LDKP translates to in milliseconds for the OFA 8910/9910 remote? I am using the threshold value of 2, but feel that it may be a little to long.

Also can someone explain what is the purpose of holding down a button in relation to the last step of a macro? I noticed it mentioned a few times on this forum, but was too much of a newbie for any of the information to register.

Although it's hard to convey inflection in type, trust me taht I was JOKING with my comments about you not finding that old thread. Heck, I was the one describing this behaviour and I didn't remember/find it! That's why you ask questions in the forum.

As for the milliseconds per pause, I have little to add to what Liz wrote, aside from my experience that a setting of 1 basically calls for a short "tap" to get short, and anything else for long, whilst I use a 3 to get about a .5-1 sec. interval

[mifronte]

Thanks ElizabethD for the explanation on holding the button for the last macro step. Now I have to think of some clever way to put it to good use

I am using duration of 2 for all long key presses (LKPs) and double key presses (DKPs). Even for DKPs that call LKPs. It seems to work fine just as long as I make a mental note to slow down my trigger finger if I want to activate the LKPs. I guess its the premature trigger finger syndrome

[ElizabethD]

A double calling long press is tricky. It's not guaranteed to work 100% of the time, there will be occasional failures. At least that's my experience. Is that what you're doing?
Some history (I searched for Haggis), start with the Haggis thread referenced here
http://www.hifi-remote.com/forums/viewt ... iple+power