You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, thanks for this software! I have a small issue that I managed to work around, but maybe it can be fixed properly.
I first tried talking to my BCR2000 using a USB connection. This is very fast, maybe too fast: Whenever I tried to send a preset to the BCR, lots of error messages appear in the console about lost messages, and the BCR2000 stops accepting the data somewhere around the 6th or 7th knob in the second knob row, displaying "ER22". I then configured the BCR2000 to use stand-alone mode 4 instead and connected it via MIDI. This was a lot slower but it worked. Sending the equivalent SYX file using another tool like SendSX via the USB connection is also fine.
To me this sounds like delaying the sent MIDI messages by a bit could potentially fix this issue.
Platform: Windows 10
BCR2000 firmware version: 1.10
The text was updated successfully, but these errors were encountered:
@sagamusix Thanks for the report! I was out of country for a while, so sorry for getting back on this only now. It sounds indeed like a speed issue, I will test with my BCR2000. I think I did not use it in USB mode, but have to dust it off because it has been sitting on a shelf for too long now.
First off, thanks for this software! I have a small issue that I managed to work around, but maybe it can be fixed properly.
I first tried talking to my BCR2000 using a USB connection. This is very fast, maybe too fast: Whenever I tried to send a preset to the BCR, lots of error messages appear in the console about lost messages, and the BCR2000 stops accepting the data somewhere around the 6th or 7th knob in the second knob row, displaying "ER22". I then configured the BCR2000 to use stand-alone mode 4 instead and connected it via MIDI. This was a lot slower but it worked. Sending the equivalent SYX file using another tool like SendSX via the USB connection is also fine.
To me this sounds like delaying the sent MIDI messages by a bit could potentially fix this issue.
The text was updated successfully, but these errors were encountered: