Main menu

You are here

Navigation

Search Forum

Search Forum

Forums

Novation Automap and AAX Plugin Support

As the Novation community has developed over the years, it has naturally found the bulk of it's voice on Social Media.
To ensure we can be there to discuss and support you as best we can, we’ve decided to close the forum.

Instead of posting Novation's official stance on this subject in another thread where it may not be easily found, I have decided to create a new post.

As I said 48 hours ago, a meeting was called to discuss the future of Automap and AAX Plugin support. Below is the resulting response from Paul Whittington, the Senior Product Manager for Automap.

Thank you once again for your exceptional patience in this matter.Paul and myself will be here to field any questions you may have, so please feel free to get in contact.

Sincerest regards,Taylor

----

Novation Automap and AAX Plugin Support

Here at Novation we have been wrestling with the AAX and Automap problem for quite some time now. We are aware that there were inquiries about this as far back as May last year and will admit that it has not had our full attention over this period with all the myriad of activities going on here. For this we apologise. What I can say is that we are seriously focused on this issue right now and what to do about it.

We have uncovered the complexity of the problem. Basically Automap works by 'wrapping' plugins which involves adding a small piece of code to each one to allow the Automap server to talk to it. AAX plugins are code-signed and what that means is they can't change, therefore the 'wrapping' system simply can't work.

We've also had a good deal of discussion about the 'wrapping' mechanism in general. Over time and via customer feedback we have observed that this way of working is not really what people want. It tends to cause session incompatibility, can result in crashing plugins sometimes and has created a huge maintenance burden with the sheer number of plugins out there.

So what do we plan to do about it? Well, we're talking to Avid. We believe the only way to tackle AAX plugin support properly is to integrate with Pro Tools directly. We firmly believe this is the best and only way to make AAX plugins work properly with our products.

When we created Automap it was a clever way to get around all the various methodologies that DAWs (Digital Audio Workstations) use to control plugins. As MIDI learn has become much more common and as Automap has dated we have brought in a new technology fairly recently with our Launch range of keyboards called InControl. What this means is we are removing the need for running an intermediate piece of software and instead talking directly to each DAW using either custom scripts or HUI. We have implemented basic mixer, track and transport control so far and we plan to develop this technology further to tackle plugin support.

While we continue to work towards a solution with Avid, it is still possible to work with Automap in ProTools for mixer and transport control even though it is not possible to control AAX plugins at this time. The setup guide for Pro Tools will take you through the steps needed to get this to work using a HUI control device.

Finally, we will be changing our messaging in light of the release of Pro Tools 11 to clarify the fact that Pro Tools support is for mixer and transport only and does not include plugin control. We never had any intention of misleading customers but we accept that as things have progressed our messaging has become increasingly vague. This is something we are working to correct now.

I and the company sincerely value all your feedback so if you have any queries please do get in touch. I will be closely monitoring this thread. We also have one of the best music recording customer service departments in the world (I certainly think!), with a large team in the US and UK who have helped many Pro Tools users get the best out of their Novation products.

I own a couple of controllers and have always considered Automap and Remote SL's to be best in their class for controlling multiple DAWs and thier plugins. I am excited to hopefully see new products in the higher-end controller market ranges from you that make use of your experience getting Automap to work so well with multiple DAWs. Moving forward, Pro Tools 11+ compatibility is essential to my continued use of your products. Is there a way in which we can help by contacting AVID and letting them know that Novation is an important partner and to please open the door to you? Please let us know how you would have us reach out to AVID. On the other hand, is there any possibility of Novation making the Remote SL and other controllers Eucon 3 compatible? That would be pretty sweet, because an AVID S6 is destined for one of our rooms, and Novation consoles running Eucon or a fully compatible Automap in the other rooms would be fantastic.

We have uncovered the complexity of the problem. Basically Automap works by 'wrapping' plugins which involves adding a small piece of code to each one to allow the Automap server to talk to it. AAX plugins are code-signed and what that means is they can't change, therefore the 'wrapping' system simply can't work.

Dear Paul,

The code-signing required by AAX has been known about for at least a year. It seems rather disingenuous for you to suggest that you are only now realizing that this will be an insurmountable hurdle for the Automap wrapping scheme.

I completely see where you're coming from on this (trust me, it was my message to customer support that got this response!) but I think Paul is suggesting that it has been a problem within Novation since the AAX announcement.

It's not that they're only just discovering this problem, just that they're only just telling us they've discovered this problem.

We are actively working towards a solution with Avid, one that integrates with Pro Tools directly. We are focused on finding the best solution to AAX support. When we have a solution we will decide how that is best delivered but we do intend to provide the new support to SL MK II users.

