I just took a look at the last file you uploaded and it’s a crash in MODO BASS 2.
However, the exception didn’t get fully reported - it’s still in the exception handler.
Wondering… how long did you leave it in hung state before manually capturing the memory dump with Task Manager. Given the size of the crash dump, procdump could take 60+ seconds to finish capturing the crash.
Here’s what I think might have happened:
MODO threw an exception
ProcDump was invoked and started capturing crash report, which took a long time and made it look like Cantabile was hung.
Before ProcDump finished, you manually captured a memory dump with task manager
ProcDump either finished in the background (please check if there’s a crash report there now) or ProcDump was aborted due to the manual memory dump you invoked.
Either way, it looks like MODO BASS was the original culprit here.
Next time this happens, before using Task Manager to capture a memory dump - take a look at procdump in task manager and see if it’s doing anything (ie: CPU usage is up), if so wait for it.
You could reconfigure procdump to capture minidumps (-mm command line option) instead of full memory dumps - these are much faster/smaller (probably 200Mb instead of 25GB) but obviously don’t have as much information.
Basically, the memory dump you did capture, captured that an exception happened and was being reported… but didn’t capture the actual exception (aside from the fact that it happened in MODO).
So this is weird and may be a root cause of my issues. I followed Brad’s instructions to force Cantabile to crash. However, I don’t get the “kaboom”; it just hangs, indefinitely. When I attempt to end the Cantabile task in Windows Task Manager, it does nothing (and with no crash dump file in the C:\Dumps folder). This is the same exact behavior I see when Cantabile stops responding and hangs while I’m playing. What’s even weirder is that there are two Cantabile tasks visible in task manager when the forced crash occurs, one is running and one is suspended.
@brad I uploaded the log.txt file and memory dump file from the Cantabile process for your review and insight. Only the running task created a memory dump; the suspended task’s dump file was null. Thank you again for all your assistance!
I haven’t had a chance to look at the logs/dumps yet however…
If there’s a second instance of Cantabile, that suggests you haven’t disabled Cantabile’s own crash reporting. When enabled and Cantabile crashes, it relaunches a copy of itself in “crash reporting mode” which captures the crash report and uploads.
But if the crash reporter is disabled, it shouldn’t be doing that.
If it is and you’re sure the crash reporter is disabled, then there might be a bug there that I need to address.
Could I get you to also test something else. Try the secret kill switch again but with nothing loaded (empty set list, new empty song) and see what happens.
So I’ve been working with Brad on trying to narrow down the root cause of the crashes. As always, Brad has been phenomenal, going above and beyond. We are so lucky to have an app owner/developer that is so responsive and attentive to the user community!
Based on Brad’s findings, it appears that multiple IK Multimedia plugins behave badly. That’s disappointing because I generally like IKM’s software, their instruments and sounds, and I have a substantial financial investment in their plugins. It’s also not surprising because many of the IKM plugins are old, badly written, poorly supported, and infrequently updated.
I have therefore decided to abandon IKM plugins altogether and replace them within all my racks, songs and set lists as follows:
Replace MODO Bass 2 with Spectrasonic Trilian.
Replace Amplitube 5 with NI Guitar Rig 7.
Replace SampleTank 4 with Air Music’s Xpand2, Structure 2, and Hype samplers/ROMplers.
Replace SampleTron 2 with Air Music’s Mellotron.
Replace Miroslav Philharmonik with Musio and Kontakt symphonic string and horn libraries.
Replace B-3X organ with UAD Waterfall B3.
I own all of the replacement plugins, with the exception of Trilian which arrives on Wednesday. This will take me a bit of time and work, however I absolutely need “five 9s” uptime for live performance and moving off Cantabile is not an option for me.
I’m wondering if anyone else has had similar (or even different) experience with IKM plugins and Cantabile?
I do not use IKM, but I’ve had similar problems while running multiple instances of some plugins. The problems were isolated to “not ready for primetime” OEMs.
I gave up on IK plugins several years ago, too unstable. Don’t know how much guitar work you do but FWIW on amp modeling you might want to look at TH-U and Neural DSP… they seem to be more popular and are updated often (I use both, along with S Gear, all very stable and quite good). I tried a few versions of Guitar Rig, I think the last one was 5, it just didn’t do it for me; although I have heard that 7 is better. And of course there’s Tonex and NAM captures, if you don’t do much tweaking of tones.
Some here have run into issues with Kontakt, it seems to be a frequent offender. OTOH I still run 1 instance of Kontakt 6 player and it’s been fine for a few years. There are so many older and newer good instruments using Kontakt format it’s often hard to get away from. Maybe reduce the outputs to just one stereo pair, there’s a way to force extra outputs to be disabled in C4 but I can’t remember exactly how.
Of course YMMV, do what works for you.
Tom
Thanks, Tom. I’m not a guitar player. I just use an amp sim with Orange Tree Samples electric guitar vsts for rhythm comping, so I’m not as picky about the quality of the simulation. I already own GR7 as part of Komplete.
Since I am in way too deep with Kontakt instruments, that’s a good tip to reduce the number of outputs. I have several linked racks with Kontakt 8, so I’ll have to address each one individually, I believe.
I’m not a fan of SampleTank, but B-3X and Tonex have been working without any issues in my (pretty complex) Cantabile setup.
And Trillian does have its own issues, with Spectrasonics plugins architecture driving quite a bit of system resource load. MODO bass has been working nicely in my production setup for years now.
Torsten, are you using the original MODO Bass or MODO Bass 2? I am using the latter and Brad has noted that it has been the cause of more than a couple crashes recently.
Also, which Windows version do you run? I’m on 11 25H2.
After a few hours working with Trilian, I have to say it is an absolute game changer for anyone that plays left-hand (keyboard) bass. IMHO it sounds so much better than MODO Bass 2 and also allows supports using CC64 sustain pedal for legato playing (which MODO 2 does not). As Torsten pointed out, Trilian is CPU “heavier” than MODO, but since I removed Sampletank and B-3X from my set list, I’m not seeing any additional load.
I wanted to provide an update. After removing and replacing all IKM plugins, I have been stable through three live shows and countless hours of rehearsal and studio playing.
Previously, I was experiencing intermittent mid-song crashes and general instability. The only crash I’ve had over the past three weeks was switching between songs, and after doing some extensive editing of songs and racks. I consider that a one-off outlier, but will continue to monitor.
The IKM plugins that I removed include Sampletank 4, Sampletron 2, Syntronik 2, Mkroslav Philharmonik, Amplitube 5, MODO Bass 2, and Pianoverse. I don’t know which specific plugin(s) were problematic, or whether it was interaction between IKM plugins or with other non-IKM plugins.
I may look at reintroducing Pianoverse, as I much prefer its Steinway and Yamaha grand pianos to those of Pianoteq 9.
So I ended up removing Pianoverse (again) because it was causing Windows “invalid access to memory location” errors, which crashes Cantabile. All of my Pianos are now either in Kontakt, Falcon, or Pianoteq. It’s a shame that IKM instrument plugins are so poorly written, because they sound great IMO.
