10-02-2021, 03:50 PM
(10-01-2021, 09:31 PM)Jesse Johannesen Wrote: I don't know if the 37 is specifically in our arsenal, but the MRCC was designed interfacing primarily with arturia devices (keystep and BSP) as the primary inputs, so it seems really unlikely that they would develop a completely different USB protocol for the 37, but it's possible. can we test the Keystep without the feedback and see if it still causes a fault if the MIDI goes out directly to a synth. If we can establish that it's not feedback related that would help.
I suggest we test it with just the simplest setup possible, like MIDI in from a keyboard into port 1 on channel 10 out to keystep on USB whatever, channel 10 and out keystep din into a synth to listen to the notes. If this doesn't hang then try incorporating the same feedback routing and see if that hangs us up.
FYI I added a feature request to identify midi loops and block them rather than hang the device, so hopefully we can make that happen at some point to avoid this kind of thing. I'm sending that NDLR FW now by the way.
Jesse
Odd, since as part of the beta test team, I have been using my KeyStep 37 (and Pro and KeyLab 61) connected to the MRCC from the beginning with no problems.
I kept my Arturia stuff updated to the latest versions and have the 37 connected (and powered) via the USB only and it's been solid.
I can check my 37 configuration tomorrow when I'm back in front of my machines if necessary.