|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Shall we really...
...celebrate any announcement of a new AAX Native only Plugin?
I mean: Is this a misleading sign for the companies that we are satisfied with Nativ and don´t need the DSP versions anymore?
__________________
www.srs-mastering.de Mac Pro 6.1-8core, OS 12.6, PT2023, HDX2, Sonnet Echo Express III-R, Madi Interface. |
#2
|
||||
|
||||
Re: Shall we really...
Well I'll leave the celebration-thing alone. What I do agree is that the plug-in companies should clearly mark if their plug-in is:
AAX-Native or AAX-DSP or AAX-Native and AAX-DSP. I have seen that a lot of the companies simply list that the plug-in supports AAX. And that's it. I think that is misleading and that every single plug-in should be clearly marked what it really is. That should be a necessity, not an option.
__________________
********** Main DAW: MacPRO 7.1, 16-Core Xeon 3.2GHz, 196 GB RAM, OSX 10.15.2, HDX3, PT 2019.12 Ultimate, 2x UAD-2 PCIe Octo's, Raven MTZ, 1x HD Omni, 2x HD I/O's, 1x MTRX and some more cool stuff... Auxilary DAW: MacBook Pro with Retina Display (2012), 2.6GHz quad-core Intel Core i7, 16GB RAM, OSX 10.13.6, PT2019 Ultimate, 1x UAD Apollo Quad Audio Interface /w Thunderbolt Interface (v9.x) ********** |
#3
|
||||
|
||||
Re: Shall we really...
Very recently Native Instruments announced AAX versions of Massive, FM8, Reaktor and Absynth.
I still dont know if its DSP as well as Native.
__________________
Kind Regards Peter www.peterjuulkristensen.com http://www.facebook.com/mixingmusic |
#4
|
||||
|
||||
Re: Shall we really...
My bet is native. My hope is DSP as well. I know that a lot of people wonder why DSP would be needed for a VI PI (since data/library still needs to be read via a HDD/SSD) but I would still like to see DSP based VI hosts because of stability/resource off loading reasons.
I am talking about VI hosts such as NI, Play or VSL. Guitar sims like Eleven do not fall into the above as they can clearly work DSP as a whole.
__________________
********** Main DAW: MacPRO 7.1, 16-Core Xeon 3.2GHz, 196 GB RAM, OSX 10.15.2, HDX3, PT 2019.12 Ultimate, 2x UAD-2 PCIe Octo's, Raven MTZ, 1x HD Omni, 2x HD I/O's, 1x MTRX and some more cool stuff... Auxilary DAW: MacBook Pro with Retina Display (2012), 2.6GHz quad-core Intel Core i7, 16GB RAM, OSX 10.13.6, PT2019 Ultimate, 1x UAD Apollo Quad Audio Interface /w Thunderbolt Interface (v9.x) ********** |
#5
|
||||
|
||||
Re: Shall we really...
Quote:
|
#6
|
|||
|
|||
Re: Shall we really...
Quote:
Actually, Pro Tools accesses the data on a "drive" that exists in memory, the HDX card doesn't directly access memory... And to drift back toward where the thread is heading, while Avid might have some tricks up their sleeve, I don't really think there would be much to be gained by shifting VI's to a DSP card. It's possible that some of the "effects" embedded in VI's (EQs, reverbs, dynamics) might benefit from a DSP card, the small gain probably wouldn't be worth the effort of coding it...
__________________
X Note that all opinions, observations, whatever, in this post are mine, unless I'm being mean or am wrong, in which case it's somebody else's fault. I do not work for Avid (their loss)...my only relationship with Avid is that of a customer (when I'm not too poor to buy stuff, like now)...and that hot administrative assistant...that's more of a "thing" than a "relationship" (that should keep them guessing for a while...) Just rockin'...what more is there? Bill in Pittsburgh |
#7
|
||||
|
||||
Re: Shall we really...
Quote:
Of course though that's the traditional use of disk cache or more properly named ram disk. If Avid is using something else and naming it disk cashing, then it's a bit off. But in this case, they are using it right http://www.youtube.com/watch?v=0JHAH...feature=relmfu And doofus me I just saw your " " around the drive haha... *slaps forehead* |
#8
|
|||
|
|||
Re: Shall we really...
Considering NI have never done DSP, they're unlikely to start doing it now.
|
#9
|
|||
|
|||
Re: Shall we really...
And I don't think they've ever needed to. The clue is in the companies name!
|
#10
|
|||
|
|||
Re: Shall we really...
Any company showing a commitment to the future should be encouraged for the move
native to native = OK (most VIs fall in here) DSP to DSP = should be expected DSP to native = golf clap at best native to native + DSP = standing ovation
__________________
... "Fly High Freeee click psst tic tic tic click Bird Yeah!" - dave911 Thank you, Craig |
|
|