Hey, how can I add the analyze button and process (like Nugen LMCorrect or the “learn” button on RX Ambience Match) to my AAX plugin using JUCE AAX wrapper?
Is it possible? Is it worth the effort?
Thanks.
1 Like
As far as I know, the JUCE AAX wrapper does not support the AudioSuite style functions since those are not available directly with the other plugin formats like VST or AU. JUCE mostly provides features that are common to all the supported plugin formats.
1 Like
Thanks Xenakios, I got you. But I don’t understand why does the render button work if I open my plugin in Audiosuite. It requires to override the AAX RenderAudio function, but it is not implemented by JUCE. If I could understand why it works, maybe I could apply the logic to the AAX AnalyzeAudio function… maybe
The AudioSuite feature in ProTools was changed at some point to allow AAX plugins to be used with AudioSuite and JUCE supports that. But it’s only for doing the same kind of audio processing you do in real time too. (I should have written above “JUCE does not support the AudioSuite specific functions like reading audio directly in an offline manner from the files selected in ProTools”.)
You could of course attempt to change the JUCE AAX wrapper code to allow to do what you want to do. But even if someone knew (I don’t) how to do that, it couldn’t be discussed because of the AAX licensing limitations.
2 Likes
You might be interested in this 
:
3 Likes
Yep, it is exactly what I was looking for. I implemented their modded modules and work fine. So thank you so much and thank Sound Radix.
2 Likes
Hi,
I’m a beginner in your exact situation. I know this was ages ago, but how did you import the SoundRadix to your project? E.G did you have to override the existing juce_AAX_Wrapper.cpp ? I’ve never imported a library, the fact that Sound Radix is not ‘new files’ but instead ‘modified existing JUCE files’ makes me worried about messing up the default JUCE files.
If you could provide some guidance I’d be super grateful 
Hi @voluntaryzonkey, as you’ve also PMed me I’ll answer you privately but it feels you’ve missed the idea of forking and branches of GIT version control.
I’ll provide deeper explanation as a PM which is more suitable.
1 Like
hey guys, is this still true or newer versions of JUCE have affected the AAX wrapping?
its still true
We would very much like to have the AAX Analyze feature in JUCE without using a fork. It’s one of our most common feature requests.
1 Like
Why not use a fork?
From our experience using a JUCE fork has been a must for us. JUCE tries to cater to a wide audience but sometimes your specific needs may differ. Maybe you wanted to develop a plugin with a side-chain before JUCE supported it, or maybe your customers hit a bug that is less prioritized by the JUCE team. You can ask and wait and hope or you can use a fork.
2 Likes
Yea, we use a fork internally ourselves as well, though we try to keep it as close as possible to mainline JUCE since updating, bug reporting, etc. all become a bit more difficult.
For feature requests, we generally ask first, since it’s often something that would benefit the JUCE community as a whole, before going it alone or doing it in a patch / fork. We do appreciate the Sound Radix fork though!
3 Likes
Indeed that’s a very important goal as it tames the merge conflicts burden.
That’s always better and makes broader availability of the feature.
Always better to start trying to get it into vanilla JUCE. But, it’s a mixed bag.
Here are two feature requests, one is within JUCE already, the other is yet to be evaluated:
Add AAX - isRecording support - #3 by ttg (Included in JUCE)
Pro Tools Tempo "Resolution" Issue - #2 by ttg (Not yet available)
1 Like