Heyloo, so in my neverending quest to sync midi gear with ableton and avoid clock wobble I noticed that higher bpm has a much higher variance. For now I have found sending arp half clock and internally using 2x rhythms is significantly more stable and thought others might also find that helpful. (I am measuring with just clock no mixed midi traffic) Double / Half Time Currently at tempos >97 if I send arp a half-clock things lock in way better and rarely even get wobble on arp's tempo reader. It is fine to work in but a little bit awkward, if there were maybe some sort of option for clock scaling that I could set it to internally double all of my tempos in the background that would be perfect. Sensitivity Scaling Not sure if it's helpful and I'm not sure how it's implemented, but based on measuring things, I thought that perhaps the sensitivity of the internal logic isn't scaled proportionally to account for ie: 120 is much closer to 121 than 60 is to 61 this is also I think why drift is more perceptible at high tempos* as loose (ie: a choir member 5-10ms late in a 60bpm-choral is fine, but if something is running 16ths at 134 and wobbles 50ms it feels like they've lost the groove). *Not tempo per-se, but where the perceived audible pulse is (ie: if 16ths is your pulse, it's the time between those) Hope this is useful for anybody else :)

So syncing between ableton and external gear has proven to be quite the general quagmire largely stemming from the various physical and digital systems involved in audio conversion processing. I decided to dig in and see if I could get midicake to really lock in on the beat in a way I can quickly add to projects and it lead to some interesting discoveries I thought would be helpful to others to know so you don't have to also feel crazy. Hoping others might also have some tips or thoughts to add. Midicake Tempo Wobble My arp usually gets a lot of wobble, but switching to audio sample rate of 48khz locked it in and with ableton leading I see significantly less tempo drift. Not sure if this is related or a false indicator. Latency Adding latency ANYWHERE in your ableton project will put delays on the notes received in ableton regardless of 'Reduced Latency When Monitoring' or 'Keep Latency' settings for a given track. This is not in any way unique to midicake, I could reproduce it on multiple devices. This means that if you configure the latency by either adjusting track delays or shifting the control clock from ableton, you will need to update it every time you add a latency causing device to your project. This can be an ok way to work, just good to remember later as you build out a project. (duplicating a few limiters with a long lookahead is a good way to see this) Unfortunately, here lies a special quirk where adjusting track delays can also affect latency which requires adjusting track delays which affects latency which requires adjusting track delays which affects latency (...) Delay Compensation The only way I was able to get consistent timing that I could set and forget was disabling delay compensation which means you'd have to manage your tracks with audio delays (track delay is disabled when delay compensation is removed) HOWEVER, if you do this, routing midi internally will add delays unless 'Keep Latency' is enabled on both tracks, but receiving direct from midicake will be on beat. Delay Compensation: NO, Keep Latency: OFF No Delay Compensation and Keep Latency Enabled Requires Clock Shift This config is consistent for Midicake Input, and for internal ableton midi routing, but requires shifting the midiclock in ableton's midi settings. Leading Chords The end goal is to send a chord track out to midicake and get back four lanes. To ensure harmonies change on the downbeat, I had the most success by leading 5ms. Not sure yet how to do this without delay compensation. Hopefully this helps anybody else out there navigating this, if anybody else has tips let me know!

I built out a nice bank of midicake patterns that I can jump between, so the way I cue this live is to press LOAD on midicake and leave that page open so when I notice other transition cues musically I can easily glance over and one press launch next pattern synced with ie: drum machine change I've noticed a lot of strangeness with this where sometimes the downbeat gets slightly shifted back or forward where midicake's downbeat is off +/-3/16 The weird part is that if I give a long cue to midicake ie: press the next pattern on beat 2 so that it has a few beats to count it starts to lose things. However, if I time it and cue right on the and of 4 it seems to land together way more consistently. I've also gotten better at a live reset stopping on 3 and restarting on downbeat, but tapping early is far preferable Some Notes: if I run at 133 or so I need to do lots of manual resets and midicake seems to really only land if I nail the cue on the and of 4 lower bpms had less of an issue ~111 or so, however. If I had previously been at high tempos and getting lots of drift then it doesn't matter what tempo I use and drift expands. If I do a full power disconnect and plug back in, things sync up better for a bit. This makes me think maybe there's a memory leak or some traffic getting clogged? I was also sending new chords to midicake to coincide with the program changes and it feels like midicake ever so briefly pauses to process this and then comes in late

Move->Cake works fine, but Cake->Move isn't functioning. I've been surprised by the Move and find it useful for sketching things and it plugs right into midicake really nicely Unfortunately traffic doesn't route back into the Move. I checked on some other connections and traffic seems to run fine from the midicake so I'm not sure what would prevent this. I mostly want to be able to use the midi-thru back into the move over usb. I love having the back-capture midi function on move so I can 'jam' around and if I liked a moment I can just cap it and play it back I have a midimate cable that I can plug from move into midicake but then I have to also find power elsewhere and the clock on this fluctuates a lot and loses the downbeat. USB works to MRCC and my Laptop

Hey, sorry I checked out for a bit, I'm not positive it's the same issue that was/is crashing the mrcc, but making a new thread for others. I was hoping the firmware update might catch this somewhere and get lucky, but no dice. Unfortunately, I'm in ableton mode so using that again and midicake is crashing it quite often (9 times in last hour) It could be something else, but it seems like all signs point to cake. • brand new computer / fresh installs • computer and ableton working fine all day and last week, moment plugged in cake crashing consistently (including on brand new projects) • my midi monitor consistently after every crash the last messages were the note offs for every channel • in crash logs, it looks like midi thread is locking up but not so helpful Maybe Good News? The note offs are actually not the last message, but there is always a couple straggler notes thta come after (like 1 to 5). I don't know how midi handles this but could things be choking on the note sends directly after the note offs? General Info • Macbook • Ableton 12 • latest cake firmware • midi over usb Thanks! Cake is definitely one of my favorite devices and I love how it works, hoping this one can get fixed! I want to use more cake but I keep getting k/oed All the best

Hey, I'm not sure why but the ARP will occasionally crash my MRCC, when it does so, I'm also unable to turn the MRCC back on because as soon as the arp gets power it blocks things again. The only way to recover is to unplug the arp. It happens periodically, but I have one use case that is 100% reproducible that is maybe helpful: MRCC Has onboard clock routed to the ARP, however, it's difficult to trigger start/stop etc. so I send that from my RYTM. My other devices seem to play nicely, but the ARP gets locked up. I triple checked that there's no midi-thru or other thing making a loop and I don't know if the clock thing is a herring, but if it prompts you to have an idea for a fix let me know. I'll try with midi cables later today, but it's nice to have all the power and midi in one cable longterm.

Triggering mutes remotely is very useful, and in some ways I kind of like the current trigger-only mute option because I can overlay various triggers that mix and match things in fun ways.. The main problem is that right now my controllers need some context of the current mute state before knowing whether to send a trigger. This can also complicate things if for example A and B both go to C, but don't start with the same mute state. This is cool sometimes, but if I always want C to begin with tracks[1...3] muted I can't really program it currently. tldr; Current: Mute Toggles on cc:127 Desire: Mute on — cc: 127, Mute off — cc:0 If I missed another way to do this let me know :)

Perhaps I missed it in the documentation, but it seems the only way to proceed through a list is one direction, this is workable but I can't tell you how often I overstep and end up circling all over, or I'm coordinating to options in a list and get lost in the circle (especially in the general menu) I have a few proposals for bidirectional navigation, if it already exists and I missed it let me know and I'll leave youu OPTION 1: Menu Option: Up/Down Navigates Lists I don't ever use the up/down buttons, and from what I can tell they seem to duplicate the knob function. It can be useful for specifying single steps, but the cake's knob has nice solid 'ticks' so single values is pretty easy. The menu could also have three options to reverse this so ie: List Navigation [better name here]: 1. none (current) 2. up/down 3. knob OPTION 2: HOLD + Knob or Arrows Instead of tapping, ie: [menu], if I held the button it could push knob control to list navigation Hope this is helpful