Diese Seite ist auf Englisch.
Troubleshooting
Start with the status line in the header display. It names most connection faults; the table in Connecting explains each one.
Installing and starting
Windows says "Windows protected your PC". The installer is not code-signed yet. Click More info, then Run anyway. To check the file, compare its SHA-256 checksum with the account page; see Getting started.
Nothing reaches the instrument
The display reads NO MIDI. No MIDI out is selected. Open Settings → MIDI and choose the port connected to the MKS-70's MIDI IN.
Controls move, nothing changes in the sound. Check in this order:
- Firmware setting. On an original Roland ROM, a Vecoven setting changes nothing: the original ROM ignores single-parameter messages. Choose Original Roland in Settings → Instrument. See Firmware.
- Original ROM, nothing read yet. Edits are sent only after the unit has sent its current patch: select a patch, or use Read from unit. A half marked TONE NOT READ holds back its edits until you select a patch that uses that tone.
- Channel. The app's Channel must match the MKS-70's. See Connecting.
- Standby. In Settings → MIDI, the switch must read Transmitting.
- Ports released. If Ports released shows in the top bar, the app has released its ports. Click it to take them back. Silent. If the antenna icon in the top bar is red and reads Silent, nothing is sent. Click it.
- A sequencer lane in Abs mode. While an Abs lane is aimed at a parameter, the panel knob for it has no effect. Set the lane to Rel or aim it elsewhere.
- Listening to the other half. Edit Target chooses the half you edit; Listen and the balance between the tones choose what you hear. If Listen is on Upper and you edit Lower, you will not hear the change.
Init, Send all or a library sound reports "N of M reached the unit". On the Original Roland setting, read a patch from the unit first. Otherwise check the firmware setting and the MIDI out.
Nothing comes back from the instrument
The display reads NO MIDI IN. Choose the input the MKS-70's MIDI OUT is connected to in Settings → MIDI, and check the ports are not released and the app is not in Standby.
The display reads NO REPLY, Read from unit times out, or a bank scan stops after three silent programs.
- Check the cable from the MKS-70's MIDI OUT to your interface's MIDI IN.
- Check the Channel. The MKS-70 answers a patch change only on its own channel. Notes on another channel may still play, which hides this.
- Check that no other program holds the interface. See the next section.
- Check the MKS-70's own MIDI settings allow it to transmit.
The patch list shows numbers, not names. Names fill in as you select patches, or press Scan bank names in the Patch Browser. Scanning selects every patch, so store any unsaved edit first.
Ports busy or shared
A DAW is open and the MKS-70 looks dead. The DAW may hold the interface. On a UM-ONE with a DAW open, the input delivers nothing while the output still works. Release the port in the DAW or close it, or use the plug icon in the app to hand the ports over and take them back. See Connecting.
Roland UM-ONE: the app or the DAW cannot open it. The UM-ONE driver allows one program at a time. Close the other program, or use the plug icon to release and take back the ports. Any program that uses MIDI can hold it, not only a DAW.
The output works but nothing comes back, and no MIDI program is open. A program running in the background can hold the input without a window: a Stream Deck MIDI plug-in, a controller's helper service, a DAW's audio engine left running after the DAW closed. Look near the clock and in Task Manager for such programs, quit them or switch that input off in their settings, then click Rescan ports. If nothing obvious is running, unplug the interface, wait five seconds and plug it back in.
An interface is missing from the port list. Click Rescan ports in Settings → MIDI. If an interface was moved to a different USB socket and still does not open, restart Windows, or move it back.
Controls missing or doing nothing
The PWM, LFO Fine, KF Fine and LFO Phase controls are missing. They exist only on Vecoven 4.x firmware. Set Settings → Instrument → Fitted ROM to Vecoven 4.x if your unit has it.
The Vecoven 4.x controls are shown and do nothing. Your unit has Vecoven 3.x or the original ROM. Choose the matching setting.
Portamento does not glide. Set Porta Time above 0 and play legato: the MKS-70 glides only between overlapping notes.
A matrix routing will not arm. Some parameters cannot be driven by an engine; the row says why. See Modulation.
The Modulation window warns about the bus. The engines use more than about 60 % of the MIDI cable. Lower the matrix rate, use fewer routings, or thin the pattern.
Arpeggiator or sequencer plays nothing. Check that Arp or Seq is armed, a MIDI out is selected and the app is Transmitting. With MIDI Clock chosen, the engines wait for Start from the clock port. With Start: On key, they wait for the first note from the master keyboard.
The sound I made is gone
I selected another patch and lost my edit. Selecting a patch reloads it from the unit's memory. The MKS-70 cannot store over MIDI: press WRITE on the unit to keep a sound there, and save it to the library to keep a copy on your computer. See Library.
I pressed WRITE and the sound went to the wrong slot. WRITE stores into the slot chosen on the unit. Use Write current sound → in the Patch Browser to select the slot first.
The patch plays an old tone after WRITE. A patch stores which tones it uses, not the tones. Write each edited tone to tone memory on the unit as well.
Still stuck
Write to hello@knobsmith.com with your app version (Settings → About), which firmware is fitted, your MIDI interface and what you saw. If the app crashed, attach %APPDATA%\MKS-70 Controller\logs\main.log if it exists.