Suppose I have a push and hold macro, that fires one command on tap, but a different command if I hold it for e.g. 1 sec. If that last command is normally a sustained IR command (such as volume button), does it also sustain in the macro if I keep holding the button?



This message was edited by Arjen on 06/03/02 00:05.19.

Bump.

I know I have asked a similar question before, wanting to know if you could specify a number of repeats for a command in a macro.

But now that the remote is here, could someone try if the last step of a macro or push-and-hold macro will sustain an IR signal at all (like volume, FF etc.) when continuing the hold the button?

Thx...

Hi Arjen,

I think you're out of luck on this one. I tried to do what you're talking about but it doesn't work. I added a "volume up" command to the end of a macro string, but it just fires it the one time. In fact, even if you learn the "volume up" command to a button and place a push and hold macro on the same button, it fires the "vol up" command and the macro, then stops.

You would have to add a definite number of "volume up" steps to the macro, but that wouldn't give you the variable control you're looking for.

Mike
Surf Remote Control

A "sustained" button like VOLUME needs to be held down, even when its not in a macro.

We did talk about the inability for the MX-700 to have sustained buttons other than the usual ones, unlike the T2, in another thread a couple of months ago.

... Greg :-)

Greg,

What do you consider "the ususal ones"? I have repeating codes on the cursor, Prev Ch and Guide buttons on the Audio Preamp device. They all work fine.

DJ

I mean any ones that repeat when held down, as opposed to those that send out one IR code no matter how long you hold them down.

It doesn't matter what button you put them on. You can put a repeating code on any button. It just has to have a repeating signal either in the database, or learned from a remote.

... Greg :-)

Right. More or less what was expected based on pre-release discussions, but this confirms it then. Repeat codes only do their sustained job as single commands on a button. Good for now, but I definitely would like to put in an enhancement request for supporting sustained codes as the last step of a macro.

Thanks for testing that Mike. I'll be off on vacation for a few weeks, but when I get back I think I'll be placing that order :)

This workaround is obvious, but I've found it effective in a few situations - in the macro, press VOL UP or whatever 10-20 times. Often does the trick if the macro goes fast enough!