Cake Crashing Ableton

So after getting another chance it seems ableton is mostly ok as long as the arp is follower not leader so this is fine for my purposes, the leader was just very briefly setting up.

I'm still not sure what could have happened to the oxi, it can draw power from my computer but even that doesn't show up on connections on the system report (incl when I boot oxi in safe mode). I don't know how to recreate this locked usb mode that the midicake was in when it was somehow blocking things, my guess is that it was something to do with my presets prior or sth.

in this locked state, midicake was behaving exactly as the oxi is now, it wouldn't show up in system reports, could get power, but no midi was able to come in or out

Are there any really low level system messages that are exchanged from teensy that maybe somehow didn't make it to the right device? I haven't worked with too many physical protocols like usb so I'm not sure what sort of things might back up the pipes or block things.

My thinking is like a network call that maybe started a message protocol but left it unfinished? This could explain the multiple devices getting blocked by oxi after plugging in, maybe combined with oxi missing a resetIfIncomplete somewhere

midicake and ableton move seemed able to shake off the odd state but the oxi persists. I'm going to try a full battery drain to see if maybe that triggers some additional start up procedures

on a good note, the new arrow mode is great and makes it easier to recreate lost things!!!! also excited to delve into the new modulation possibilities

even through all of my midicake issues I still push through because the device is so interesting!

some things to add:

ableton latest crashes on both firmwares, it might be something with follow mode, I think ableton as leader is working better

it seems that it also somehow fried my oxi one usb port (and ableton move) and it no longer functions or connects to any device even in reboot mode after a factory reset. I plugged it in because the midi monitor on the oxi is a really reliable place to debug usb stuff, and now it seems that the oxi is acting how the midicake did before I reset the midicake.

I know that the oxi said there is some risk to plugging non-music devices in, so I'm wondering if there's something in the usb protocol that's not meshing with other systems. (a similar issue to sometimes in the past plugging monitors into things could mess things up internally.)

it is able to send usb power out, so the physical port is ok, but it no longer receives or sends any midi data over usb.

confirmed with my keyboard, a midimake ex cable, two computers

I also tried to plug the midicake to an ableton move and it caused that usb port to no longer function as leader or follower to any other devices. This one was luckily fixed without a factory reset, somehow plugging my keyboard in unlocked it and everything then worked with other devices as normal. not sure if the keyboard could have maybe finished the second half of some protocols that were blocking

if you have any tips for the oxi, right now it's seeming like I don't have any options, there is a ble way to update, but resets and safe mode also don't connect to anything so hoping there's a pro tip

hey, I just updated to the latest firmware and I wanted to double check that the fix you sent me got merged in :)

I am having a lot of issues with it and I'm getting ableton crashes again.

after the update it would connect to things, but it wouldn't send or receive any midi notes.. except, if I hit the 'stop' button a bunch on the midicake I would hear a high pitch sound like that was somehow sending a midi note

I fixed this with a 'factory reset' so lost some things but very recoverable

unfortunately something in there is causing the latest LIVE to crash pretty immediately with just an empty project trying to see if midi in is coming through.

it happened a few times right in a row so I'm not sure what to do

I could workaround with midi cables but I really like to just sit with my laptop sometimes and have one cable

I downgraded back to the firmware you sent before for now, but I haven't retested with this version yet on the most recent ableton update, so it might be something that changed on their end

FIXED AND WORKING NO PROBLEMS :)

Hey, just wanted to let you know that the firmware you sent me has resolved all of the problems I was having and I haven't had another issue with ableton since.. buuuttt..

Yesterday I finally had a long stretch of time to try again with the MRCC and that also had no problems for hours, no crash!

Thank you thank you thank you for fixing these! I love the midicake but I was really getting blocked by this and I'm really happy I can use the cake in my setups again :) it's the only device I want everywhere! Also, I realized when testing the MRCC why I double tap stop buttons so much– my virus has a bad habit of notes getting stuck and the panic buttons are usually sort of far, but double-stop kills them all

Hey I think I have the same setup as you, but here's the screen shots in case there's something I'm not seeing :)

'-> ARP' is my Lead Sheet, others are back in to Able

Hope it helps :)

Hey yea, I have all of that stuff hooked up and working properly, the only issue is the crashes keep wiping a bit of work, especially with serum. Removing serum helped reduce frequency but they're still definitely an issue.

Is it possible that something is corrupt on my hardware? Three devices crashing in the same way with cake (MRCC, Digitone, Ableton).

You can tell that something is blocking the main thread because the ui starts to glitch up a little bit before it catches up with itself, eventually crashing (or rarely just fully locking until I kill it). It feels like the same as the behavior when I experienced the other hardware crashes with cake on Digitone and MRCC.

It has all the tell tale signs of software locking up in a loop somewhere, it seems like midi based on other behavior, and my assumption is that it's something with MIDI-CC messages because blocking them immediately resolves my issue.

Cake Loops:

I think whenever there's a loop in the setup (which happens a lot with cake), like in the example above: ABLETON CHORDS -> out to -> CAKE CAKE MAGIC -> back to ABLETON Then one of the devices sends a stop or all notes command or something at the wrong time and they get trapped telling each other to stop. This might be why I'm experiencing it when others aren't because I'm also obsessive about the stop button. I don't trust things to ever start correctly and double tap the stop button reflexively.

Maybe Helpful Details in case they point somewhere:

• obsessive stop button tapper (see above)

• cake has always been MIDI-Control: IN in all of my cases where things got locked up

• I'm usually using USB

• I removed all sync and just used Live-Play for a bit and no crashes, but lost some of the rhythms

• my chord out track from ableton to cake always has a negative 6 to 10 millisecond predelay (otherwise chord changes take affect on arp after the downbeat and an attack is added on the second beat if one is not there in the rhythm ptrn)
  

Nice Things::

• it's not all bad! when things crash, I usually don't lost much on the cake since it's all saved outside of the computer

• the new binary modes are really neat, a great way to reign in things getting loose and make some variety. Also great UI/X

• I still love cake even tho she is crashing all of my things haha
  

Hi Logan,

Can you share how you have ARP configured in Ableton's MIDI setup screen?

I use Ableton and ARP daily with no issues so something is amiss.

How are you trying to work? Just using Ableton as VST host and MIDI recording or more?

Let us know and I'll try to find the cause.