I am having all sorts of trouble with turning sends on and off in N14, I can write the automation, it just won’t read back. Send level atm is fine though.
It is not just a display error either, the sends keep sending even with the automation track is clearly showing the send as disabled
In this video I am showing the send enable atm track. You can see it writing fine, just not reading on playback. This makes Nuendo unreliable for mixing and mastering anything that uses FX sends. N14.0.32 Win 11
It seems to be working on my install.
Have you tried the “usual suspects”? Close/reopen project, quit/restart Nuendo, shut down/reboot computer, duplicate track and try on duplicate… and so on?
Yes, tried those. This is a problem I have had for some time.
I was mixing just now and ALL of my automation stopped reading, faders and all. This happens from time to time. It writes ok though. A session restart or reboot works for a while, but the problem can come back.
It may be something in my session, but is seems to happen on random sessions at seemingly random times.
Even if it is something in my session, It’s a scary way for N14 to fail, just quietly ignoring automation.
I wonder if it could be a Eucontrol issue? I’d be interested to see if this happens to anyone else.
You know I was literally just going to ask if you have controllers connected.
I’ve had my s1 go wonky on me several times. What happens is that a control ‘device’, usually a fader, stops responding correctly and just sends automation data continuously if I’m in specific automation modes. It also fails “with” Nuendo in that reading automation gets screwed up.
I recommend that if you have an s1 you quit Nuendo when this happens and then turn off the s1 using the back switch. Then disconnect the power cable to it. Reconnect after 10 seconds and after it’s recognized restart Eucon and load up the project again. That seems to work for me.
OK that’s great to know!
Yep. That’s pretty much my standard procedure for working around this. I just really wish there was some sort of warning that Eucon or Nuendo wasn’t functioning properly… other than the obvious fact that it isn’t working properly 
.
Sometimes it may not be that easy to notice, say for example, at the end of a 20 hour mix day and you are mastereing in trim mode so you don’t see the faders moving. You will obviously hear the difference, but if you are mastering from stems with small tweaks and the changes are subtle a this point it may have the potential to slip through with not ATM being read.
Yeah I agree.
This is really a problem for me. I have disabled Eucontrol and the send problem is still apparent and making Nuendo unusable.
In this video i am sending to a delay from 2 different tracks. the settings are the same on each. The send works from one track but not the other. The FX panning is set correctly too.
Am I the only one that this sort of thing happens to?
I quit N14.0.40 and reopened the project and it still doesn’t work.
Over nearly 20 year of using Nuendo this hasn’t been such a problem as it seems to be for me now. I wonder if anything has changed that could be causing this?
If I copy from a non working track to a working track with automation the send stope working for the sound on that track. if I copy without automation to the working track ithe send does work.
I have had similar issues with direct sends in the recent past too.