AnsweredBypassing FX/plugin and plugin latency

Author
tnipe
Max Output Level: -89 dBFS
  • Total Posts : 91
  • Joined: 2015/02/14 06:13:42
  • Status: offline
2017/10/18 23:13:53 (permalink)

Bypassing FX/plugin and plugin latency

Hello. As far as I can tell, when bypassing a plugin in the FX bin, the latency introduced by that plugin is still present. In Pro Tools, there is something called "Make inactive" when right clicking on a plugin insert. In Reaper, it's "Offline FX". This has been practical when needing zero latency for tracking, especially for certain plugins on the master fader. Does anyone know if there's similar functionality in SONAR?
#1
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/18 23:18:38 (permalink)
Bypass the FX rack using the FX rack context menu (right-click in the rack to display the context menu). Click on the FX button in the Mix module or "E" on the keyboard to bypass all plug-ins. While reading the help about the FX button in the Mix module, take a look at the PDC button too.
#2
tnipe
Max Output Level: -89 dBFS
  • Total Posts : 91
  • Joined: 2015/02/14 06:13:42
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/18 23:34:39 (permalink)
So the only way to bypass the latency introduced is by bypassing the FX rack entirely? The PDC button could be a nice solution.
#3
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/18 23:41:41 (permalink) ☼ Best Answerby tnipe 2017/10/19 11:16:58
Yes
#4
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
  • Total Posts : 26036
  • Joined: 2006/09/17 11:23:23
  • Location: Everett, WA USA
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/19 00:41:41 (permalink) ☄ Helpfulby tnipe 2017/10/19 11:17:00
Well, it sounds like a good idea, letting you disable PDC on a track-by-track or per-plugin basis, but in practice it can make tracking much more difficult. Just ask anybody whose audio interface doesn't report its own latency correctly how much even a few milliseconds' time shift matters. 
 
If you have high-latency plugins in the chain and you're still in the tracking phase (don't do that!), or even if you're just overdubbing a list-minute addition/correction, you're really better off doing a global bypass or using the Live Input PDC Override feature and thus remove PDC from the equation altogether. 
 
 


All else is in doubt, so this is the truth I cling to. 

My Stuff
#5
tnipe
Max Output Level: -89 dBFS
  • Total Posts : 91
  • Joined: 2015/02/14 06:13:42
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/19 11:17:17 (permalink)
I went ahead and made a feature request for this:
https://bakery.cakewalk.c...fline-inactive-plugins
#6
azslow3
Max Output Level: -42.5 dBFS
  • Total Posts : 3297
  • Joined: 2012/06/22 19:27:51
  • Location: Germany
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/19 12:12:00 (permalink)
May be irrelevant, but "Bypassing" a plug-in using its own button (most plug-ins have such a button) is not only different from bypassing it with global FX button but also different from "disabling" the plug-in in the FX bin ("Power" button for each plug-in). I mean the resulting sound is the same in all 3 cases, but only last 2 options remove delays.

Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
#7
Jeffiphone
Max Output Level: -87 dBFS
  • Total Posts : 173
  • Joined: 2014/09/27 19:58:17
  • Location: Santa Rosa, CA
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/19 16:04:58 (permalink)
You may want to try using the Mix Recall function. I have saved one Mix Scene for tracking, and one for mixing. The tracking scene has only a few plug-ins turned on, mostly just guitar plugs (Amplitube). On this scene there are no ProChannels on, no Bux FX, and no track FX except Amplitube on a few tracks. For tracking in this scene, I just lower the settings on the interface to 64 or 128ms, then record the part. 
 
Once the part is recorded, I save the scene, save the project, then switch back over the Mixing Scene. With this scene, all the PC modules are turned on, as well as all the track and buss FX.
 
This is one of the best features in Sonar, imho. I use it every day. It works great if you need to add a new part to a song, or re-do an existing part. 
 
~Jeff

Acer with i7 processer - Sonar Platinum 64bit - Windows 10 64 bit - Focusrite Scarlett 2i2 (2nd Gen) -
#8
ryecatchermark
Max Output Level: -89 dBFS
  • Total Posts : 87
  • Joined: 2015/06/08 01:23:28
  • Status: offline
Re: Bypassing FX/plugin and plugin latency 2017/10/19 16:27:19 (permalink)
Just curious... I did a loopback test the other day with Sonar Platinum and a RME Babyface Pro. I had a session with lots of tracks and plugins, some of which were linear phase and look-ahead plugins, which I am assuming are creating some latency. I left all the FX enabled and left PDC on, solo'd my drum tracks and recorded the stereo output directly back into the stereo input. (The master bus has some hefty plugins on it as well). The resulting recording was perfectly in time and in phase with the original drums. Does this mean I can leave everything enabled and record a brand new overdub to a new track with no plugins on it and have the new track be in sync to the way I played it, or am I missing something? In the past I would just make a quick bounce of the mix in progress, disable FX and PDC, and record overdubs to the temp mix, then put everything back on again. Thanks, Mark.

Mark K.
Asus G752VY Laptop.  Intel Quad i7 6700HQ 2.6 GHz. 32 GB RAM. NVIDIA GTX 980M. Windows 10 Home 64bit. MOTU 828x.
#9
Jump to:
© 2024 APG vNext Commercial Version 5.1