To see this working, head to your live site.

Cake Crashes MRCC (and blocks restart)

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.

28 comments

Comments (28)

Chris Brown

Sep 02

Just an update on this thread. I have now completed the work to prevent ARP outputting ALL SOUNDS OFF when triggered from an external stop event. This should resolve issues external devices when pressing the panic button.

ARP Stop Event behaviour has been updated as follows: -

This change will be included in the next firmware release. If you want to test the new firmware with your hardware, I'd be happy to share the beta firmware.

logan.william.wright

Jun 27

submo

Jul 01

Replying to

Ok bud,

Functionally I still think I would prefer if CC123 & CC120 was separated somehow, and not sent together, so the synths gets chance to play out any release, but we'll see how you get on.

Chris Brown

Jul 01

Replying to

So... Press Stop = ARP stops generating new notes and triggers the internal sequencer to stop when all notes have completed. Press Stop again = ARP emits All Notes Off (CC123) Press Stop again = ARP emits All Sounds Off (CC120) = Panic I'll test it with various sound sources and see how they behave. I'll also test not sending 123 or 120 at all when receiving and external Stop to see how they behave. I'm wary of causing other problems by making this change.

submo

Jul 01

Replying to

Ok scrap that..... I thought pressing stop once will keep any played notes held, I didn't realise they will stop after their gate time... Sorry bud!

....but I think separating them anyway like you have wrote there would still work..... Say If you wanted to stop the notes early, but not cut all the sound.

Edited

logan.william.wright

Jun 27

I did one more test with a device that sends transport via CC and for this one, the ARP works properly supressing PLAY, but still outputs on STOP, so I get two stop messages sent

logan.william.wright

Jun 27

Hmm, weird, I can reproduce it via any combination so far, I've gone through every cord combo I can think of some updates maybe to help: Firmware: Yup, definitely 15.5.1973 Forwarding: To be more clear, it's not sending the transport message, it's converting it to a CC transport message.

Arp Settings: MidiControl: IN MidiThru: OFF

Setup:

Route Rytm into ARP (any port, midi, host, usb)

That's all I have to do and if I send transport commands from there while reading ARP output, I can see it every time output a CC

(also works with digitone)

Chris Brown

Jun 19

Firstly, Is ARP's MIDI Control Mode set to IN?

ARP only emits clock and transport messages if MIDI Control Mode is set to OUT.

So if this is the case it can only be MIDI Note Data or some USB protocol issue causing the problem.

We can eliminate USB MIDI as the culprit if you set ARP's MIDI Output Options to DIN ONLY.

Please try this and let me know. I don't have an MRCC to test it here.

Chris Brown

Jun 27

Replying to

Hi Logan,

Thank you for persevering with this and narrowing it down. I will take a look at this scenario this morning to see if I can replicate the issue.

Does it do it when MIDI Thru is disabled on ARP?

logan.william.wright

Jun 27

Replying to

Yup! I never use midi-thru, and tried also to toggle it on and back off again just in case but no luck.

Chris Brown

Jun 27

Replying to

Hi Logan, I have tried every combination I can think of with DIN, USB Host and USB MIDI. External gear sending transport, CC and Notes, DAW likewise and MIDI-OX simulating the above and capturing the MIDI data on it's way through in both directions. In all of these cases, ARP behaves and doesn't Thru transport messages, if Control Mode is IN and MIDI Thru is OFF. There must be some configuration/routing I'm missing. Just for sanity sake, can you confirm the firmware version ARP is on, it should have shipped with v1.5.5.3973 Could you possibly send me a photo of the setup with an explanation of the routing of all the connected gear, what is master clock, what is master transport and what is set to Thru? There is definitely something that I'm missing.