I work at a church and I want to be able to recall the dyn8 whenever I recall a user from the library. So I have several different musicians and several microphone positions I don’t want to be able to easily recall this.
Sure I can create a scene with all of these different ones but that’s tedious and not volunteer friendly.
The idea is that whenever you go and select a particular Channel, you didn’t go into overview and hit the library button. Whenever you recall that different person it will also recall their dyn8.
With firmware 2 the channel library was expanded with what is possible to store. But A&H was not able or willing to include inserts in that process.
This is still high on my feature suggestion list, when it comes to workflow improvements.
1 Like
I fully support this request…
That being said, I would argue the opposite. Create a scene and recall block everything except the musician’s channel information (name, processing, FX send levels, etc), a set of baseline send levels for their monitor buss based on their preferences (if you aren’t using the ME system or other external monitor solution), as well as the DNY8 settings. Then create a user key to load this scene. This makes it literally a “one button” solution to “load” a particular musician’s setup and make all of those changes in the system.
Trying to do all of these things via various library recalls is going to require a lot more knowledge of the system and far more steps to accomplish this than a single user key would which makes if far more volunteer unfriendly than the “scene solution” would be.
If you are worried about how complicated it would be for a volunteer to save these changes week to week, again I would argue that the scene solution is far more volunteer friendly. The hard work is in setting up the scene recall filters correctly. However once that is done correctly, a volunteer could easily save the current console settings to that musician’s scene if/when needed.
If the same musician/vocalist always uses the same input then I can see the scene method working. If they move around on the inputs then I don’t get how the scene method would work.
Its never the same. 6 microphones and 15 different people.
I’d use one channel per singer/position and switch them with Mute. You have 128 channels. 
With ABCD you could setup 4 positions in a single channel.
Some parameters could be ganged between the channels of the same singer.
Each of those channels have their own processing and send levels.
With mixing station I would build a surface to “monitor” which channels are on and to be able to switch between them.
Apart from that, I’d love the channel library to also recall the Dyn8.
I feel like you meant exactly opposite of where I was going with this. Sure I have 128 channels on the desk but in a church environment I’m using a lot of them every week. This is also not volunteer friendly. That was the biggest thing that was in my opening statement. Utilizing scenes or anything crazy like that invite someone to mess it up. I’m not always going to be there to make sure it’s operational. All the pieces are there they just need to put it in place
Utilizing 15x6 possible combinations of channels/inputs will never be volunteer friendly. Also I can’t imagine an easier method than just mute and unmute. 
Then maybe two sets of scenes, one for “who?” and one for “where?”?