I had the same issues with elincenser. I wrote support, but got no reply (as usual). Then I bought a new licenser, and now everything works again fine. It’s strange that several users reported issues with their licensers lately. It seems like Steinberg wants us to buy new dongles
However, my usb-key was very old und now Nuendo starts up considerably faster.
Thanks for mentioning.
Good question. I have to check to see how old it is, can’t remember which may mean it’s time to get a new one.
I have mine plugged directly into the front of the 5.1 Mac. Tried to reseat it a few times, didn’t seem to help. But that said had sessions today without issue, first time in week. Will be looking into it further the next few days.
It feels like runninng pirated software, I get embarrased when a director and an actor sit next to me to start an ADR job and I need to click through dozens of copy protection errors.
I have switched to PT for almost all of my audio post tasks with ADR being the only thing left I do in Nuendo and I cannot even start the software without a huge bugfest exploding in error messages across my screen.
Will we at least see a final Nuendo 8 or eLicenser bugfix release that will make the software usable again in a professional environment?
I can confirm that issue persists here as well. Despite changing ports (not in a hub) & running eLicenser maintenance.
Based on others experiences with the “buy a new dongle” advice from Steinberg support, I remain unconvinced that resolves the issue.
And Yes, I can relate with your frustration. We pay a steep premium to stay with Nuendo (here since ver.1) and the clear “lack of zeal to appreciably help” by Steinberg is simply shameful. I too feel embarrassed when I’m trying to open projects and wrestling with numerous error messages.
How does that look to a professional sitting in the room behind me?
Steinberg, do you think inspires confidence in Nuendo when it consistently happens & some Grammy winner (or whatever) dude asks me what SW I run?
How does that look to a professional sitting in the room behind me? And they realize it’s been happening for the last 3 weeks since we started the project.
With the eLicenser version 126.96.36.199 I’ve started to get errors like “Failed to get Info command”. Uninstalling Cubase (10.20) and re-installing it fixed the errors for the first launch of cubase after the clean install. Then on every subsequent launch of Cubase the eLicenser errors return. This leads me to believe that some state is being written after the first launch that creates a conflict with the eLicenser software (this is on Mac OS 10.13.6). I looked thru some backups and found one that used eLicenser version 188.8.131.52. So I copied over that old rev of the application and also restored the contents of /Library/Application Support/eLicenser. Now both Cubase 10.20 (and older version 10.05) are back to normal. They could of made changes between versions 184.108.40.206 and 220.127.116.11 to break things.
Good grief, no comments from SB? …How are y’all doing with this issue?
It’s times like this that makes me feel like a fool for spending / supporting a company over the years (since ver.1) that ostensibly, doesn’t seem to want to be helpful post sale. Almost disdainful that you even have the nerve to ask for help! Even if it turns out to be not as much on their end, still? …a few words of advice past the obvious run eLicenser maintanance etc.
I’m not getting quite as many error messages lately for some reason, but they are certainly still persistent.
As well getting some N8 crashes when closing the program lately. My system was very stable before this all happened.
That is really strange. It is obvious that this occurs only within specific conditions, otherwise no-one would be able to get some work done.
If you have updated the eLicenser, ran maintance on the eLicenser and replaced your old dongle, then we need to start looking for other things.
From what I see , most of you are on Mac. Are there people with problems on PC?
We also need to rule anything else out.
-Try another USB port.
-Use a powered hub.
-Try testing with a new project, add more plugins, close any other applicatoins,anything you can think of …
No-one will be able ot help you if the problem can’t be reproduced.