Options
Related

MIDI and macros

There are three things I'm dealing with that I feel would be easy fixes.

1: There is only the ability to have one MIDI channel be set to comment macros. You can't use two Launchpads for instance because it puts you over 127 MIDI notes. Really annoying when trying to do extensive external inputs.

2: Sequential macro commands. Why do they all need times? And why when they're set to a 0 second delay do they mess up? I feel that should execute the commands, top down, as fast as the CPU can crunch the numbers. Which would be SEEMINGLY instant, but you could establish a hierarchy in your commands.

3: Allow comment macros in the "button macro" builder instead of the whole "key press" "1" etc. I want to be able to apply times to comment macros which I know I can technically be done with a cue stack... But the interface is already there. I want to be able to launch Macro 1 for instance, but have that be filled with "GL#".
Parents
  • These have been logged as
    1. H4OS-3412
    2. H4OS-5558
    3. H4OS-5557

    To address your point in #2 about needing times. The keystroke can work like a cuelist where if you don't put a wait time, the console will pause the macro and wait till you execute the macro again. Useful if you want the macro to wait for your input. Here's a link showing how to do this support.etcconnect.com/HES/Consoles/Hog_4/Software_and_Programming/Make_a_keystroke_macro_that_waits_for_user_input
Reply
  • These have been logged as
    1. H4OS-3412
    2. H4OS-5558
    3. H4OS-5557

    To address your point in #2 about needing times. The keystroke can work like a cuelist where if you don't put a wait time, the console will pause the macro and wait till you execute the macro again. Useful if you want the macro to wait for your input. Here's a link showing how to do this support.etcconnect.com/HES/Consoles/Hog_4/Software_and_Programming/Make_a_keystroke_macro_that_waits_for_user_input
Children
No Data

www.etcconnect.com