Hi Guys,
Nuendo 12 had a wrong channel layout for 9.1.4 and 9.1.6 which seems to have been fixed in Nuendo 13 (seems to, not sure though). Now Juce built plugins do not load anymore in Nuendo 13 on track with these formats correctly. I mean they load, but you cannot get them to be recognized as such having all inputs and outputs connected.
A fix for this is urgent.
Best,
Thomas
We’re experiencing the same issue.
Same here
There are now two 9.1.6 formats offered by Nuendo 13, 9.1.6 and 9.1.6 ITU.
I think 9.1.6 ITU is the Nuendo 12 era format (where we have the additional wide channels directly left and right of the centre) and VST3s seem to be working with that as before in Nuendo 13 (but I can imagine why clients may want to begin to migrate to the newer layout offered). I think that’s known as k91_6 in vstspeaker.h in the VST3 SDK and is what we get with AudioChannelSet::create9point1point6.
The new 9.1.6 format will be the one causing problems if clients select it. This places the wides in the more familiar place between the front and sides but that’s new to Nuendo and the VST3 SDK (I don’t know when it popped up, but it’s in the newest SDK). Juce 7 and 8 do not yet seem to have support for the new k91_6_W in vstspeaker.h. So now AudioChannelSet::create9point1point6 needs to somehow disambiguate between two 9.1.6 formats - I’ll leave it to greater minds than mine to figure out how that’s going to be handled.
You may find that VST2 plugins that do not understand the difference between these format widths are working as before, this was the case in my investigation for a client.
We are experiencing this issue as well. It seems that the new “Wide” layouts (compatible with Dolby Atmos) were added in VST3 v3.7.9, and are used by Nuendo 13.
More info here.
Seems like a very good reason to update JUCE from VST3 SDK 3.7.8 (from a year ago) to 3.7.11. Why is JUCE not to up-to-date with such important SDKs?
Please add at least support for Steinberg’s k91_6_W
Nope, for all 4 new layouts please, not only one.
So +1 for a quick update of Juce to the latest VST3 SDK, please!
In another topic I just noted a comment from Reuben:
“At this point we’re only fixing critical bugs on the JUCE 7 branch.”
I really hope this 9.1.6 issue will be considered a critical bug (i.e. incompatibility with a major DAW due to not staying up-to-date with the VST3 SDK), that should IMHO get priority over ongoing WebView, DirectD and other GUI developments.
We ran into this issue during tests of a new surround plugin. A show stopper for us for now.
For us as well, especially because we develop Dolby Atmos software.
We’d really like to see this fixed in JUCE 7 as well - as it stands, all 9.x.x plugins built with JUCE are seemingly incompatible with Nuendo 13. Support for the k90_4_W, k91_4_W, k90_6_W, and k91_6_W speaker arrangements needs to be added.
Can we expect a hot fix?
Since these features landed in the VST 3.7.9 SDK from October 2023 I think it’s reasonable to ask for them in one of the final Juce 7 updates. That was well before we were seeing public work being focused on Juce 8.
We’ll look at this. We’re just waiting for a Nuendo NFR license refresh.
So this issue - which is a blocking issue for at least a few of us - is now parked until someone at Steinberg takes action?
This is not a JUCE-Nuendo issue.
This is about JUCE lagging behind, as “The most widely used framework for audio application and plug-in development” (from your site).
The problem can be easily understood when you compare the VstSpeaker.h from the recent VST3 SDKs and the older one that is included with Juce, which was explained above.
I kindly ask for a more pro-active reaction, like “we are going to integrate the most recent VST3 SDK on the shortest term possible”. This can be started before having access to Nuendo.
Also very keen to see juce7 inherit a fix for this. V8 is way too fresh for us to release a bug fix using it.
Thanks @t0m for taking a look. Hopefully it’s not too much of a hassle.
Bump
Maybe someone at Steinberg can help the Juce team with an NFR license for Nuendo 13?
So disappointing how this bug report is handled
It’s live
Thank you very much for mentioning this!
And thank you @reuk for fixing this issue!
As mentioned already, support for the new Atmos layouts is added in this commit:
We’ll add this to the JUCE 8 branch shortly.
