I don’t think this is the only thread on the subject, but I’m adding myself to this one as well. Just like everyone above, I too can’t understand why visibility configurations automatically include newly added tracks/channels.
I would love to see a Lock property on individual configurations that would prevent this.
3 Likes
+1
… to every visibility configuration.
Ugh.
Related problem:
A macro can handle hiding selected tracks in the current configuration… and also change configurations, and hide them again… but ONLY UP UNTIL Configuration 8. Right? I don’t see a key command option for 9+.
+1 for the feature request
This right here would be the best workflow for mixer visibility configurations in my opinion.
1 Like
+1000000 to this request, please!
1 Like
Been wanting this for so long. The workarounds needed to get around it are INSANE.
+1000000
+1
Additionally, Visibility Configurations 1–8 are available as key commands and can therefore be used in MIDI Remote. If we could have access to more than 8, it would greatly improve workflows with large templates.
I’ve never bothered with mixer configuration for the reasons posted, except I thought it was just me being thick, rather than poor coding, as it seems to be, by all accounts. Glad it’s not me whose’s thick, so thank you for this thread!
This thread is from 2020, 6 years ago. Come on Steinberg wake up. Have you found one user saying this is an acceptable design for this feature ?