Thanks for this. Sounds like those workarounds aren’t worth the extra work involved for this particular issue.
It’s interesting that the delay isn’t working for you either. @oldgearguy said above that it doesn’t work like one might expect. @martin, could you confirm if this is the case or if this is actually a bug?
I should say, btw, that Martin has already kindly done some testing on this himself after I DM’d him, but I started this thread instead of continuing to bother him directly 
yes, I played with the Bluebox but I have not been able to replicate it yet, My bluebox gets updated correctly after it receives the snapshot data. The throttling is not enabled currently, it was causing issues on mk1. When the rate was slow, the data stream could easily exhaust the available memory on mk1.
What’s strange here is that @davehouse has his BlueBoxes connected via MIDI I/O, meaning the data rate is quite slow for a modern device. I am currently in midst of finishing another bit of 4.0, I will look at it early next week.
Regarding the CCs, nowdays, many MIDI devices use CCs as they wish. Even Electra does that. That higher level of standard (assigning specific meanings to particular CCs) seems to be a thing of the past.
just wondering since @martin has not had issues – @davehouse is there a possibility that you have a MIDI loop somehow going on? Maybe try the update by unplugging the MIDI cable going into the Electra One and see if that changes anything.
@martin It’s a faff, but you might need to make sure all Bluebox controls are set differently to what’s on the E1 preset in order to know if everything is updating when MIDI is sent in bulk. The Bluebox template I use has 8 tracks with vol, mute, solo, pan, sends 1-3, fx1, fx2 all mapped.
@oldgearguy I tested using just E1 and Bluebox so no chance of a MIDI loop