I want to use one guitar plug-in (amp sim/effects) on a single source track and record its processed signal to multiple audio tracks for layering (L/R, solos).
I don’t need the dry DI signal—this is just a demo.
Current setup:
Source track with plug-in → routed to a group track → group track used as input for other tracks.
Monitoring source track while recording others.
Issue: Sometimes I get huge latency on some tracks, even with delay compensation, but one target track is fine, no huge delay.
Why does latency vary between tracks?
Is there a better workflow for this?
I wish I could have multiple target tracks which I could monitor and record, but all processing done via 1 vst. So I don’t need to monitor the source, just the target track
This is what I do when recording guitar (or bass), which gets around the latency issue altogether. However, it requires a couple of things (I use a Windows / Nuendo setup):
I use a separate audio interface specifically for guitar input (an inexpensive IK Multimedia AXE I/O One), which has it’s own ASIO driver that gets as low as a 16 sample buffer (~2ms latency - unnoticeable). This feeds a desktop “standalone” version of the amp sim I want to use (AmpliTube, NeuralDSP, Guitar Rig, etc.), bypassing Nuendo entirely. From there, I run the AXE I/O One’s stereo outputs to my main audio interface (RME UCX), using balanced analog cables.
The reason - I keep my main interface (RME UCX) at the highest buffer setting for sound design / post-production mixing work and rarely ever change it.
Additional reason - on Windows systems, you can’t use multiple ASIO drivers within Nuendo at the same time. This gets around that, but does require your amp sims have standalone versions available (the best ones do for live playing).
I set up two input channels of my RME UCX in ‘loopback mode’ in it’s TotalMix software, so I can monitor in real-time, outside of Nuendo. Once in Nuendo, by selecting those stereo inputs on any armed audio track in Nuendo, I can record that same processed signal anywhere I like, while the rest of the music plays back in Nuendo normally - voila, no latency.
One other thing I like about this setup is that the AXE I/O One interface also has another output called ‘AMP OUT’. It’s meant to be sent to a real guitar amplifier, but I use it to feed a third input channel on the UCX for a DI signal (just using a standard 1/4" guitar cable). This is perfect for capturing an additional mono DI recording at the same time as the stereo processed signal). I have that setup in Nuendo as well so that, once recorded, I can then swap out other amp sims as I see fit for the same performance). That, too, bypasses the latency issue.
Anyway, hope this helps in some way. It’s been a perfect workaround for me without having to resort to using a DSP-based interface like a UAD Apollo, etc. The key, for me, was getting the guitar signal into the DAW outside of Nuendo first, then routing it accordingly.
Latency will vary between tracks depending on plugin latency for the signal chains on those tracks. Some plugins have more latency than others, ranging anywhere from no latency to maybe even over 100ms. It is easy to check how much latency is in any given set of track inserts, though. Open up the MixConsole settings and enable the field that displays the latency. That will at least make it easy to identify any culprits that may need to be disabled when tracking.
I haven’t noticed guitar plugins I’ve tracked through (note that I am playing virtual guitars from a keyboard, so I’m tracking MIDI, but playing through pedalboard and amp simulation-type plugins so I can play off the feel of the sound, even if I might change it later) adding a level of latency that distracts from the playing.
Martin’s suggestion seems like it might be a good way to deal with one audio input going to two tracks with different signal chains (at least if you’re not needing to do comping and/or other editing with the recorded audio). That said, my method of the one track/two processing chains, specifically for (virtual) electric guitar signal chains has been to record the direct (MIDI) part to one (instrument) track, with no fader volume on the track but pre-fader sends to two FX tracks with the different signal chains, panning, fader levels, and whatever else may be needed. But I am wanting the un-effected track for comping and editing, and I don’t want to mess with doing that on two separate tracks for this type of scenario. Another possibility I’ve used is using Waves StudioVerse Effects to host the VST3 plugins and deal with the different left/right signal chains. It makes it pretty easy to do parallel effects chains on a single track, but, of course, overall plugin latency will vary depending on what plugins are used within it.
Personally I would load the amp simulation plugin in the Input Bus. And then create the audio tracks, all having their input set to the same bus.. No group track needed.