Automation Read / Write Problems N14 Win 11

Nuendo
1

I had this in another thread but though it would be best to move it here to a thread with a broader title.

I am trying to automate some parameters on a reverb. They write OK but do not read back… until I give them a jiggle.

I write ATM change parameters as time goes on.

I play back, the parameters do not change even though the automation can be seen on the relevant tracks.

I stop, jiggle a parameter when I’m stopped and the parameter suddenly jumps t what it should be, and from that point onwards it does update correctly on playback.

This happens with all parameters of this reverb.

I have odd problems with other plugins too.

This means that I can’t rely on Nuendo’s automation to work when I’m mixing.

Has anyone else experienced anything like this?

2

With this panner I can’t write any automation from the GUI, i need to use the remote control to make it write.

It does seem to read OK though.

3

Assigning Quick Controls works really well for inserts. Maybe give this a go.

4

For this, try assigning Quick Controls via the inspector. (great if you have a dedicated controller for quick controls in Midi remote)

5

True but pretty time consuming setting it uo for lots of plugs and lots of tracks.

Also, the writing seems to work ok for the reverb example, just not the reading.

There are also a hell of a lot of parameters in the reverb example her e and not enough quick controls to controls them all.

Have you ever experienced anything like this ckon?

6

Not recently but I do remember issues with an external reverb hardware via midi plugin and preset changes/parameters not changing on read. I see you’re going through ‘presets’ which in turn have different parameters. (The preset changes in the plugin are probably not able to be automated either or have a midi command?) I can only gues the Plugin is getting stuck on the amount of data coming back in and the changing of presets might possibly be an issue. I am only guessing btw.

Other issue: Does the QC work for you with the panner?

7

I’ll give that a go. I also use the plugin remote control for that and that works fine.

From memory don’t I need to set each parameter up for each track manually, I can’t copy the quick control setting across tracks? I also reckon it would be much better if I just worked in the first place without a workaround.

At the moment I’m more worried about the reverb automation not reading. Especially as it writes ok but doesn’t read.

I am fkicking through presets but the automation is writing just fine. It just doesn’t read back reliably.

This is a problem for me.

8

It’s possible to save the setting as a QC Preset e.g. ‘HARPEX’ and as long as the other track has the HARPEX plugin inserted then load the QC preset on that track also.

1 Like
9

I just tried the QC on the Harpex panner and frustratingly it won’t work at all. The parameters won’t appear in the QC area using the normal GUI. It does work if I assign the QC’S via the remote control panel though.

The annoying things now are having to assign the QC’s manually on each track and also the QC parameter limitation.

10

Yep, that work, thanks! Still annoying to have a limited number of controllable parameters though…

And would still be great to be able to use my beautiful reverb with automation.

11

Just a thought, for all the presets that you are going to use, save them as Nuendo VST3 presets in the plugin menu (not in the Cinematic rooms presets). Select them as you are in write. Do the parameters read back now?

1 Like
12

Good call, that seems to work! Thanks again!!

You’ve been an enormous help, but I don’t really want to tag this as a solution as it still feels like a bit of a workaround, and the Harpex panner thing is functional, but still not what it should be… However, I can get to work now :slight_smile:

13

:+1: Great.

The way developers do their preset management seems to vary wildly, so I suppose using the Steinberg Preset management in the context of automation could maybe be viewed as a solution:-) as when there are 3rd party VSTs involved who knows what’s going on under the hood.

14

Yep. I’ve been playing with the presets for a bit now and it’s a bit flaky. If I have existing automated parameters and I go back before them, recall a vst preset with touch assist on and punch it in, it does not write all parameters, so some parameters will keep switching when I don’t want them to.

Back to the drawing board

15

It also appears not all parameters are being read every time they appear. Sometimes the preset name updates on playback, but most of the time it doesn’t.

16

Yeah, tried a few various plugins to write with preset change (incl’ old VST2 2c audio B2 and exponential R4) and it’s really flaky. Sometimes having to click on the parameter value on the track to bring it to life on read. Steinbergs plugins seem to work fine though e.g Revelation and Roomworks (automation paramaters via presets) . I don’t ever use preset automation on VST inserts (apart from the hardware VST mentioned earlier). It could be the way the 3rd party plugin is coded making communication glitchy, I donno.

17

Yeah, I really don’t want to be limited to Steinberg plugs.

I also have a long running problem with Nuendo where it sometimes just stops reading automation altogether and I need to quit and reopen my session, so I tend to see Nuendo as the problem… but I’m sure it’s not just a Nuendo thing.

Out if curiousity I might give these plugs a test in Protools and see how they behave, see if it’s more reliable in general.

18

will be interesting to hear if Liquidsonics Reverb works with all the written automation points via write via presets in Pro tools

Was for sure not suggesting this:-)