I was trying to print a mix and found some of my FX sends weren’t sending. I did a quick test and it seems these FX sends can’t be automated (send slot 3 in this case).
anyone else have automation problems?
I was trying to print a mix and found some of my FX sends weren’t sending. I did a quick test and it seems these FX sends can’t be automated (send slot 3 in this case).
anyone else have automation problems?
KI just quit and reopened N15 and the problem went away.
The fact that this can happen is mildly terrifying.
I wish I knew a recipe to make it happen, but it seemed pretty random.
Not the first time automation has failed but usually it’s everything, this time it was just this one parameter. Wouldn’t be that hard to miss one parameter when mastering.
I’m not sure I understand what’s in the video. You toggled “Preview” but I didn’t see you write any automation. Was it already written on that track’s send?
In the video I made sure Nuendo was not in preview mode, therefore the send I was toggling should not be changing state when I’m clicking on it, but it is.
When I quit Nuendo and re-opened the session, I made sure preview was off, and I was not able to toggle the active state which is the behaviour I expect. I didn’t make a video of this
Ok, now I understand.
I feel like I’ve seen this in N13. Don’t think I figured out how to reproduce it unfortunately. Scary.
I’ve encountered similar behaviour as well, sparsely. In 13, 14 and now 15. Some particular Automation data not being red. Then I reload the project and it works… I have to screen capture this.
Yep automating enable on send tracks is unreliable - I just don’t use it at all for safety. Better off doing it with send volume instead.
See also these threads:
Reported it to Steinberg during the N12 cycle, was asked for reproduction steps and a project file, which were duly provided as well as a video clearly demonstrating the problem. I heard nothing back and years later it was closed as “solved”, needless to say it is not solved.
@TimoWildenhain perhaps this could be retrospectively added to the March bug thread as it is a v longstanding bug relating to basic functionality?
Yikes! This is massive. And it’s still happening, unbelievable!!
Perhaps Steinberg don’t think reliable automation is important?
I can’t think of any other reason this is still happening.