Is the SL mkII range be the only current Automap product range you are planning on supporting? i.e. no Nocturn, Impulse etc.?

I too would like to know about this (specifically, in my case, The Nocturn). Thank you

Just to let you know mate, I emailed Tech Support about this and got a response saying that was merely addressing the majority of the users requests here by mentioning the SL range. All other ranges are still good as usual including your nocturn :)

I must admit to a little confusion over the Novation response to the question of the future of Automap. The original thread wasn't exclusively on AAX as the OP noted. Rather it seems to me that there is a considerable gap in scope between "We have called a company meeting regarding Automap and its future. We aim to have an official and honest response for you within 48 hours." and the tightly crafted "Novation Automap and AAX Plugin Support" response.

Novation/Focusrite is a significant company but this gap is more typical of a smaller operation. A roadmap would be good. I see in the job descriptions that Product Managers "Support the Senior Management Team in meeting agreed business goals by leading the generation of long term 3-5 year Product Roadmaps that meet ambitious, but achievable company revenue growth targets."

I appreciate that control surfaces exist in a dynamic difficult space ... Cubase 7.5 is out today. Some of the problems of the 'wrap' model are identified above. Nektar is providing some competition.

I can assure you I do read the forum in its entirety - this post will not be left forgotten.Apologies for the delay in the response - I tarried when I should have passed on Paul's message as soon as I received it.

We hope you are also fixing various issues and strange random crashing caused by Automap wrapped plugins with Cakewalk Sonar X2 and do further test with Sonar X3.I've stopped using Automap months ago frustrated by all that weird crashes.

I have a Remote SL 61 MKII. I recently updated to Pro Tools 11x. I already know that Automap does not work with .AAX plugins. I can live with that for now. However even the keyboard does not work in PT11 so I cannot play virtual instruments. I searched on the web and found that I am not the only one with this problem. Is this "normal" as far as Automap 4.7 goes? Or do I have to go back to my X-Station to play virtual keys or even buy a controller of a different brand? I have owned Novation controllers since 2003 but this is unacceptable. Can anyone tell me if this is a known issue and if it will be addressed? Before I sell this 61 key paperweight and buy M-Audio? PS - the controller works fine in Reason 7x and all other programs, keyboard and all.

This Automap update is taking looong now. Please don't act like M audio. A lot of us here switch from them to Novation because we were hoping that you guys are better on keeping your products up to date, and we still believe in you, but this is taking long now.

I try it on one of my PC Automap doesn't even do anything on this one. So i am wondering if Novation is doing anything in colaboration with Avid or they just trying to drag their feet just like M Adio is doing with hypercontrol. This is getting a little old here and a lot of frustration among us the customer.

Mr Taylor please give us some update on what you guys have done so far.

Im currently shopping around to buy a new 61 keyboard controller for use in my studio that is running Pro Tools 11.1.2 AAX.

I have a very keen interest in the Novation 61SL MKII Controller Keyboard

..., but I dont want to go and buy myself another dead paperweight like the new controller keyboard I already own (and selling) from the other company. Nor do I want to get outdated before I start with Novation - by a new model that might be soon around the corner either.

Taylor , Could you please tell me ;

Q - If this Novation 61SL MKII will stay current for 2014 - as Novations "top of the line" product for Controller Keyboards. Yes or No ?

..., and also ;

Q - Could you please confirm that there are NO "new secret weapons" planned for 2014 (NAMM ?),

............, that will knock the 61 SL MKII of its throne as Novations Premier Controller keyboard offering in both - Better Quality, and / or Advanced technology and features for use with Pro Tools 11 and AAX compatibily

If there is a new model planned for this year (2014) - then I'd like to hang out and wait for it . (Please, Honestly "spill the beans" on this one ? )

But .....,

If the Novation 61 SL MKII is planned to be a continuation of Novations top shelf product for their Keyboard Controller models for 2014,

......., Then I also eagerly await with crossed fingers (hopefully soon)

The connectivity between the Novation 61SL MKII -with AAX plugins and the planned direct integration with Pro Tools 11

I also just bought an Impulse 61 Key to use with my Pro Tools 11.1.2 only to find it is incompatible with the AAX plugins and even the mixer control has been buggy (which is supposed to work). I need to know a firm answer on whether the Impulse is DEFINITELY in the scope to develop AAX compatibility and won't be left by the wayside before my opportunity to return my keyboard elapses. You can directly contact me at jetwolf@live.com

Also, a free version of Bass Station was included with my keyboard, which is also not compatible. Any plans or alternatives to be able to use Bass Station as an AAX plugin??

Also, I was very disappointed to see no tollfree number provided for technical support for US owners.

