Transition to AAX: A Real Programmer's Perspective

[daeron80]

Originally Posted by DaveTremblay

all bridges come with some significant tradeoffs...

Like trolls, e.g.

Ahem.

Seriously, I hope fxpansion or somebody will do a VST to AAX wrapper. Not looking forward to losing access to all my VSTs. Hopefully it will be somebody who will pay attention to it, update it, and make it work like something that doesn't feel like some kid coded it for Win95.

[Top Jimmy]

Originally Posted by daeron80

Seriously, I hope fxpansion or somebody will do a VST to AAX wrapper. Not looking forward to losing access to all my VSTs. Hopefully it will be somebody who will pay attention to it, update it, and make it work like something that doesn't feel like some kid coded it for Win95.

See post #14 http://duc.avid.com/showthread.php?p=1852716

[tamasdragon]

I always had very mixed results with wrappers, but never had completely flawless operation. I try to avoid them these days.

[daeron80]

Woo hoo! Thanks for that. fxpansion's always works flawlessly for me. The only problem with it is the rudimentary interface. It's not really suitable for dealing with more than a couple dozen plugs, and most of us have hundreds.

[OSXPCUser]

Hi,
I have I few questions about the new AAX plugin file structure.
Does the AAX plugin have a .aax file extension and
is it stored in the same file directory as RTAS and TDM plugins
or is it .dpm ?

please explain

/TIA


please explain

TIA

[LukeHoward]

Originally Posted by OSXPCUser

Hi,
I have I few questions about the new AAX plugin file structure.
Does the AAX plugin have a .aax file extension and
is it stored in the same file directory as RTAS and TDM plugins
or is it .dpm ?

On the Mac, they're stored in /Library/Application Support/Avid/Audio/Plug-Ins, and the bundle extension is aaxplugin.

[daeron80]

On Windows they're stored in the same folder as the dpms, and the extension is .giganticleapinsoundandspeedaaxpluginsothere. j/k.

[pcmusicpro]

"Some question why Avid didn't simply adopt AU or VST -- a few simple reasons are these: AU is a mac-only spec, and VST simply doesn't have the power and flexibility to do everything RTAS/TDM and AAX are capable of."

I would like to know exactly what RTAS/TDM and AAX can do that VST can´t.

[John_Toolbox]

Originally Posted by pcmusicpro

"Some question why Avid didn't simply adopt AU or VST -- a few simple reasons are these: AU is a mac-only spec, and VST simply doesn't have the power and flexibility to do everything RTAS/TDM and AAX are capable of."

I would like to know exactly what RTAS/TDM and AAX can do that VST can´t.

Integration with their dsp chips and with pro tools itself come to mind. I'm guessing that converting all of the stock protools plugins to aax and keeping them somewhat backwards compatible was a lot less work than completely rewriting them as vst, and then trying to get them to work with the hdx hardware.


Sent from my sub-epic jailbroken and unlocked iPhone 3g running on a cheap pay-as-you-go T-HOBObile plan using Tapatalk

[roberts]

PT 10 HD TDM will be are for a while with a lot of users.
Plug-ins like TC/Line 6 (TDM). A lot of users are not going to like giving those up. Plus a lot of users are not to like the high cost of plug-ins companies like Sonnox->AAX upgrade.
While I do understand that they certainly a high cost to program for a new format. I think for some not all users it going to put the bakes on getting ride of HD / TDM and moving to HDX. We spent 25K moving PCI-X hardware to PCIe
It's going to cost me 75K (including my Plug-in "gestimates") to go to HDX
I am putting the breaks on that. We may buy 2 systems as we expand but there is no way I am changing out all my HD rigs in the foreseeable future.