Waves Will NOT Be Supporting AAX-DSP!!!

[Bob Olhsson]

Do really efficient native plugins really bog an HDX system down that much?

[AINSLIE]

Originally Posted by Bob Olhsson

Do really efficient native plugins really bog an HDX system down that much?

It's latency issue first - I.e. Plugins are usable while tracking in DSP systems but not native. And you get all Native can do PLUS DSP when mixing. I'm not giving up DSP yet. Native is still not all the way there.

[Emcha_audio]

Originally Posted by Bob Olhsson

Do really efficient native plugins really bog an HDX system down that much?

No, but why waste time doing native plugins only, lose your market hold on the dsp market, because you don't want to run the same code (that is in the native) through a dsp compiler and do minor optimization?

[Emcha_audio]

I've sent an other email to them, being very very specific in what I asked. Let's see if they will respond I might have exaggerated very slightly on a few things, but I wanted a clear answer from them.

So let me be clear on this as this is really a source of frustration to others.

You are saying that Waves, will NEVER do a AAX-DSP plugin?

And to be sure that's it's clear. You will not port over the old tdm plugins to aax dsp. You will not run the plugins that you have made as native, into the dsp compiler.

Even though many other company's coders out there have stated that porting the Native AAX plugin into DSP is a breaze (run the plugin into the dsp compiler for aax and it's done) and only need a few touch up for optimization?

I'm trying to be very thorough in my question here because it makes no sense for any of us who owns waves tdm plugins, that you would leave this platform. It is selling well, it's close to 5 time more powerful than the older tdm platform. It's easier to make plugins that will sound exactly the same DSP to Native wise. You don't have to write 3 different codes anymore, as you only have to run your codes into the dsp compiler, audio suite compiler and native compiler, to have them ported over.

So the question that we have is this, if it's easy to do (as reported by many others plugins manufacturer) why would Waves decide to lose their market holdings and lose money? As stated, Avid is reporting that they were taken their pants down when they started to ship the HDX card, they were selling faster than they could manufacture them. So why would Wave decide to be left behind? Many Waves tdm users are stating now with the rumors, that if you guys do not make dsp port of your plugins, they will completely stop buying any of your products. That's a dangerous thing right now.

So Why?

[Darryl Ramm]

Originally Posted by Emcha_audio

No, but why waste time doing native plugins only, lose your market hold on the dsp market, because you don't want to run the same code (that is in the native) through a dsp compiler and do minor optimization?

I would not minimize QA and testing time/cost of doing this even if it is just 'throwing a switch' from a developer perspective (I don't know what actually is involved). But yes, I think it is an extremely bad mistake by Waves to blow off high-end users like this.

Darryl

[blairl]

Originally Posted by Emcha_audio

Well see that's the thing, I have and it's not clearly stated as "We will never support AAX-DSP". All they are saying is that support for AAX-DSP is not planned. Which is probably why Bill is asking for a copy paste of the email, because he might have received the exact same email as me, and like mine, it's not as a definite never.

[email protected]

Here's the meat of the response.

QUOTE

"Waves will not be supporting AAX DSP. AAX Native support however is planned at a later date."

END QUOTE

The email was dated today. Tim, the Internal Sales/Customer Support Manager replied. Anything you may have received in the past would be superseded by today's response.

I asked them a few months ago about their plans and received a similar answer to you: that there were no current plans to support AAX-DSP. In my most recent exchange, I asked them to clarify their future intentions for AAX-DSP. I'd say today's response is a pretty definitive NO.

[Emcha_audio]

Originally Posted by blairl

[email protected]

Here's the meat of the response.

QUOTE

"Waves will not be supporting AAX DSP. AAX Native support however is planned at a later date."

END QUOTE

The email was dated today. Tim, the Internal Sales/Customer Support Manager replied. Anything you may have received in the past would be superseded by today's response.

I asked them a few months ago about their plans and received a similar answer to you; that there were no current plans to support AAX-DSP. In my most recent exchange, I asked them to clarify their future intentions for AAX-DSP. I'd say today's response is a pretty definitive NO.

I received the email today also 21/06/2012 3:49 PM to be precise. Which makes 2 different answers, Your's which is definite, and mine that isn't.

[blairl]

Originally Posted by Bob Olhsson

Do really efficient native plugins really bog an HDX system down that much?

It's not that the system is being bogged down--at least for reasonable track counts. The latency of the system when introducing native plug-ins during tracking is the issue.

[Bill Denton]

Originally Posted by blairl

[email protected]

Here's the meat of the response.

QUOTE

"Waves will not be supporting AAX DSP. AAX Native support however is planned at a later date."

END QUOTE

The email was dated today. Tim, the Internal Sales/Customer Support Manager replied. Anything you may have received in the past would be superseded by today's response.

I asked them a few months ago about their plans and received a similar answer to you: that there were no current plans to support AAX-DSP. In my most recent exchange, I asked them to clarify their future intentions for AAX-DSP. I'd say today's response is a pretty definitive NO.

I'd say today's response is a pretty definitive NO.

And given the other information you've posted, I would tend to agree with you.

I'm an old geezer, and over the years I've had so much smoke blown up my ass that I can fart a forest fire...so I tend to "Joe Friday" things..."Just the facts, ma'am"...

And for you "tin foil hats" guys, this coming right behind the "no new Mac Pro" thing kinda makes you wonder what's going on...

[Emcha_audio]

Originally Posted by Bill Denton

I'd say today's response is a pretty definitive NO.

And given the other information you've posted, I would tend to agree with you.

I'm an old geezer, and over the years I've had so much smoke blown up my ass that I can fart a forest fire...so I tend to "Joe Friday" things..."Just the facts, ma'am"...

And for you "tin foil hats" guys, this coming right behind the "no new Mac Pro" thing kinda makes you wonder what's going on...

Well except that tim cook did say that there would be a new release in 2013 for the pro users. They have not either discontinued the mac pro or made any announcements of such. So that's really splitting the tin foil thin.