Macro editing behavior

I am trying to write a channel check macro to check 132 lights on a truss. I wrote the macro using learn mode: 513 @ full [channel check} [enter] [next] [next] [next]...132 next commands.

I need to add a {macro wait} between each of the [next] commands. I would like to use a wait time of .5 but I have found that this command kicks the console out of channel check mode. That is the first issue.

The second issue is when in the macro editor to add the {wait} 1 command after the 3rd {wait} the cursor jumps ahead to the next line of the macro. This becomes a massive PITA to edit this. Is there a way to insert the {wait} command in learn mode?

Parents
  • You can use the Macro Loop command to achieve this, which should simplify your macro:

    513 [Full] {Check} [Enter] 

    {Macro Loop Begin} 131 [Enter] 

    {Macro Wait} 1 [Enter] 

    [Next] {Macro Loop End} [Enter] 

    {Macro Wait} 1 [Enter] 

    [Clear]

     

    Hope that helps. 

    -M

  • I tested this running a slightly shorter loop of 10

     

    513 @ [Full] {check} [enter]

    {macro loop begin} 10 [enter]

    {macro wait} 1 [enter]

    [Next] {macro loop end} [enter]

    [Clear]

    It seems to be running the loop 2 additional times. I will just modify the loop count to reflect this. But is it posible have a macro wait time of less than 1 second? 

  • Well, technically, it's not running the loop 2 extra times. The first channel is not part of the loop, and the loop doesn't count the first iteration, the number after the {macro loop begin} is telling the desk to repeat the loop x times *after* it's gone through the first iteration. So if you have a {macro loop begin} 1 , it will execute the sequence twice; It runs through the sequence and then *loops* the sequence one time.

    If it only ran through once it would not be a loop. I agree that this seems a bit counter-intuitive, but is logical.

    As for the macro wait of less than 1 second: there is a bug that won't let you use decimals in macro wait times. The dev team is aware of this and should be fixed shortly (right, Dan?).

    Hope that helps. 

    -M

Reply
  • Well, technically, it's not running the loop 2 extra times. The first channel is not part of the loop, and the loop doesn't count the first iteration, the number after the {macro loop begin} is telling the desk to repeat the loop x times *after* it's gone through the first iteration. So if you have a {macro loop begin} 1 , it will execute the sequence twice; It runs through the sequence and then *loops* the sequence one time.

    If it only ran through once it would not be a loop. I agree that this seems a bit counter-intuitive, but is logical.

    As for the macro wait of less than 1 second: there is a bug that won't let you use decimals in macro wait times. The dev team is aware of this and should be fixed shortly (right, Dan?).

    Hope that helps. 

    -M

Children
No Data
Related