This is awesome work, Logan! I'm looking forward to exploring this setup. It's going to be an excellent resource for others looking to do the same. Thank you. Fantastic job!

The Kenton hubs are solid. The MRCC is very versatile but much more complex. There are others out there but I've not had experience with anything else.

Hi Rudi, Two notes played on the same MIDI channel will only issue one note of the same pitch at a time, even when the notes are from different tracks. ARP monitors all active notes and does not send a new note if that pitch is already active. It simply updates the note off timing; based on the gate length of the longest active note. That is unless one of the tracks is in MONO Voice Mode, in which case the active note is stopped and retriggered. I hope that helps.

Coming soon it will be. 😊

Not currently. However, we have been working on a solution for external patch management that will be available in a future update.

When you say MIDI-Thru, are you trying to use the MIDI notes, that are used to play ARP, to also trigger something else on the Move? ARP prevents Incoming MIDI messages being returned on the same USB port. This is to prevent circular reference loops that would cause crashes if both devices are set to Thru. You can of course use the MIDI output from ARP but there must be something blocking the output to Move or Move receiving it. Do you have the right MIDI output Channels setup? MIDI Thru enabled? MIDI Output Options set to ALL?

Firstly, Do you have the Patch Change Behaviour to Non-Stop or Retrigger? Also, patch change switches on the bar. You'll see it says "loading..." before switching. ARP does need to recalculate the 4 sequences when loading in a patch. However, this should all be done within a single cycle, well within a MIDI Clock tick. There shouldn't be a pause when calculating as the MIDI output has priority. However, if you are sending the input chord directly on the beat, ARP will calculate the new sequences and apply them on the next active step (usually within 1 clock tick). So ideally, you want to be sending the new chord before the next beat you want it to play on. If you can share a video of the behaviour it will help me understand the setup and shed some light on the steps to recreate if there is an issue.

Ok, Thanks for clarifying. It is as I understood and part of the design. I'll keep you posted.

I've no hands on experience with the Buchla but it should be simple to set up and I think you'd get a lot out of the pairing. As you say, MIDI Connection is a single DIN Cable. Looking at the MIDI Implementation chart, you can use ARPs note sequencers to drive the melody, and ARP's CC Output to modulate Velocity, Pitch, Portamento, Timbre, Modulation, Pressure and Slew. I'm not sure if MIDI Note Velocity is supported, which is a shame because, if it did, you could make use of the ARP's Rhythm patterns. I'm not convinced that the Buchla supports MIDI Gate either, so set your gate very short and maybe set ARP's Voice Mode to MONO. Using ARP's Note and Scale Locks, you'd also be able to sequence the Triggers on the lowest octave, like setting up ARP to run a drum machine. I hope that helps.

Yes, V8 includes the Chord Sequencer Updates. The sequences will be saved. I just want to check though... Are you looking for means to lock in the sequence so it cannot be changed by pressing the note buttons?

If you mean each MIDI CC Output should use the ARP Track's MIDI Channel, rather than the Global CC Ouput Channel... You can, but you need to install the latest firmware from midicake.com/downloads We added this as a quick update after the V7 release, following this post... https://www.midicake.com/forum/get-help/understanding-new-midi-cc-controls Once v1. 5.7.4825 is installed, go to SET Mode >> Menu >> CC Output Channel and select "Per Track". CC Output then uses the MIDI Out parameter of the same track as its MIDI Channel. I hope that helps.

My first thinking is that there is perhaps a MIDI message overload that the MFB cannot handle. Does it happen if you only run ARP with a single track unmuted? And only a reasonable time division, e.g. 4/1? With 4 tracks, there's 4 times the midi data. It should be able to handle 300 messages per second but I don't know the specs for that synth. Are you sending MIDI CC LFOs too? My other suggestion would be to see if the MFB uses MIDI to change patch and perhaps some message number is trying to change to the current patch. Unlikely but worth checking. Lastly, Have you tried a different MIDI channel? If there are any spurious messages, then changing channel may help. Let me know and I'll keep thinking on it.

We seriously considered a "non-destructive edit" option or having a save button option. However, I've always found myself forgetting to save something that I've made, which is pretty frustrating. So instead, we implemented the Patch Reset options. Press and Hold the LOAD/RESET button to open the Patch Reset menu, here you can select 1 to go back to the last time you loaded the patch. Also, as you suggested, the COPY function, in PLAY Mode, can be used to create multiple save points. Perhaps we could add a global Setting to disable auto save in the future but it's not on our roadmap right now.

Yes, I spotted this. I'll get it updated. Thanks! Glad it's sorted.

I've been thinking on this topic and considering ways to reduce ARP's output. Perhaps options to reduce the CC Output rate (currently 50Hz). MIDI devices can usually handle around 300 messages per second, so 4 channels of CC plus the occasional note message shouldn't exceed this. However, there may be other devices, emitting messages, in the loop and as ARP's capabilities continue to increase, I need to consider and handle potential overloads In this case though, I think the receiving device does need to handle the overload without crashing.

These MIDI Notes are used for daisy chaining ARP's. You can disable them by setting MIDI Output Channel to OFF. In SET Mode, press menu until you see MIDI Output Channel (Note Sync) Set this to OFF and the notes should cease. Let me know if this doesn't resolve it for you.

Cheers for the feedback and your preferred solution I will definitely look into a solution.

That does sound very strange. Do you have ARP's MIDI Control Mode set to IN or OFF? I just wonder if the transport messages are messing with Blackbox. When I get back to the office I'll have a look at the USB MIDI Messages. I'll also do some research on the USB Host and Blackbox, to see if I can find anything. ARP is Class-Compliant and there are no other protocols/coms messages in ARP's logic, so it has to be MIDI or something really odd.

Per Track CC channelss is available now. Head to Midicake.com/downloads for the latest update. Setting the exact numbers of bars for modulation rate is not currently available but is something we might consider. I haven't done this yet because it involves lots of scrolling (1 tick to 256 bars). plus, it increases the memory needed to store the selected values. Also, where is the limit? You might want to define a specific number of MIDI clock ticks! I'm just highlighting that it isn't a straightforward change. Perhaps we could implement it as an advanced option where you can choose a specific granularity at a global level and this overrides the limited mod rate options but limits the range of options. I'll think on it and see what we can do. Thanks for the suggestion though, much appreciated!

Mute doesn't stop MIDI CC output, in fact it doesn't stop the track progress, it only suppresses MIDI Note output. ARP is deterministic so as long as the sequencer is running, the sequences keep going too. This approach keeps everything in sync. If ARP suppressed the CC Output, then kicked the CC message back in when unmuting, there a possibility of a sudden jump in the CC value leading to undesirable sounds. A bit like when you change patch on a digital synth with pots, the Synth control value and the potentiometer position doesn't match until you turn the knob and suddenly the sound changes drastically. What led you to the question? Is there a scenario where this behaviour is causing issues? Poly and Mono Voice Modes have no effect on CC output. They simply control concurrent MIDI Notes. I.e. Poly allows notes to be layered.