M-Audio do have an unignorable advantage over all competition when it comes to embedding functionality within Pro Tools in Novation's defence, but this does go to show that this level of connection can be made to the new software.However I cannot see in writing if this new version of Hypercontrol features control over AAX plugins or just over basic Pro Tools functionality. I assume both however.

Mike, this thread exists for the sole purpose of Taylor (on behalf of Novation as a whole) keeping us - your customers - informed on when we will be able to use our hardware with current software. It is not unreasonable that we are starting to query your silence after such a potential major development.

This thread started as an apology for Novation not keeping us up to date. You have not been doing this again lately. Please do not be patronising enough to simply brush our worries elsewhere. Instead be thankful that we are containing them to within your own forum and not voicing our negative views of your customer service in public.

If you can enlighten us further on this issue please do, if not please remind Taylor or anyone else who can help that we are still here awaiting a response.

Mike, this thread exists for the sole purpose of Taylor (on behalf of Novation as a whole) keeping us - your customers - informed on when we will be able to use our hardware with current software. Dave.

Please don't push us to take this to your public sites like facebook and your other social networks and most music forums that we know, just like we did with M AUDIO.

Then after they took the heat, they came with an update quikly. I am just saying this because i like my MKII keyboard a lot but that doesn't mean that me and my freinds can't start to ask for our right to get the update of our software to be updated to support new softwares like pro tools 11.

So again please let Taylor know to keep us updated about this asap, because we are realy running out of patience.

Or we going to have to ask you on your facebook and other places. Again we seeing other companys doing it so why not you NOVATION.

Our development team is looking into AAX compatibility with Pro Tools 11, but there is no current ETA on when that may be added. We listen to all of our users' requests though, and we know that this is a common request, so I will pass yours onto the R&D Team so they know it is still being actively requested.

Best,--Jordan Bennett // Novation Technical Support

By the way where is Taylor!!!!!

Let's get ready for a facebook,tweeter and other social networks complaints.

It has been over two months since any contact from Novation within this thread (any that I am going to consider worth acknowledging anyway!)

I find this beyond disgusting for a company that formally apologised for lack of information and that claimed they would keep us up to date.

Novation, you have failed on this regard and I have had enough of possessing a piece of hardware that is now useless to me. Therefore I have decided to sell my Novation gear - several pieces of Novation equipment in fact.

I no longer care about your support for Automap. I do hope on behalf of all others struggling here that you remedy this issue asap.

But just so you know Novation, I will not be keeping my opinions within your forums. Will I be going out of my way to disgrace your customer support? No, frankly I don't have the time to waste on you. But whenever I see someone asking for opinions/help I certainly will not stay quiet.

I hope everyone else on here continues to get some joy out of their hardware, but I've decided to give up now.

In my last message, I promised I would update you all the moment I had any more information. I have not swayed from that promise, nor do I plan to.

I read this thread every single time there's a post (and even more often than that) and report the information to the relevant parties in the company, who are currently chasing this with all their might. I have not posted simply because I have no new information for you all, and I respect you too much to try to placate you with marketing speak.

If you do choose to 'get ready for a Facebook, Tweeter and other social networks complaints' campaign, you will find yourself speaking to me once again - and I will make the same promise I have made here: the moment I have any more information for you, I will pass it on.

If there's anything I can do in the meanwhile, whilst Novation does everything in their power to support AAX in Automap, please don't hesitate to let me know. I am here to help in any way I can.

Best wishes,Taylor

P.S. I'm very sorry to see you go, Dave. Stay well, and please get in touch if there's anything I can do. :(

I think If you were to just post every so often even to say you haven't made any progress, but are still working on it, would give people the sense that you care. I want to be able to use my Impulse 61 to control AAX 64 plugins, but would take UAD-2 AAX 64 first. I figure if so many companies are struggling with the issue, it must not be an easy one.

Hi all,Just a quick update - I have no new news on this. We are continuing to pursue this with Avid, and I will bring back any further information I recieve.Thank you all for your continued patience in this difficult situation.

I know you can't divulge much but "continuing to pursue this with Avid"? is a bit vague...are Avid playing hard to get?

As a Pro Tools user I'm very much aware of how difficult Avid can be, so is there anything "we" can do to get Avid's attention to further this?

I'm in the market for a keyboard/controller especially for plugins and your automap software is highly recommended and direct support would be fantastic.

I have money burning in my back pocket right now and am pretty much sold on an SL mk2 but would appreciate a "guarantee" (for want of a better word) not so much from yourselves but after owning an Axiom mk1 and seeing M-audio/Avid drop support for that as quick as child caught in the Cookie jar, so am wary of their commitment especially to things non-Avid.