"you may now switch the aux-sends to "(none)" and back again to the intended target one (eg. "Master") to make it work."
That's not a solution.
If signal reliability cannot be guaranteed, it's better not to have this new feature (although it's wonderful).
Imagine that some subtle reverbs that I put in the background stop working. It's very likely that it will go unnoticed while I mix and master.
Then after listening to the mastered track several times I would say.
This mix is very dry, why?
I would have to go through reverb by reverb to find out which one failed... and the worst thing is, when opening the session from scratch they may all work, or a different Aux Send fails.
"you may now switch the aux-sends to "(none)" and back again to the intended target one (eg. "Master") to make it work."
That's not a solution.
If signal reliability cannot be guaranteed, it's better not to have this new feature (although it's wonderful).
Imagine that some subtle reverbs that I put in the background stop working. It's very likely that it will go unnoticed while I mix and master.
Then after listening to the mastered track several times I would say.
This mix is very dry, why?
I would have to go through reverb by reverb to find out which one failed... and the worst thing is, when opening the session from scratch they may all work, or a different Aux Send fails.