Using Clip Matrix in the MPC LIVE III to play live

I'm curious to know how Live III owners have fared so far while performing with the Live III?
I'm a longtime Ableton user and the Clip Matrix is one of the key features that sold me into buying this machine however I have been practicing using Clip Matrix to play live and my machine has crashed while using it in this way.
I'm currently preparing for a show in a few weeks and considering sacking it off if I have any more crashes?

If any other live III users have suggestions for optimising this machine for live performance please let me know!

I'm already doing the following:
-No Limiters/maximisers in my live project (compressor/EQ on the 1/2 masterout)
-Keeping Fx to four sends
-Restricting Drum tracks to 2
-Three midi channels controlling hardware synths (no internal MPC synths being used)[/list]

I'm also running audio from two of the hardware mono synths into the MPC's audio inputs and mixing these internally

Any other tips for keeping CPU spikes in check?

What kind of errors do you get?
I jumped from 2.15 directly to 3.6 and then 3.7 (on a live 2)and occasionally gett audio dropouts when changing screens/modes (for instance when jumping from main to clip matrix, but also even simple ones: when just going from main to grid edit or mute page for instance).
Also code -71 errors started popping up, as well as ' the internal audio device could not be found' and random messages about the SD and SSD being ejected improperly.
This happens also when starting from a empty, fresh mpc3 project.
I'm on a live2, so I was thinking hardware contraints, but this seems kinda related?

It crashed during a rehearsal with my band.. the screen froze and audio stopped working and i had to hard reset.
Yesterday one of my synths stopped receiving midi for no reason. Restarting solved the problem
Ive also had the screen freeze on the 'shutting down' message.. When I restarted, the project was different as if it was a previous version and not the most latest.
I've started to quit my live project then open a blank new project and then powering down to avoid this.
My projects are already pretty light in terms of CPU hogging plugins and number of channels! Not what i signed up for!

Sounds like a nightmare. It's at least comforting to know they are hard at work making sure the OS works perfectly before pumping out new machines. Oh wait..

Do a Preference reset if you haven't already & send a bug report to Akai:
https://support.akaipro.com/en/support/ ... al_support