My First Mid-Show Crash

Gadzooks, I had my first mid-song crash at a gig yesterday…

Everything was going great, we were half way through the last song of the first set with no glitches or pops, then all of a sudden C3 shuts down and throws up an errror dialogue box :open_mouth: I loose bass and keys but at least the outboard looper is still playing the drum loop; the guitarist and singer look over at me but keep going. I don’t have time to read the error and quickly restart C3, which by default loads the first song in our set and in doing so sends a MIDI program change signal to the looper telling it to switch to that first song :roll_eyes: so now we loose drums and are left with acoustic guitar and vocals. I’ve now broken into a cold sweat :scream: and scrambling to load the last song we were on before the crash, I manage to do so and re-start the drum loop just in time for the last chorus :rofl: Thankfully we managed to finish the rest of the 3 hour show without further incident.

It wouldn’t have been so bad if I was just playing keys, but when you’re the trio’s drummer, bass and keyboard player things get a bit more intense. It’s times like these I wish we were on a Mac platform.

Coincidentally, I’m halfway through seting up a brand new Intel NUC that will purely run C3 which I’m hoping will be more reliable than the MS Surface Pro 4 I’m currently using :ok_hand: otherwise I’ll be going back to hardware keys :-1:

Thank you for reading my tale of woe…

So, I suppose you sent @brad your crash files so you can find a cause of the crash? What exactly makes you believe Mac wouldn’t have crashed? What proof do you have that it wasn’t a faulty plug, or a bad routing? I sincerely feel bad for you, cause I know how it feels. But, do you really want to move ahead without knowing what caused the crash?

I’ve had 2 live gig crashes, and 3 rehearsal crashes in the past 6 years since I’ve been heavily gigging with Cantabile. I had one of the rehearsal crashes 2 weeks ago. Turned out to be a problem with a plugin, and I immediately DITCHED it…now no problems. My two live gig crashes were from faulty wiring, and another faulty plugin. In that 6 year period, I probably performed around 900+ gigs with 5 different bands, and with the same computer. I would never go back to hardware again. They contain computers, they are costly, they are heavy, they are limited, they also crash, and they usually have a dozen good presets and 1200 lousy ones. My rig sounds better than any expensive Nord I’ve ever played.

Do yourself a favor and send Brad a crash report. He can usually discover what happened, instead of letting it happen again.




Hi @Pete_67,

So sorry to hear that.

I’m keen to look at a crash log if you happen to have it. If Cantabile prompted to send a crash report but you couldn’t send it at the time it should be still in your settings folder:

  1. Start Cantabile
  2. From the Tools menu, choose Open Settings Folder
  3. Look for a .zip file time stamped at the time of the crash.

If it’s there, email it to me and I’ll check it out.



Thanks guys I definitely want to know what caused it, so I’ll have a look for that zip file and send it to Brad. I’m sure it’s something in my Surface, I doubt it’s the 4 plug-ins I use as they’re pretty low overhead non-sampling type.

This morning I finished setting up my new NUC… this thing is smaller than my Steinberg interface, amazing!! I did a bunch of latency tests on it with multiple instances of plug-ins through C3 and it hardly broke a sweat :sweat_smile: I just need to get a 12” touch screen I can use with it to ditch the keyboard and mouse.


Hi all,
I had a few crashes in the past few weeks. I’ll look for the log file. @brad is the offer to look at the log file (assuming that there is one) still valid?
Any suggestion for debugging? Cantabile has been extremely stable for me until recently.

Just got home and looked at the zip files. I think the last lines indicate that something went bad, but I am not sure I understand what it was. here they are:
07403270 110718 ! [09364:0]: Exception context: Unhandled exception filter
07403270 0 ! [09364:0]: Native exception: code:0xc0000005 address:0x00007FFCCFA9384E flags:0x00000000 params:0x0000000000000001,0x000000038124F708 rax:000000032EBFF542 rbx:0000000000000004 rcx:000000032EBFF540 rdx:000000038124F6F0 rdi:000000032EBFF5D8 rsi:00007FFC049EBCC8 r8:000000032EBFF540 r9:00000000006D06D0 r10:000000032EBFF540 r11:000000032EBFF540 r12:0000000000000000 r13:00007FFCCFB944F8 r14:00000000006D03A0 r15:0000000000000000 cs:0033 ds:002b es:002b fs:0053 gs:002b ss:002b eflags:00010246 stack dump: 00007FFCCFA93625 0000000000000000 0000000000000000 00001F800010001B 0000000000000033 00007FFC049EBCC8 0000000000002494 000000038124F6F0 0000000000000000 0000000000000000 0000000000000001 0000000000000000 FFFFFFFFFFFFFFFF 0000000000000000 00007FFCCFA9346D 00007FFC049EBCC0 0000000000001722 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 00000000FFFFFFF6 000000038867C000 0000000000000000 0000000000000000 00007FFCCFA82630 000000000000027F 0000000000000000 00000

1 Like

Hey Marco,

Yes it’s still valid. Sending your crash log to Brad is the best way to figure out the problem.