Hi! Not sure if anyone care’s to reproduce this but I think this is quite a big one. If you have any tracks with mute automation, it will over-ride any solo selection you make from the arrange window or mixer. This seems like incorrect behaviour to me. It can be temporarily solved by disabling Read automation status on all other channels, but it’d be better if Solo’ing over-rode the automation to begin with. Thanks!
Hello,
This is not a bug, it behaves as expected.
Best regards,
GN
Hello Guillermo, thank you for your fast reply! This does present a bit of a problem, though. I’m doing variant exports for a job and it’s not allowing me to mute certain tracks. Like I said I can just disable Read on channels that have mute automation but it does get quite fiddly with large projects/track counts. It’s also leading to tracks being muted despite the mute button not being lit. I’ll try and put together a video to demonstrate it once my work is finished.
How about you automate a plugin control which either has a mute button or just a fast volume change instead. Then you won’t have any conflict with the mute or solo buttons on the mixer. That’s what I do, because during mixing I often want to mute or solo a channel for fine adjustment and mute automation is always going to get in the way of that.
Mike.
Hello,
I understand what you mean, but in this case the automation has priority.
What you could do is disable the read automation for all tracks from the automation panel or as suggested above.
Best regards,
GN
I have also had this problem randomly and it occurs still when I ungrouping tracks. V strange
I respectively disagree with Guillermo Navarrete, Online Product Specialist. His response indicates that the behavior of the solo button being disregarded by other track mute automation implies this to be of intentional design. However, I suspect this was not the intended outcome of this “feature” if continuity is the rule. The very word “solo” implies only the track(s) selected should be played. It is illogical to override the intent of solo because of external track mute automation, and I am curious as to the arguments why any non-solo’d track mute automation is allowed to take precedence over the user’s obvious intent. I am unaware of any other DAW (Pro Tools, Reaper, Reason) that offer this peculiar behavior. As it stands now, the solo button should be named “not quite solo”, by changing the “S” to an “N”, as it would be much more intuitive and give the user a clear indication as to what this feature actually performs. (Apologies for the sarcasm, but it’s not necessarily too far off the mark).
Steinberg, this really does need to be fixed as I cannot think of any usable instance where this “feature” has any practical application. I am happy to concede my argument if you would offer any reasonable advantages to this capability that is within the norm of what the majority of new users expect from this functionality. Additionally, I would be curious from other Cubase users if they find value in this capability.
I submit to you that if any track is being solo’d that mute automation on any non-participating solo’d tracks be ignored as it is in the aforementioned DAWs.
Of note, I am trying to come off of Pro Tools, of which I am a proficient fifteen year user, and convert to Cubase Pro due to the plentiful, powerful features and O/S compatibility afforded by Cubase 8. I am one week away from finishing up my 30 day evaluation, but the lack of several productive editing abilities along with several nuisance/quirky UI items, such as this odd solo behavior and no mouse wheel mixer fader disable to name just a couple, are discouraging my full commitment to switch at this time.