DSP Plugins on Master Fader are being repurposed as Native
 

Hi folks,

Searched the forum here and couldn't find anything about this...

I just pulled the pin and did the HDX upgrade on Friday, and I'm having a couple of growing pains here.

I have an AAX-DSP instance of MDW EQ and an AAX-DSP instance of Impact on the master fader. Both of them are being repurposed as Native to allegedly improve my voice count, but I'm confused. Why is ProTools giving me no choice in the matter? They end up having about 2500 samples of delay, and that's not acceptable for a tracking session...

Why would ProTools think that a master fader that is running in the hardware DSP environment would be better off running Native plug-ins? That would only make sense if it was running on HD Native...

There may have been an L2007 sitting deactivated below these, but I'm pretty sure I tried deleting the L2007 and it's opening the same way.

Is there a workaround for this? Clearly, the check box for "Open Unresourced DSP Plug-ins as Native" is unchecked...

Any suggestions or workarounds are welcome!

Cheers, eh?

Re: DSP Plugins on Master Fader are being repurposed as Native
 

Can't you just select between Native and DSP in the plugin window?

Re: DSP Plugins on Master Fader are being repurposed as Native
 

Yes he can switch between dsp and native in the plug in window. What pro tools is doing is changing dsp plug ins after native plug ins to native. Pro tools will do this in every start up, when it makes sense. OP do you have any native plug ins on the buss feeding the master fader? Last one on the aux or whatever?