#Avid hybrid engine how to

But, our betas have been absolutely loving it and we're looking forward to all HDX users getting their hands on it very soon.Ĭongratulations on what I can only guess must have been a huge project.

#Avid hybrid engine how to

It's definitely a paradigm shift in how to think about DSP and mixing compared to HDX Classic. For example, bussing drum tracks in Native Mode to an Aux Input track in DSP Mode running DSP plugins. That said, if you wish to leverage DSP for mixing you can still do that by routing to tracks in DSP Mode. By splitting Native and DSP performance these issues are eradicated and complexity is significantly reduced.

Both of these are problems with HDX Classic and result in bottlenecks in performance and hard limits on session size. It also eats into the hardware-based voice count because audio paths are needed for these roundtrips. This increases system latency which means control surfaces feel less responsive because your fader/knob moves are latent. For mixing workflows where you don't care about low latency monitoring, the combination of Native and DSP plugins is also problematic because it forces the audio to round trip between the DSP and host. If the combination of active Native and DSP plugins is allowed, you are guaranteed to not have a low latency monitoring on that track. The philosophy behind the Hybrid Engine design is that you leverage host processing by default, then have on-demand low latency monitoring via DSP Mode. Further, can you give us any insight into why the new Hybrid mode can't run the traditional combination of Native and DSP plugins on a track (when not in Input or DSP Low Latency mode of course)?