Hello
I noticed that the new version of Wavelab is supported as ARA 2 in Nuendo 13, why can’t I find it in Nuendo 12? This is still ARA 2, which also works in version 12. Does anyone have a similar problem? Does anyone know how to fix this? Thank you
Because Nuendo has a hard-coded list of ARA compatible plugins, and of course, WaveLab ARA did not exist at that time.
Got you and thanks for the answer. What do you think - will Wavelab be added to version 12, or will only version 13 be a solution to this problem.
Ask on the Nuendo forum, because I have no idea.
Thanks
So, has anyone heard whether or not Nuendo 12 will be updated to support all ARA2 related plugins? Or at least, their own products. I understand about what was said about the hard-coding in Nuendo 12 of ARA 2 plugins, so that begs the question: Is this the way that this is also handled in Cubase Pro 13 and Nuendo 13? It would seem to me that, if something comes out today, let’s say, would you also not be able to use it in versions 12 or versions 13 of the two software tools? It would seem to me that a hotfix is necessary and the code should be able to identify an ARA 2 plugin and simply support it. Why hard code? That’s a quick fix, but it’s limiting and Cubase Pro or Nuendo are big investments from a financial standpoint I certainly hope that Steinberg decides to do something about this and soon and quickly. Many of us, still using version 12 of their DAW products, ran out to purchase Wevlab 12 Pro, expecting ARA2 to work, and of course, it does not.
This question is more to ask on the Cubase or Nuendo forums.
Yeah, that makes sense, instead of on the Wavelab form.
Steinberg doesn’t seem to be looking after N12 any more, which is a commercial disgrace from my point of view*, especially as N13 isn’t ready for solid use and is taking a lot of flak for its interface. I’m among those who are blocked. I don’t want N13, but I do want Wavelab 12 in ARA.
- Just take the bug with the left window (track list or visibility) that can’t expand. Fixed in N13, of course, but it’s a bug. The initial purchase of N12 should guarantee corrections of this kind.
The whole way that ARA2 is handled is totally unprofessional from a coding point of view. There should not be a “List” of ARA2 applications tacked onto Nuendo/Cubase 12. Software is much more sophisticated than that these days. There are ways to detect whether or not an application is ARA2 compatible or not, and if it’s compatible, it should show up. Simple as that. I’m a software developer by trade so I know better. The half baked way that this is handled in version 12 of the software is amazingly bad. This has nothing to do with whether or not Wavelab 12 was out or not. If it’s an ARA2 application, it should work with ARA2 aware applications that means that both Wavelab 12 and Revoice Pro 5 should work in Nuendo 12, without any code changes, had it been done right in the first place. I have not heard of any other DAW related software that supports ARA2 having this issue. I am going to try this out in two other DAWs that I have to see what I get. From the research I’ve done, I have found the following but have not tried it yet.
- Studio One 4 on up supports ARA2
- MAGIX Samplitude X5 supports ARA2
I have both of the above DAWS so I will see if they will work with the following:
- Wavelab 12 Pro - ARA2
- Revoice Pro 5 - ARA2
Should be interesting.
1 Like
? I don’t follow this at all, it is already included from start
I mean you can do all editing and more…
Why do you need this?
and by the the way REAPER also support ARA2…
regards S-EH
I brought it up because if ARA2 is supported, then doesn’t that mean that all ARA2 software should be supported by an application claiming support? It doesn’t make any difference if a brand new ARA2 piece of software comes out today or next month. Any product claiming to support the protocol should mean that it will work in the software claiming to support it. If not, then this means that the software claiming to support the protocol is bypassing the requirements for that support. Example: There are old versions of DAWs that support brand new VST3 plugins that were out well before those brand new VST3 plugins came to market. ARA2 should work the same way and if a product that claims to support ARA2 doesn’t “See” the new ARA2 products, then that product is not following the protocols required to support that particular technology. In this case, I’m talking about Nuendo 12. Either you support ARA2 or you do not. If you do, then you have followed the protocol and any and/or all newly released ARA2 software should show up in your application. If not, then you (the software creator) should make the proper adjustments to ensure that this is the case. This is especially true when it comes to Steinberg, who created VST technology which most support and follows the guidelines and protocols necessary to render that support. Steinberg, among all companies should understand that better than anyone. When I open Nuendo 12, and I’m going for ARA2, then I should see Wavelab 12 and Revoice Pro 5 for example. Two ARA2 enabled applications. If I don’t see them, which using Nuendo 12, I do not, then this means that the software doesn’t support ARA2 applications. Support means ALL ARA2 applications or should, just like it is with VST3. If you’re going to pick and choose, then be honest with the consumer and say, we support the following ARA2 enabled applications and give them a list. And be clear that anything not on that list is not supported.
1 Like