Please see the attached screen shot and crash dump for details. The short version of the story is that the problem is 100% reproducible in the current version of Nuendo. The steps I take to cause it are:
- Create a new Nuendo Project.
- Add an audio track for my guitar signal, mono or stereo makes no difference.
- Add the Amplitude 5 Max plugin as an insert on that track’s mixer channel.
That’s all it takes to cause the crash every single time. I’ve reported the problem to IK Multimedia as well in the hope that I can get this fixed on one end or the other. For sake of reference, I don’t have any issues using this same exact workflow with either Line 6 Helix Native or Native Instruments Guitar Rig. I was just hoping to switch to Amplitude 5 Max for some of my projects. Thanks in advance.
Nuendo 14.0.20 64bit2025.5.3 16.15.37.262.zip (398.1 KB)
So this might be an issue with the install (or something else) on your system. I tried to replicate it and couldn’t. I loaded up a project, dropped in an instance of Kontakt 7 with a guitar synth (Evolution Dracus in this case) and then dropped Amplitube 5 on the channel. It worked properly, no crash, and it distorts the sound properly. I also tried an empty project, inserted an audio track, dropped Amplitube 5 on it, and no crash. I don’t have a guitar to record, but just having it record silence while Amplitube was inserted worked fine, no crash.
This is Windows 11 24H2, Nuendo 14.0.20 and Amplitube 5.10.4.
You might want to look at uninstalling and cleaning out all your IK stuff and reinstalling it, see if maybe something got corrupted, since the problem doesn’t seem to be universal.
1 Like
No issues here in Windows 10 / Nuendo 14.0.20 either - though I rarely use the plug-in versions of guitar sims for live playing, due to having to drop the audio interface buffer setting way down low. (I keep my RME UCX’s buffer at 4096 all the time). Perhaps just try reinstalling Amplitube?
I’ve found that if I run guitar sims standalone on the desktop, with an IK Multimedia Axe I/O One interface, at a super-low 16 sample buffer into Nuendo’s RME UCX interface via loopback for no-latency recording at Nuendo’s inputs, that it lets me leave the DAW’s buffer setting alone.
Amplitube 5’s VST plug-in is great for previously-recorded DI tracks, though!
1 Like
Well, first I’m glad to hear this isn’t a universal issue. But here’s the thing: I literally just purchased Amplitude 5 MAX and freshly installed it using IK Product Manager. There shouldn’t be any “cruft” or old version lying around. Any ideas to what it might be sensitive? The standalone seems to work fine with all my audio interfaces. It clearly doesn’t have a problem with other stuff installed. Maybe I’ll see if I can still launch Cubase (I only just upgraded to Nuendo last year) or try some other host.
UPDATE: Oh wow! Thanks, ya’ll! I don’t know why reinstalling Amplitude 5 MAX fixed my problem, but it did. That’s so weird that a fresh install yesterday doesn’t work for some reason but a reinstall today does. I literally changed nothing else. I even left the bloody computer on overnight so as not to change anything. That really makes me wonder about the IK Product Manager’s ability to do its job. But this is great!
2 Likes
Good to hear a reinstall fixed it. If I were to guess, it might not be something with IK itself, but with one of the requirements it installed, like the Visual C++ libraries. Maybe the reinstall triggered a reinstall of those, and the corrupt library got fixed.
Either way, glad you got it fixed. I do wish things like the product manager had a “verify and repair all the files, including dependencies,” option but few do and you never know when you have it do a repair or reinstall what all it’ll kick off.
I gotta be honest: I’ve been doing software development, music software, you name it for more decades than I care to admit, and this is the first time I’ve ever seen an installer give you zero errors, go to completion just fine, produce a product that works great on its own, but isn’t set up correctly as a plugin?!?! That’s just nuts. But I’m grateful for the help nevertheless: thanks again!
Ya, it should totally not happen. That’s why I was guessing maybe a corrupt dependency. So what I could potentially see happening is the software needs something like VC++ 2019 DLLs. Your system already has them, but they have an issue, unknown to you. It notices they are already installed, so elects not to do a reinstall and just bypasses that step. Then you have issues. However when you do a reinstall it installs everything, including dependencies even if they are already there. That fixes it.
I’m not saying that was what happened, just a theory as to what might cause something like this.
Not a bad theory at all. Thanks for that too.