Let me rephrase once again:
There will be no confusion at all for unexperienced users. Quite the contrary.
It’s been already 6 years since this post and there‘s really still no progress regarding this Problem?
We just got a bunch of dLives and seriously, the more I use them, the more stuff like this I learn to hate. How can something like this, which every company seems to get right still not be fixed 6 YEARS LATER…
Just to clarify why I find this extremely problematic:
We are a venue, using dLives as house desks. So I setup a starter show with a bunch of utility scenes such as surface illumination, patch configs etc.
For every show I mix, I duplicate this show and do some adjustments, for example change mono to stereo channels. So after I made these changes, I’m supposed to go though all my scene filters, to make sure that this stereo channel is still blocked in my filter for illumination?
I don’t understand how this could be advantageous for anybody? I could understand somehow, that a fundamental change to the show, like changing bus structure is having an impact on the filters, but cmon A&H, I change a channel from mono to stereo and it renders all my filtered scenes useless?
It would be awesome if someone would reconsider taking this way higher in the list. Also aren‘t here also some A&H representatives who could maybe elaborate why it is the way it is and why it would not be addressed in the past 6 Years?
Maybe if all contributing here start voting for the topic, somebody at A&H will care about it
Agreed, please default to block for new mix elements in filtered scenes.
Again, this isn’t that simple.
Nobody is suggesting it’s simple Steffan, but I stand by my opinion that the best solution is, as mentioned by others above, default to block for new elements in filtered scenes. Leave unfiltered scenes unfiltered.
I encourage as many people as possible to suggest alternatives so the A+H engineering staff have as much input as possible when looking at this issue.
I agree that the default behaviour should be block, but that will not change the fact that you need to go through your recall filters if you add something to the show file. You would still need to go in and manually unblock the new elements.
Maybe the ability to copy filters between channels or busses could make it less daunting when when updating very granular filters.
+1 for default block.
Not sure, how “default block” should be done technically. If it needs something like a conversion tool for show files, I would prefer doing it by hand. That way I could do a “sanity check” of the files in parallel.
The same way default unblocked is working.
Really? What a ridiculous statement.
It would lead to all filters are blocked by default. That is not what we would expect. It would need extra effort to every scene you store, always.
No real solution.
Not for all scenes but for new mixes due to mixer config changes. Now they are by default unblocked in all filters. They could also be blocked by default. There are use cases for both ways of course.
Thanks for calling my statement ridiculous, only because you didn’t understand it. 
One way I see to solve this: change the behaviour of the “block all” button. Currently it is basically a gui action that checks all the boxes for you. I think it could be changed to toggle between “default blocked / default unblocked” and then store that setting with the scene. That way the user can choose what behaviour he wants and it would give the result most of us want.
That would be great.
what should be “default blocked”, what “default unblocked”? I don’t get it yet, sorry…
Well… Currently there are two buttons: “Block all” and “Unblock all”. This is a one time action. If you change the mixer config any new items in the scene will not be blocked even if you previously selected “Block all”.
So what I am proposing is changing the behaviour of the “Block all” and “Unblock all” buttons. Instead of it being a one-time action that blocks or unblocks all current items it should remember your selection and apply the same to new items. So for example if you selected “Block all” And later you change a channel from stereo to mono the newly added channel in the scene would also be blocked. Hence me calling it “Default blocked”. It’s the default reaction to new items added to the scene.
Don’t see how this would help in situations where you have blocked only certain parts before. And as another question: how should a “automated” solution like this work for locked scenes? But as always with questions like these, unless someone from A&H will shed some light on this, it feels like poking in the dark for me. But at least we are in consent, that the current situation is not desirable for most users.
You have a show with hundreds of scenes with specific filters. Now you change the mixer config. All new mixes are by default unblocked in all of your scenes which can be an absolute pita.
It would be great to have an option, that those new mixes are blocked instead of unblocked. That’s it.
Yes please (and I did vote, I am one of the 3 votes currently) And as stated, this should only affect scenes that currently have recall filters. Or it could apply only to filtered scenes that are locked as another option. (really something that is “locked” should never be able to change its scope to allow new things)
I have scenes that I use to unmute a few channels automatically at a certain time using 3rd party software. Changing the mixer config causes these scenes to zero out these newly created channels or bus’s when the filtered scene is recalled. Makes me very warry of even wanting to change the mixer config very often as I have about 50 filtered scenes for FX, gating, choir mic gate presets, illumination, and drum compression. Annoying to go through each scene, one by one and block the new elements.
I think a solution with a button that let’s you pick if the filter should default to block or unblock would be a nice solution. It could be even be a user option somewhere.
One thing i’d like to clarify. I think its one thing, that the filters change when you alter the mix configuration. Because for the engine its probably a completely new channel getting created.
But when i switch a channel from stereo to mono, why cant the newly created mono channels inherit the recall filter of the initial stereo channel? This would at least make this process safe.
I think the current state is that it makes scene filters basically useless, unless you are always using the show with the same Mixrack config. You giving the user the options to customize the desk to your needs, but basically you cant use scenes properly anymore as a tradeoff?
It can’t really be that hard to implement and i’m sure that something like this is a big turnoff for a lot of FOH, especially theater folks.