Etc eos magic sheet user command

तुमच्या विनंतीवर प्रक्रिया करणे शक्य झाले नाही
या विनंतीमध्‍ये एक समस्या आली. तिचे लवकरात लवकर निराकरण करण्‍यासाठी आम्ही प्रयत्न करत आहोत.

चालू ठेवण्यासाठी Facebook मध्ये सामील व्हा किंवा लॉग इन करा.

सामील व्हा

किंवा

लॉग इन करा

Hi All,

Despite trying myself and searching the manual, forum, Reddit and everywhere else I usually go to for advice, I can't seem to find a way to launch a macro from within a magic sheet command. 

I can call macro 100 from within a macro with: Macro_Button 100 <enter>

If I use this same Macro_Button command from within a command button I get a syntax error. Is there any other way to do this?

Other things I would love to do are record a macro from a command button, but that's for another day...

Thanks in advance

Chris

• Eos is a little picky about the spelling of the commands. Try to type only a piece of the command without the "Enter" at the end, so Eos will post the command to the command line. In this way you can try to track down the issue

• 

  event:macro 100

  and press Enter at the end of the line, do not spell "enter"

• 

  Thanks for the tip. I'll give it a go. Out of curiosity, what is the "event:" command doing and why is it needed here but not in a macro?

 Hello Everyone,

I'm running a 11-unit setup in a showroom (EOS+gadget on windows or mac) where I want to integrate a simple touch screen and a mgic sheet to alter our LED fixtures. Magic-sheet setup is doable, but i've run into problems, when it comes to "create a button" which should recall a certain cue or execute a function like "channel 1 through 11 intensity 40".

So in short:

- how do I setup commands for a magic sheet button (I know its target must be "command") - but how do I execute "Go To Cue 2"?

- is there an overview of possible commands (e.g. "got to cue")? (the user manual and its various unstructured supplements is a nightmare)

Thanks,

Jan

• 

  In the command editable text box. Type out the command line.

  For examples, hover your mouse over the box.

• 

  Got that, but the real hint was the "_" in your screenshot's "Go_To_Cue 2" - here is where the documentation of that commands would be great (again).

• 

  Its often easier to record a macro and then make the button a macro button rather than a command button, unless its a very simple command

• 

  i love the commands and prefer having my magic sheet buttons be a command rather than a macro.

  to answer the question regarding syntax: usually you can find the correct spelling of a command in the macro editor when looking at a macro.

• 

  To add to Ueli's point it also makes merging a magic sheet into Showfiles much easier. If the functionality of a magic sheet is all within as commands rather than linked to macros, presets and palettes, you only have to merge the magic sheet rather than keeping track of the macros, presets and palettes used and merging them as well.

• 

  The only downside to commands is, that they are language-specific.
  So if you prepare a show for someone who might use a different language on his console, most commands won't work.
  Macros on the other hand get "translated".

• 

  If you were to record your commands into a macro, the console will display the correct command line text from your button pushing.
  (Call it a grammar checker.)

• 

  It does come down to the complexity of your commands. Sure if they are short ones like @30 or Sneak 2 but not if they are more complex ones. Commands are more prone to error as you have to spell them just right whereas the macro is just the button you press.

  I'd also argue that what are you really going to use macros for id they are not being used from a magic sheet as you are not really going to remember the numbers to type in once you gave a few. (ok a few may be from execute on cues or OSC).

  As with all of this a bit of structure and planning may be need eg show specifc macros are numbered 1 to 100 and general use magic sheet ones are 200 up.

  Sam, I'm also not sure how you would avoid needing to merge in the presets and palettes, you're rather limiting your magic sheet if you dont allow it to refer to presets and palletes.

• 

  Pretty much the majority of the buttons of this magic sheet are commands with exception to the edge/zoom/iris buttons:

  

  I'm not saying you should never link them to presets and palettes, but limiting the amount certainly helps. If you can do it with a command, use the command. If you need to, learn the macro and copy it into the command text field.

• 

  Thanks guys. I'll macro my way through EOS!

• 

  It really depends on what you are using the magic sheet for. Your one is indeed mostly doing basic commands and you probably use it for setting up a new show and so that makes perfect sense to keep it all as commands.

  I'm using the magic sheets to busk shows, so I need it to have more functionality and for some of it my sheet needs to be like direct selects, ie a bunch of colour pallets, general looks, focus pallets for my movers as well as macros for copying BPMs to my effects, macros to load the master fader with different cue lists for different song styles etc, as well as the kind of things you have on your sheet to adjust parameters (which I do use commands on the buttons). Using macros makes it easier to re use as well as just need the new magic sheet (or areas of the sheet using views) to reference the macro rather than copy pasting the command from button to button.

  So really depends on what you are needing to do, both ways of setting it up are valid depending on the usage.

• 

  Therefore it's good thing we can have multiple magic sheets!

  I also put MS navigation buttons on mine. So I can jump to one that has the tools I want at the moment. Think early web page design.

• 

  Yes agree navigation buttons are useful to jump to say a setup sheet from you main sheet. Using the views thing that lets you have one sheet and a view shows you an area of it is useful as well . linked to buttons you achieve the same thing navigation wise but you can also copy paste within the single sheet that contains all your "sub sheets"

  So I've switched to doing that after I think Ueli suggested it in a post a few months back

• 

  would you mind sharing this magic sheet? I'm trying to use commands in a magic sheet to write labels/notes to cues and can't get it work correctly...

  Thanks!

How do I use etcnomad EOS?

How do I copy and paste from Eos family magic sheets?

How do I assign objects to console button functions in EOS?

How do I use EOS software?