Its a bug in the Sysex implementation and is not related to the Eone.
the bug is if you request parameter status for either [60] or [61] the Mirage running MASOS sends back
Wave parameter updates for [60], [61], [62], [63], [64], [65] and [66].
The reason why I mention the MASOS OS is of the crashes related to incoming status bytes.
Which seems to be the same behavior as on the Soundprocess OS.
Hoping that this hints will help pinpoint the fault.
That makes sense because if you change the wavesample start or end (60, 61) then things like the loop start/end, size, etc may have changed.
So the Mirage probably recalculates those values and sends them back to you.
The onResponse() code will have to handle 60 and 61 separately when the Electra One sends out a parameter change for 60 or 61.
First step is to capture the size on the incoming message (does the Mirage send one big message with a single F0/F7 and all parameters inside it or does it send 7 separate regular size F0/F7 messages)?
If it sends back 7 separate messages for every change to 60 or 61 that you send, we’ll have to think of the best way to handle that.
Let me PM as this topic is only for the bug of the incoming sysex.
Cheers