During busking, store an effect in a sub without visibly running the effect

For busking I thought it would be nice to be able to have deferred effect activation, so dynamically putting a channel selection in some effect, but not having that effect activate yet. But instead the channel selection would have that effect applied within a submaster, so I can bump the submaster to hold when I actually want to run the effect. I could of course go into blind sub and put an effect on the channel selection, but I would like to stay in live, so that the layout of the desk stays the same at all times. Going into blind via a background macro is not the problem, because that doesn't change the visible layout.

So I would like to type something like this: '91 Thru 100 Effect 141' and then press a macro that puts that thought into some dedicated submaster. The submaster would then configured to be a rate + size submaster, so I have great control over the effect as soon as I actually activate the effect through said submaster.

So this requires some hacks. And the approach I tried was to have the macro press enter for me, so the effect is activated in live, then store the effect in submaster 61 and quickly remove specifically only that very effect from live output again (through quick macros, so it's not noticable). So I need some sort of mask to only remove the effect I just typed in and then get back the previous manual values. So after some trial and error I figured out that putting a sub in LTP and then bumping twice would first overtake the effect (source is now the sub) and then stop the effect (effect stops entirely and does not go to manual source effect).

Macro 1 (foreground): 'Enter', 'Macro Button 2 Enter'.

Macro 2 (background): 'Select Last Effect Record Only Sub 62 Enter', 'Sub 62 LTP', 'BLIND Sub 61: Effect Recall From Sub 62 Enter', 'SubOn 62 Enter', 'SubOff 62 Enter', 'Delete Sub 62 Enter Enter'.

This sort of works, but it's not reliable, because it sometimes fails to disable the manual effect (the last part of the macro, but it does delete sub 62) and you see a slight flicker (for an intensity effect at least, focus effect would be slight movement), because the effect is activated in live output and not turned off quickly enough.

So does anyone have any ideas?

Parents
  • A lot of Macro action... puh.

    Not tested:
    You could nest different macros into each other.
    1. [Learn] a macro with you selection and the FX
    2. [learn] your Sub
    3. in background -> go to blind Sub, use macro(2.) to create your Sub and edit it to contain your desired contant with macro(1.)

    I don't know if you are not faster if you create the sub in blind yourself.

    ----

    other thing that pops in mind is, can you use Stagging Mode?
    Than you maybe don't have to enter blind at all.

Reply
  • A lot of Macro action... puh.

    Not tested:
    You could nest different macros into each other.
    1. [Learn] a macro with you selection and the FX
    2. [learn] your Sub
    3. in background -> go to blind Sub, use macro(2.) to create your Sub and edit it to contain your desired contant with macro(1.)

    I don't know if you are not faster if you create the sub in blind yourself.

    ----

    other thing that pops in mind is, can you use Stagging Mode?
    Than you maybe don't have to enter blind at all.

Children
  • Since it's always sub 61, I can just hardcode it. If you meant the following:
    511: '91 Thru 100 Effect 141 Enter'
    512 (background): 'BLIND sub 61 Enter', 'Macro Button 511 Enter'

    Unfortunately it doesn't work. Macro 512 has to be background, or else it will visibly go into blind. If macro 511 is foreground, then the effect just activates in live. If macro 512 is background, then it doesn't work either, because a background macro for some reason always starts in live (user 0, but in live), which I can see in Tab 99. So the idea of macro 512 'presetting' the blind sub layout for macro 511 to then do its work there, doesn't seem to be possible.

    And staging mode changes my layout, and I don't like the idea of not having immediate control at pivotal moments. And I thought about maybe including a dynamic snapshot at the end of every macro (so record a snapshot to some throwaway hardcoded number and restore at the end of the macro), but I think that only complicates the problem.

Related