Timing macro in show control

The macro needs to contain these commands [Event 1 / time], without an [Enter]. Where 1 is the list number of your timecode list. Then when you run the macro, it will post this to the command line, and the macro will no longer be running, but you can enter a time and press [enter].

In the macro editor, the [Event] command is on the 12th page of commands, the 4th button on the third row. So to make this macro:

[macro macro] (opens the macro editor)

[1 Enter] to create macro 1

[Edit]

[Event 1 \ time]

[Done]

Hi Dan, thanks for the wise words - however looking back should the macro contain a / or \ . Does the time command come from the page of commands or is it generated by the time button on the keypad?  I have created the macro but when I input the time and press enter the command line clears but the clock does not start. I am wondering if the macro I use to start the clock is causing the problem, the first tap starts it and the second stops it and resets to 00

This is what I have

Clear CMD line

Clear CMDline

Blind event [enter]

Internal time 0000 [enter]

clear CMD line

Live [enter]

When I stop the clock using the second tap could this disable the internal clock?

Is there any further information available for macro programming?

Regards

Malcolm

Hi Malcolm,

Dan put me straight on this by E mail yesterday. Here's what I think is the best solution...

In the macro editor:

[Event 1 / time Wait_For_Input Enter]
[Event 1 / Internal Enter] (or Internal Enable) if it should always enable it, not toggle

[Event] is on the 10th page, and [Enable] is on the first page.

You should create a macro from scratch to do this and use the softkeys in the macro editor rather than trying to Learn it. There are complications when Learning in the Show Control display as the Learn key has a different function there.

Also, to re-commence the macro once you have inputted your time you need to hit the macro key again rather than Enter. For this to work you need to be in Live rather than the show control display - currently Macro posts to the command line in this display. Dan is writing this up as a defect.

I would suggest creating a second macro to stop the clock which is simply:

[Event 1 / Internal Disable Enter]

rather than trying to have one macro which toggles start and stop.

I hope this works for you, I have attached a showfile here with two working macros 401 and 402 as an example

Graham0675.Macro Timecode 2012-05-02 09-44-36.zip

Hi Graham and Dan

This all works excellently now. Just 2 points,firstly what is the logic behind the softkey allocation in macro programming apart from there isn't any, and secondly is there any documentation about macro programming, everytime I have to do something I invariably have to kick it upstairs for clarification.

Thanks

Malcolm

Hi Graham and Dan

This all works excellently now. Just 2 points,firstly what is the logic behind the softkey allocation in macro programming apart from there isn't any, and secondly is there any documentation about macro programming, everytime I have to do something I invariably have to kick it upstairs for clarification.

Thanks

Malcolm

Each two rows of buttons in the macro editor is a softkey page that exists elsewhere in teh software. But the order of all of the softkey pages in this display is mostly random. We plan on changing this organization in the future, or maybe add a second format that is all of the comamnds sorted alphabetically.

I don't think any documentation exists beyond the manual, but I usually suggest:

1) Learn the macro instead of creating it in the macro editor, and then go into the macro editor and delete any extra unneeded commands. Including any commands that change the displays, like entering blind.

2) If it's a toggle command, and you don't want a toggle, add [Enable] or [disable] after the command in the macro editor. 

3) As much as possible, don't rely on the console to autoinsert rthe first command on the command line, (Ex: type [Event 1 \ ] instead of just [1 \]). If you type the first command, the macro will likely run correctly in live, instead of needing to be in patch, or showcontrol editor.

4) Add [Enter] to long command sequences to spearate different parts of the macro onto different lines. Sometimes this helps the software resolve ambiguous commands.

Special Case: The [macro] button and the [learn] button act differently in the show control editor than other displays, so learning a macro in this display isn't possible unless you start learning the macro in live before you go to the showcontrol editor, and staop learning it after you have returned to live.