and we have the lack of fixes in Cubase 11 as a guide
Hi everyone,
I have an update for you and I hope this finds you well. After our discussion concerning EuCon I felt I owe you some more
transparency on the topic and have started talking to our dev team to not only review the N11 release version but also the
following maintenance roadmap.
Iām happy to confirm that the first .10 maintenance update for Nuendo 11 (first maintenance expected for January, 2021)
will not only make the EuCon adapter compatible with Nuendo 11 functions, but will fix issues such as crashes and other
workflow problems that have been reported. At the moment, I cannot say to which extend this will happen (as I mentioned,
we do not own the adapter), but we will definitely provide bug fixes with this update.
Thanks,
Timo
Again, thank you Timo for letting us know in advance. This kind of information is rarely shared by a developer prior to release.
This leads me to repost part of an earlier post of mine in this thread.
I certainly remember expecting various users to complain about a new update when it was released. But we have now āprogressedā to the point that complaining begins before a single user has booted the official release on their system. > Unless someone is now running the final release of Nuendo 11. Anyone doing that?
How much space has been used for complaining about something that, as it turns out, has already been addressed before N11 releases in this thread originally started by Timo to inform this user base about upcoming good news? Perhaps assuming the worst is a counterproductive time waster sometimes?
Thanks Timo - hopefully this will shut me up 
Well, we have been running N11 for the last couple of months on all of our commercial projects.
So do most of the beta testers.
The only thing I can tell you is that Beta testers nag (in an extreme polite way) as much about unresolved issues as users on this forum.
But as Timo has explained, most of the āeasy to fixā issues, long standing problems and āsmall changesā are not as easy, and as fast, to fix as you might think. So things get prioritized.
I did make a few attempts to change the order of the priority list in the past, with the help of plenty of Alcohol.
Unfortunately our Product Manager is a teetolar.
Timo however ā¦ (Fredo running and taking cover ā¦)
Fredo
Yes, my friend, I know how that works. And thanks to you and the rest of the beta testers. I paid my dues with many years of beta testing and frankly, donāt miss it.
But I did use the words āofficial releaseā which canāt happen until the Official Release. So even you are not running the official release, only an official release candidate.
So a time machine would, in fact, be needed to do so at this time
Hi all,
am 100% in line with Joris and Crispin.
Thanks to Timo for his very fair view points. Juggling many such customer facets and mixed requirements isnāt just easy.
And having Nuendo, as it may seem (initally) with many features of no use for one or the other, can be seen as āno limitations for creativityā. It is like āā¦ hmmm, whats this ā¦ letās give it a try ā¦ā
Personally, I am flashed about N11 and āproduce Dolby Atmos* content entirely within Nuendoā. Hope, that the ā*ā [Dolby Certification pending] isnāt a big thing to overcome.
LG, Juergi
Excited to hear about tight Atmos integration. Does this mean that Nuendo will follow Dolby guidelines for surround buss naming schemes? ie. As of N10, Nuendo and Dolby are at odds at what are considered āsurroundsā, making it very easy to mix up buss assignments when composing and mixing within Nuendo.
i.e.;
Nuendo: āSidesā are the side speakers, while āSurroundsā are the rear speakers.
Dolby: āSurroundsā are the side speakers, while āRear Surroundsā are the rear speakers.
And unfortunately, you cannot rename the busses to accommodate a Dolby workflow.
What? Next time we meet, Iāll bring a Whisky 
Hi Juergi,
donāt worry, it will be finalized until release.
Thanks,
Timo
Iāve been running Cubase 11 for two days now and itās pretty good. The only bugs Iāve encountered are meters in midi tracks not working correctly. As far as bugs go, thatās definitely on the āI can deal with it for nowā list. When Cubase 10.5 came out it was a disaster for me. I had to stay in C10.0.30. When Nuendo 10.3 was released it had most of the same ābugsā that stopped me from working in C10.5, causing me to keep working in N10.2.20. I had to keep experimenting and change a few settings to finally make it work. Iāve been using N10.3 successfully for the past four months. If N11 is similar to C11, then the update should be smooth and pleasant. Just my experience of course, no disrespect to yours.
This is great news Timo. Thanks much for the update! Is it safe to assume this update to the Eucon Appset will also port over to Cubase 11 at the same time? I would be so grateful to more fully implement my Eucon controllers with Cubase. Thanks again and please keep us posted on this!! Jon
Hi Timo,
Thanks a lot for this promising information.
Hopefully this leads to a proper working Eucon implementation after years! A dream would come true
Really looking forward to this maintenance update!
All the best
Thanks for the deep and transparent response, Timo. As usual, youāre a huge asset to Steinberg and all of us.
Just a slight correction here as you might be surprised: In game audio many of us care very much about Field Recorder import - we live and die by great source and custom recordings are essential to this. I have a team of guys constantly editing and categorizing everything we record. In games we also do a lot of what is considered Post - my team and I handle cinematics on most of the games we do and the workflow is very similar. At the same time, we also use midi-sequencing (myself as a composer in particular) to do things like setup foley banks and gunfire banks of ingame sounds to quickly lay in to our cines.
In todayās environment, it pays to be able to handle a diversity of workflows and projects so everything you guys do is important to us and all of it is hugely appreciated!
Best,
Crispin
ps: very much looking forward to COVID being done so we can finally travel and hopefully share some whisky!
This is the best news Iāve had all week!! Thanks Timo!
Timo gets 5% on all N11 upgrades.
You know what? Screw EUCON! 
EUCON hasnāt been EUCON since Avid got a hold of it! The entire appeal of EUCON, when Euphonix owned it, was that it was designed to work with every DAW. THAT was the big selling feature in every tutorial I saw when it was released.
Now that itās āfallen into darkness,ā itās acting just like anybody paying any attention wouldāve predicted! All SB has to do is MAKE THEIR OWN VERSION OF AN ARTIST SERIES/S1 - 3 LINE OF CONTROLLERS and the issue is solved once and for all!
Cubase/Nuendo users are FIERCELY LOYAL!! Iāve been using Nuendo since Ver. 1.0 and, with the exception of Fairlight, I never once considered moving to any other DAW, let alone Pro Tools! So if SB released a Mid priced, fully integrated line of controllers for their DAWs, āWE WOULD ABSOLUTELY COME HOME!ā All those Artist Series controllers would be on eBay in a second and moved onto where they now belong, in the Avid Ecosystem and we would be in Nirvana using our āNuage Lightā controllers.
From all of the complaining about THIS ONE ISSUE for almost a decade now, it should be clear that there really IS A MARKET for budget priced Yamaha/Steinberg Hardware. A ā.10 Fixā promise just feels like another carrot on the same stick!
Iām sure Iāll get N11 and IF the EUCON fix actually happens, Iāll be pleased. But frankly, Iād rather be done with EUCON altogether. Itās no longer for us and it never will be!
Hi Crispin,
youāre certainly right, Nuendoās strength is to cover multiple workflows in different parts of the industry and the lines
are getting blurred more often in recent years. My intention was to rather point out POSSIBLE differences in the expectations
of Nuendo users. I fully agree that this is different in a variety of cases, and certainly, bug fixes contribute to the general
stability of the application. And a key element in development is to find out, which fixes are a win for the majority of users
in the different industry areas.
ps: very much looking forward to COVID being done so we can finally travel and hopefully share some whisky!
Definitely! Iām familiar with Canadian Whisky, but Iām very much into Single Malt I have to admit.
All the best,
Timo
How cool is that. I didnāt know! Maybe the company has a wrong bank account. Nothing received for any of the previous updates 
there must be āTimo Wildenhainā imposter out there then 