Plans for VST Adapter Support in Pro Tools 11

[WorldStudios]

Thats right. It is not a new format to replace the others. It is a third one, where you in a reverb could have early reflections computed on hardware/hdx and the loooong tails done natively. That way you would get the best of both worlds. The zero latency and firm dependability of the hw and the massive computing power of native. Win!

[Firechild]

Hybrid plugin is nothing new. TC Electronic made one called Tubifex, running on the Powercore platform. However I guess most of the processing took place on the native CPU in reality. The plugin latency is huge with this plugin.

The Duende software V3 used hybrid processing but I think it was just another way to say that the PCIe hardware was just a dongle. A couple of months later the native Duende plugins came out.

My apologies for saying that AVID is charging the developers for selling AAX plugins, just rumors , I may be wrong about this , sure PACE is charging but that is the point with their business...

[Bharath]

Not really. Once you have shipping plugins and more details emerge on how exactly this works you might change your mind.

[Carl Kolchak]

Originally Posted by Bill Denton

From the horse's mouth...

http://www.avidblogs.com/aax-the-evo...of-a-platform/

You guys really should try using the Search...

Nah! I don't need to use the search function. I need to use my woeful medium term memory

Now that you've jogged my memory (I did read that article when Dave first published it), I seem to remember Rich Holmes going in to some "detail" about AAX Hybrid in the PT11 Q&A video :

In sort of vague, layman's terms, he mentioned that certain aspects of a particular process, could be addressed in the different domains, where DSP can take care of low latency aspects, and Native can take care of high RAM requirement aspects (such as reverb tails) simultaneously, to make the system as powerful and efficient as possible.

From what I remember, the whole audio engine (AAE) was coded for this, but at the moment there aren't any plugins taking advantage of it.

[TheJamsh]

http://duc.avid.com/showthread.php?t=342309

^ I'm just going to leave this here.

[ionactive]

Amazed that VE PRO 5 is not mentioned more. It works perfectly in PT 10 (latest version). I actually use it now in preference (for most cases) for a direct insert into PT. I let PT worrying about running the show and VE Pro 5 doing the hard number crunching.

As long as :

1) I can have PT and P11 on same system (I can)..

2) That installing PT11 does not muck up my PT plug in locations (etc) ..

I will go for PT11, using VE Pro 5 (as I have to) and wait for more compatibility (e.g. all the NI stuff I have)...

The reason I have not yet gone for PT 11 is I am nervous the install might muck up / break my plugins that do work perfectly in PT10 currently.

[musicman691]

Originally Posted by ionactive

Amazed that VE PRO 5 is not mentioned more. It works perfectly in PT 10 (latest version). I actually use it now in preference (for most cases) for a direct insert into PT. I let PT worrying about running the show and VE Pro 5 doing the hard number crunching.

As long as :

1) I can have PT and P11 on same system (I can)..

2) That installing PT11 does not muck up my PT plug in locations (etc) ..

I will go for PT11, using VE Pro 5 (as I have to) and wait for more compatibility (e.g. all the NI stuff I have)...

The reason I have not yet gone for PT 11 is I am nervous the install might muck up / break my plugins that do work perfectly in PT10 currently.

VE Pro does get a lot of mention around here - you may not have noticed that.

PT 11 does not muck up your plugin locations, at least not on a Mac. I understand there's a folder location change on Windows machines though. Just watch when starting PT 11 and it does it's scan and comes up with plugins not compatible with PT 11 and offers to move them to the unused plugins folder - don't let it do that or you'll have a nasty surprise when you go back to PT 10. Just let them stay in the regular .aax used plugins folder and you'll be good to go.

[Weg]

I was thinking about this he other day. What criteria define when a vst plugin can be used in PT11? By looking at the current options, it seems to me to be

-you can load vst plugins just as long as it is just awkward enough to kill your usual workflow

I would have bought Nomad Factory's Magma for just the vst hosting. The demo worked well enough for what I need, but when opening the plugin, you have to make additional clicks and mouse moves to get the vst plugin window up which is time and energy added to the whole effort of getting PT11 up and running in a usable manner.

Im sure anyone wishing to make a "volume level" plugin which simply has a fader or something equally perfuctory on it but will also host "clearly labeled vst's" would have no shortage of customers.

From what I read this would be the only hoop to jump through. I cant see this being allowed though which begs the question, why bother allowing it at all?

[musicman691]

Originally Posted by Weg

I was thinking about this he other day. What criteria define when a vst plugin can be used in PT11? By looking at the current options, it seems to me to be

-you can load vst plugins just as long as it is just awkward enough to kill your usual workflow

I would have bought Nomad Factory's Magma for just the vst hosting. The demo worked well enough for what I need, but when opening the plugin, you have to make additional clicks and mouse moves to get the vst plugin window up which is time and energy added to the whole effort of getting PT11 up and running in a usable manner.

Im sure anyone wishing to make a "volume level" plugin which simply has a fader or something equally perfuctory on it but will also host "clearly labeled vst's" would have no shortage of customers.

From what I read this would be the only hoop to jump through. I cant see this being allowed though which begs the question, why bother allowing it at all?

Vst format plugins do NOT run in Pro Tools. It's either RTAS (PT10 and earlier) or aax (PT 10 and PT 11). Magma as you say can host vst plugs - so you need to do a couple of extra mouse clicks - learn to live with it if you really want to run some ancient vst format plugs which aren't being ported over to aax. Or use VE Pro for your vst plugs if you're on a Windoze computer.

[Weg]

Originally Posted by musicman691

Vst format plugins do NOT run in Pro Tools. It's either RTAS (PT10 and earlier) or aax (PT 10 and PT 11). Magma as you say can host vst plugs - so you need to do a couple of extra mouse clicks - learn to live with it if you really want to run some ancient vst format plugs which aren't being ported over to aax. Or use VE Pro for your vst plugs if you're on a Windoze computer.

Kinda missed my point.

My point is that the line between disallowing a wrapper and allowing vst hosting within an aax plugin appears to be one of a level of inconvenience to the user. Maybe if you added a pan pot to my suggested volume plugin it could be a "muti-effect" and therefore qualify?