EUCON Update!

Hi @TimoWildenhain,
just installed the Nuendo 11.0.10 update to check all the promised Eucon improvements / bug fixes.
I really was looking forward to this update and had a lot of hope to finally see these Eucon issues (which already exist(ed) for years!) are gone now.

But yeah, what should I say… Nothing has changed.
Eucon exactly behaves like it did in all the previous versions! All the issues I mentioned in this thread still exist in the exact same way.

I’m really disappointed!
So my question is: what did you / Steinberg dev. team change due to Eucon (as it is mentioned in the Nuendo 11.0.10 release notes, https://new.steinberg.net/nuendo/release-notes/?_ga=2.42641894.2101397428.1611754133-201245320.1611571731)?

I’m (and probably lots of other users) really looking forward to an explanation!

Thanks in advance

1 Like

NOOOOOOOOOOOOOO!!! Are you kidding me? There is nothing on this list that addresses ANY of our issues! :rage:

The compatibility with EuCon-based Avid control surfaces has been improved.

What does this even mean?!!?

Hugely disappointing that no real changes happened with the Eucon implementation…

So now, it doesn’t crash when you hit the tracks section. Now it waits to crash when you close the program! Big Whoop!

SERIOUSLY?!!?

I thought we’d at least get the hide/show issue resolved. :rage: :cry:

where are you getting the crash ? For me it’s in the AVID plug not the Steinberg one ?

When I launched Nuendo and went straight to the tracks page, expecting a crash, since I had amost 90 tracks, I was relieved that it didn’t.

I ran it through several functions, scrolling, making layouts, etc. No crash.

Then tried hide/show and was brutally disappointed.

So, I closed Nuendo. THEN it crashed. No notice from the Avid side, just Nuendo.

I think we all feel that disappointment !

I get the crash on exit too - IIRC you’re on windows - so have a look in your Windows logs - the Application one - you’ll probably see some ‘red’ errors - that might tell you more.

1 Like

For the 1st time EVER, I am actually considering switching to Pro Tools! :scream: :disappointed_relieved: :cry: :sob:

Been saying that for years, Steinberg are amongst very few DAW companies that do not have a dedicated consumer level dedicated multichannel/fader controller for their DAWS which is actually remarkable when considering the mothership Yamaha have been world beaters and inovaters for years the range of digital desks.

The problem with Nuage is it too big and too costly for all but a very few and, lets be fair is 12 years old or more. If it was an avid device there’d probably be a few on eBay now as it would have been replaced with bigger/better or even smaller surfaces with a range to suit all users and pockets.

They’ve been pushing the CC121 again after Presonus out manouverd them with their suprise 1, 8 and 16 fader/channel remotes with many cubase forum users buying them. Why on earth Steinberg/Yamaha just haven’t built a 16 channel pro version with a few extra’s thrown in beggars belief, its not as if either party dont have the basic building blocks, (Euston/DM200 0196i etc). Maybe they think they’ve missed the boat but, with the uptake of DAW’s becoming a fixture of just about every home/bedroom studio in the western world and now appearing more and more in small/medium and even large studios, and edcucational facilities just points to Yamaha extremely short sighted views in those areas

There seems to be a lot of hot air, talk and promises on updated Eucon specs flying around on both Nuendo and Cubase forums atm but that’s nothing new, claims of a fully working mix console view, show/hide channels were released over five years ago on the forum but then side stepped for many years si i doubt id many people take them seriously any more, although companies like Qcontrol and Nektar have had that feature implented from day one it would seem, albeit on earlier control formats, but MIDI 2 is beginning to break, it won’t be too long before that protocol will outshine predecessors and MIDI will once more be the king of jungle. so, come on Steinberg. what are you (and we) all waiting for?

Either get your differences with Avid out of the way and embrace Eucon or just build your own dedicated controller!

Using Avid Artist (x2) and Avid Control.
Eucon 20.6.0.11

My only gripe?
When doing automation with a fader, Nuendo selects the automation lane, and on the control surface, it DESELECTS the track. So, in the gloom of the studio, I don’t know which fader to grab, should I accidentally take my finger off for a moment, as I often do to stop writing automation while playing back.

This needs to be better implemented… track selection should stay with the track itself, not get deselected.
Or
Give us the automation lanes on the control surface.

Other than this, I have been mixing an entire live album for the past two days, 12 hours per day, and zero crashes. OH I JINXED IT. :slight_smile:

1 Like

Hi Timo, I wish you a happy and successful new year at steinberg!

Could you please chime in and tell us (eucon users) what‘s new in the latest update regarding eucon and the known issues?

The eucon adapter in the studio setup is still dated nov 2020.

Thank you!

3 Likes

Dear @TimoWildenhain, dear @Matthias_Quellmann,

I would ask you to comment on the current Eucon update in Nuendo / Cubase 11.0.10. For me and many other users it is incomprehensible that a corresponding update has been announced but no noticeable improvements have been implemented.

I will not give up on this topic either! In my opinion, it cannot be the case that significant bugs, which extremely restrict usability, have simply not been fixed for years. Eucon controllers therefore do not work as advertised by Avid and Steinberg! In my opinion, this is a deception of consumers, because no solution has been worked on here FOR YEARS!

Can you please also tell us whether the long-standing bugs mentioned will finally be fixed in another (the next) maintenance update?
Thanks in advance

Please also check this thread for Eucon related bugs noted by many users

Dear all,

Thank you for the discussion. I’d like to shed some more light on what has been
done in the 11.0.10 Update regarding EuCon improvements.

We’ve been doing a couple of improvements that will improve the reliability of Nuendo integration.
Many of them are on code-level (code clean-up), but of course we have also fixed bugs that have been reported by users, such as:
[SOLVED] [EUCON] iPad app “The number of allowable hardware channels has been exceeded”
[SOLVED] [EUCON] Crash when selecting track wile EuCon app is in track view
[SOLVED] [EUCON] Crash when adding more than 37 tracks using Pro Tools Control iPad App
[SOLVED] [EUCON] Crash when adding 40+ Tracks with EuCon
[SOLVED] [EUCON] Crash when removing track while modifying parameter
[SOLVED] [EUCON] Crash related to MIDI Plug-Ins
[SOLVED] [EUCON] Crash when removing a midi send effect
[SOLVED] [EUCON] Avid Dock not working with EuCon
…plus a couple more related to memory handling and overall stability.

Thank you for reporting more issues in this thread. We’ve taken action in order to
fix the following issue with the next .20 maintenance update:
“Hidden tracks in the Nuendo mixer are still available in the Avid control app / Avid controller”

We’ll be investigating even more EuCon issues that have been reported in this thread
for upcoming maintenance updates.

Thanks,
Timo

2 Likes

Thanks a lot @TimoWildenhain for the detailed bug-fix list!

imho the “Hidden tracks in the Nuendo mixer are still available in the Avid control app / Avid controller” issue is by far the most important one! This one is asked for years and it would be simply awesome if this finally gets solved!

Beside that, the “Nuendo doesn’t follow scrolling in the Avid control app / nudging or banking on the Avid controller” bug is also really important, because if theses two were solved, it would be easy to navigate thru a big session “only” using the controller! As it should be!

Really looking forward to the next maintenance update, to see this progress on the Eucon implementation. Do you already know when we can estimate the .20 maintenance update?

Thanks

p.s: for a professional workflow with the controller, the following bug is also fundamental!

2 Likes

Thank you for your feedback! The next update is expected for the end of Q1 2021 and the
“Hidden tracks in the Nuendo mixer are still available in the Avid control app / Avid controller”
issue is already worked on.

We’ll be looking into the other issues as well but I cannot promise if they can be addressed with
the next maintenance.

Best,
Timo

So let’s get this right @TimoWildenhain
Are you saying that next update to be released at the end of quarter 1, 2021 WILL include the the Cubendo
mix console track filter show/hide track feature fully working and it will actually reflect that view on the avid control surface…?

This sounds remarkably similar to a few other posts from Steinberg staff I we the last few years…

Thanks much for the communication Timo -

The two that chednb reported are also the biggest fixes needed in my opinion as well:

“Hidden tracks in the Nuendo/Cubase mixer are still visible in the Avid control app /Avid controller”

“Nuendo/Cubase doesn’t follow scrolling in the Avid control app / nudging or banking on the Avid controller”**

Thanks again for keeping us updated

1 Like

I’m really looking forward for the implementation of this feature, because it will really speed up my workflow and avoide mistakes and confusion while tracking and mixing. I also hope that even if it is a competitive product, steinberg will continue to work on this. It is sad, that yamaha did not come up with a affordable alternative to this point when it comes to control surfaces. I really hope for this in the future.

I’m not sure I understand your comment about the Hide/Show issue. You said it’s “ALREADY WORKED ON.” Does that mean it’s already fixed? If so, considering it was the number one repair request for close to a decade, why didn’t you release it with the 1st patch?

If not, then do you mean you guys just got it working AFTER the 1st patch release and you’re just holding it back for the second patch along with whatever other issues you can correct in this time period? :thinking: