June update - hybrid info
 

looks like we're getting an update this month according to this mailout from Westlake. good stuff, not sure if they've jumped the gun slightly on this announcement

https://westlakepro.com/avid-pro-too...HDX+this+Month

Re: June update - hybrid info
 

Nice, I have said it before, Avid should have all Pro tools engine on native. Hybrid means all the audio engine is native but uses the hdx chips for plugins. Wich is cool.

Their next step is to eliminate voices.

And I really hope they eliminate or upgrade the 32 I/O limit.

Re: June update - hybrid info
 

It's probably all good. Avid published its June release back in March - https://www.avid.com/resource-center/hdx-hybrid-engine

I'm looking forward to it. From the sounds of some of the chatter in the Eucon sections of the forum, it seems like there will be a pretty tasty update to EuControl too.

Re: June update - hybrid info
 

More to it than that. The Carbon is the demo of the Hybrid engine. If you have the channel in DSP, no Native allowed.

HDX allows a mix. If you've mixed with both, you'll understand the issue here (when latency isn't an issue but you want to share resources between native and dsp).

Re: June update - hybrid info
 

I hope they've re-coded the entire audio engine to be more efficient and stable, soup-to-nuts, and that it's even smoother with Virtual instruments. That's all. I mean, I'd really like the MIDI stuff, new shortcuts and Sample-Rounding Error fixed, as I've been requesting. But if I'd bought that HDX card a decade ago, instead of the HD|Native card (after selling my year-old HD Accel cards to do so), maybe I'd be bouncing merrily along.

Re: June update - hybrid info
 

What happens when you engage DSP Mode on a track on a Carbon system that doesn't have input monitoring or record armed?

For what it's worth, I think the same DSP plugin before native plugin trick still applies with the Hybrid engine. If you toss a DSP trim plugin before your native plugins, the native plugins won't be bypassed when the channel is record/input armed.

Re: June update - hybrid info
 

So I don't know about current HDX as I went from LE to HD Native to Carbon Hybrid

But as far as Carbon Hybrid operation

Not sure I understand the question But what happens is the track goes into DSP mode and is running on the HDX chips, regardless of being record or input monitoring armed or not .


Assuming that's how it works on current HDX ??
Then no that is not what happens with Carbon DSP Hybrid
With Carbons current Hybrid implementation,,, It is a one or the other not both, on any single track

In Carbon while you can have a mix of tracks in the same session some in DSP mode and some in Native mode,,,,,,,,, BUT on any single track if in DSP mode, any Native mode only plugins ( not AAX-DSP capable) will be bypassed, regardless of order, does not matter if you put a DSP trim plugin first.

So to recap
#1 On a track that is put into in DSP mode any Native plugins (already on the track before being put into DSP mode) will be bypassed.... And when a track is already in DSP mode you can't put a Native only plugin on it , the only plugin selections you have are DSP capable plugins

#2 On a track put into in Native mode all plugins will be switched to Native mode

Re: June update - hybrid info
 

So what happens on an Instrument Track with a native VI on the first insert? Can that be switched to DSP mode?

Re: June update - hybrid info
 

Again the insert slot position is irrelevant in terms of mode selection or operation (DSP or Native) . And yes an instrument track can be switched into DSP mode BUT any Native VI plugin will be auto bypassed.

Here a quick off the cuff very brief summery Video I did for some guys in another forum ( don't remember If I have linked it here or not) who were asking about Carbon and DSP

https://youtu.be/YFhujEU8X30

Re: June update - hybrid info
 

Thank you for that video.
Could you explain a little more about how "DSP Mode Safe" works? If there is more to it than in the video.

Thanks