-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Applies to windows VST and Standalone versions of the panel.
Here are some tips on how to workaround some known problems.
Make sure you set up the panel with proper MIDI settings.
It's required to set MIDI Input Device and MIDI Output Device settings, as well as MIDI Input Channel and MIDI Output Channel in order to make this panel work.
MIDI settings of the synthesizer should match the panel.
Also note that MS2000 only responds to SysEx control change messages when it's in "Edit" (or "LCD") mode. The panel is trying to set synthesizer into Edit Mode on demand, but there is a chance that for some reason it wasn't done.
In this case make sure to set LCD mode manually.
This could happen after updating or rolling back the panel version. To solve this problem, you can try to delete the following file and restart the panel:
C:\Users\[username]\AppData\Roaming\ReMS2000\.delete_me_to_reload_resources
If this solution does not help, try to delete the entire "C:\Users\[username]\AppData\Roaming\ReMS2000" folder instead of a single file.
First of all it will be a good idea to cleanup the folder "C:\Users\[username]\AppData\Roaming\ReMS2000". Be aware that standalone version will lost is's saved state then.
4. Cannot retrieve single program or bulk dump from the synthesizer, the message "Data transmission error" appears
I don't know the exact reason for this to happen, but it looks like the MS2000 is flooding the MIDI connection with its realtime "sensing" messages.
My recommendation is just to set your MS2000 "Clock source" to "External" during program data retrieval operations if you encounter this problem.
5. The “Failed to open device” error appears when selecting a MIDI input or MIDI output from the panel inside the DAW.
This might happen if assigned to the panel MIDI device is busy by the sequencer. For example, a synthesizer is selected and activated as a MIDI controller in the DAW settings.