In the same way that you can setup a scene to be recalled on MixRack startup, it be useful to be able to do the same with Actions.
For example, I run SuperRack Performer and it would be nice to make sure that all Waves processing is bypassed when the console starts so that audio continues to flow while I get my Waves rig started up.
Yeah, I could do this with a scene, but I’ve already got an action setup for toggling that processing (channel inserts) in and out, so it would be nice to be able to reuse that.
just start your audio after you set up everything. or power down accordingly, like you would with mutes etc.
Yes, currently when I shut down I try to remember to recall the action to bypass the Waves inserts. The key word there is “try” 
I’m human and I forget things. This would be a minor quality of life improvement.
UPDATE: It turns out, there isn’t a great way to do this with Scenes either. The recall filters in Scenes don’t allow you to recall Insert A attributes separately from Insert B.
In my case, I typically use Insert A for Dyn8 and I use Insert B for all my outboard processing.
Ideally when the console starts up, all of the B inserts would be bypassed. Unfortunately, that doesn’t seem possible without also recalling settings for Insert A.
So, with dLive firmware 2.1, you can now recall an Action with a Scene. This should allow me to setup a “startup” scene that gets recalled at MixRack startup, which should then trigger my “Disable External Processing” Action.
I tried testing this with Director 2.11, but unfortunately it didn’t work. That said, I suspect that Director doesn’t actually support the “MixRack Startup Scene” feature. I’ll have to try it again when I’m actually in front of a console.
Updated my console and tried this out. Unfortunately, it didn’t work, which is a little surprising. @NicB, do you know if this is expected behavior?
I’m just spit balling, but did you check your global safes? Perhaps A&H automatically set this functionality as “safe” in a global safe to ensure people didn’t experience unexpected actions when they updated. That is the only thing I can think of…
Hmmmm, I’m not sure. I’ll take a peek at director in a bit. I did specifically set the scene recall filter to block everything, because I don’t want the scene itself doing the lifting.
I did a test of an action with a power on scene and I think it worked. It has been a week or two, but I think what I did was something like this:
- I already had a power on scene
- I added an action to it to do something different from what the power on scene had stored. I think in this case it was some ABCD parameter.
- I powered off the Surface (just in case)
- I power cycled the Mix Rack.
- I powered on the Surface to see the mixer state, and I concluded that the action had fired.
It is not clear to me if actions “live” entirely in the Mix Rack or are “split personality” like scenes (where each component handles parameters it owns).
It may be that surface aspects of an action would not work properly in a power on scene.
Hmmm, that’s interesting. I was testing with a power sequencer. I believe my action was pretty much just bypassing channel inserts, which I wouldn’t believe to be tied to the surface specifically. I might try it again tonight with a more obvious action.