Has anyone made any significant progress with it that they wouldn’t mind sharing? I’m hoping to free up some schedule time towards the back end of this week to pick up AAX again so any tips/pointers people can offer would be very appreciated.
Myk
Nothing here, I’m afraid. Waiting like you.
Good news and bad. I actually got an AAX plug to build under XCode 4.4 (GM). That’s the first plugin I’ve gotten that far with. Booted up ProTools and got audio! Of course it’s not quite what I’d hoped for. A quiet oscillation, getting louder and louder louder and sending me scrambling for the level knob in my studio. If only that’s what I wanted I’d be done now.
I’d let your marketing department figure out how to sell it. :mrgreen:
This is actually great news. Have you tried the plugin as a VST or AU? I tend to develop the plugin as a VST/AU, and test in Ableton Live, then move on to the more “finicky” hosts (cough cough Logic cough cough) once the audio and GUI is working in Live.
Sean Costello
Hi Sean,
I’ve actually had the plugin running as AU/VST/RTAS for quite some time. It’s the change to XCode 4.4 bit that makes it an adventure. Plug’s now running fine under VST but I’m still running into build issues on AU and RTAS.
Ditto with 2.0.22
Rail
Parameters are not exposed to protools either.
Salvator
Jules…
Seems like there’s quite a lot of demand for this feature. Is this something that you’re actively working on, or is it on a back burner for you?
My ideal situation, of course, would be that you got it all working and we could just update to get your goodness, but I don’t know where its sitting in your priorities right now.
Please could you give us an idea about whether this is something you’re going to be checking in more stuff for in the near future which we could get, or are we better carrying on from here ourselves?
Thanks
Paul
I’m working on about 5 different projects right now, and AAX is just one of them! I’m going to spend a couple of days on it next week, so will hopefully make a bit more progress with it - hopefully when it reaches the point where the basic playback works, then people will start joining in and helping out a bit more to finish off the details…
Thanks Jules, I appreciate it.
I’m a little surprised that nobody has beaten me to this comment. A couple of days back, there was a note in the tip code indicating that more work had been done with AAX. I was busy in a few other corners and didn’t have a chance to try until today. Although I’m sure there’s still much to do, I’m happy to report that I got two plugins working (OSX)–audio and UI! That’s great.
It appears that PT10 does do the cert check beforehand, so you’ll probably have to be a Pace licensee to make it work. But work it does! Thanks Jules.
Yes, had no time to comment (or deep test) either, but it worked for me too. Exiting !
Jules, what does mean the comment in the commit ? (i.e “got basic audio”).
What’s left exactly ?
Salvator
[quote=“Salvator”]Yes, had no time to comment (or deep test) either, but it worked for me too. Exiting !
Jules, what does mean the comment in the commit ? (i.e “got basic audio”).
What’s left exactly ?
Salvator[/quote]
Well, I only gave it a very quick test! I’ve also not done any kind of parameter or state saving support yet.
I’ve discovered a few more issues with AAX. The first is that I can’t build under XCode 3.2.6. I’m using XCode 4.4.1 for my own work, but I’m doing some client work and the client would like the option of using XCode 3. The problem arises somewhere around juce_AAX_Wrapper.mm. Even though I’ve tried an exclusion macro, it seems that it’s getting multiple includes. This manifests itself as a error message indicating that ‘Component’ is already declared. I’ve spent a while trying to sort it out, but I’ve got to move on to some other things.
The other issue comes when I’m loading plugins under ProTools 10. The name of the plugin isn’t properly exported to PT. Instead of the plugin name, sometimes I see the 4-character product code and sometimes I see the comment. Sometimes I even see the plugin name.
Jules I know you’re busy with lots of things, but it would be nice to see you swing through the AAX neighborhood again.
Not much activity on the AAX front in recent weeks. I’ve seen a lot of checkins regarding Introjucer (which is of little practical value to many of us), while there are still a number of outstanding issues with AAX. With AES coming up in a little over a month, I know I’m not alone in feeling a little anxious about the state of it. Jules, what can you tell us about your ability to give some attention to AAX?
Sorry chaps, am being pulled in multiple directions at once! I’ve not forgotten, and have been feeling guilty about it: will do my utmost to spend a couple of days on it as soon as this projucer hubbub dies down…
I’m trying to build AAX under Visual Studio 2010. I’ve discovered that[color=#0000FF] juce_AAX_Wrapper.cpp[/color] doesn’t include [color=#0000FF]Windows.h[/color]. Seems that it should.
We have been working toward integrating aax into one of our plugins and have had some success on the mac. With the exception of parameter saving it appears to be pretty much there. I will soon take a look at the parameter saving code and can post some snippets when I’ve got it all sorted out if that helps anyone?
In the meantime, I have started to look at windows aax and have also had some progress. We have found the following is consistent across our internal plug-in and the JuceDemoPlugin.
Changes required to get windows aax plugin loading into protools on windows
- Needs to include either <windows.h> (or a juce equivalent?)
- Change project compile flags from /MT to /MD
- remove const from GetEffectDescriptions(class AAX_ICollection *)
- The generated file should have the extension ‘.aaxplugin’ (currently .aax)
This created a compiling aax plugin which I signed using PACE ashelper tool. The plugin was listed in the Pro-Tools plugin list and when opened immediately crashed with an address access error. Commenting out the call to ‘addBypassParameter();’ in EffectInit removed that particular crash (I haven’t looked into the exact cause within that function at this point, but will post what I find when I get the chance). Without that function call the plug-in will render for a few seconds before hanging and taking down Pro-Tools with it. This occurs in the JuceDemoPlugin as well when following these steps.
Jules, Is there a chance you might get a moment to look into this? We think it’s probably not far off but we are having difficulty tracking down the cause of this latest hang.
I’d like to second myk’s request. I’ve also noticed that the aax plugin name isn’t properly reported in ProTools 10. It appears the plugin description is often returned as the name.
With AES approaching in only a month, I’m sure there are a few of us who’d like to see the AAX support completed.
Thanks, I’ve done some quick fixes for those things.
Not really sure why the bypass would cause any problems… Did you know that you can download a debug version of PT which lets you load unsigned plugins and debug them?