このページは英語です。
Connecting
Wiring
| From | To | What it carries |
|---|---|---|
| Interface MIDI OUT | MKS-70 MIDI IN | Edits, patch changes, notes from the app |
| MKS-70 MIDI OUT | Interface MIDI IN | The unit's replies: patches, tones and names |
| Keyboard MIDI OUT (optional) | Interface MIDI IN | Notes and controllers you play through the app |
The return cable is not optional if you want the app to read anything. Without it the panel can still send edits, but it cannot show a patch's real values, learn patch names, scan the bank, or edit on the Original Roland ROM setting, which builds every edit on top of what the unit sent.
Interfaces
Any interface that Windows lists as a MIDI port and that has a 5-pin DIN output should work; the controller has been tested with the Roland UM-ONE. On an interface with several ports, give the MKS-70 its own port if you can. Some drivers, Roland's UM-ONE among them, let only one program use the interface at a time; see Sharing a port with a DAW.
Channel and device number
The app and the MKS-70 have to agree on the MIDI channel.
- Check which MIDI channel the MKS-70 receives on.
- In the app, open Settings → MIDI and set Channel to the same channel.
The unit answers a patch change only on its own channel. If the channels differ, notes may still play, but selecting a patch brings no reply and every read times out.
SysEx device # sets the device number inside SysEx messages. If you leave it alone, it follows the MIDI channel, which is what the MKS-70 expects. Unit 1 corresponds to channel 1.
Choosing ports in the app
Open Settings (the gear icon in the header) and choose the MIDI tab.
| Setting | What it does |
|---|---|
| MIDI out — edits and notes go here | The port connected to the MKS-70's MIDI IN. |
| MIDI in — the unit's replies | The port the MKS-70's MIDI OUT is connected to. |
| Keyboard A / Keyboard B | The ports your keyboard and a second controller are on. Their notes are forwarded to the MKS-70 on its channel. The Keys menu in the top bar is the quicker way: it lists every free input and marks the ones in use. |
| Keyboards play this | Whether the keyboards play the MKS-70. |
| Rescan ports | Reads the list of ports again and opens the keyboards again, for example after you plug in an interface or another program lets go of one. A device switched on while the window is open turns up by itself within a few seconds. |
| Transmit on / Silent | When Silent the app sends nothing at all. The antenna icon in the top bar is the same switch. |
| Routing on / DAW mode | In DAW mode the app does not pass your keyboard through; your DAW plays the MKS-70 and the app only edits. |
| Channel | The MKS-70's MIDI channel. |
| SysEx device # | The device number in SysEx messages. Leave it to follow the channel. |
The line at the bottom shows the output and input in use. The app remembers your choices and opens the same ports at the next launch.
Do not choose the MKS-70's own input as the master keyboard. The app ignores it as a keyboard, because the synth would hear its own output.
A controller you have bound with MIDI Learn drives its control in the app and is not also passed on to the MKS-70. See The panel.
Sharing a port with a DAW
Using the plug-in inside a DAW instead of the app? See In your DAW, which covers both ways of sharing the interface.
On Windows, most MIDI drivers let several programs open the same port at once. A DAW and the MKS-70 Controller can both send to the MKS-70 and both receive its replies. What they share is the cable: a MIDI cable carries about 3,000 bytes a second for everyone on it, so heavy traffic from both programs slows both down.
Some drivers, the Roland UM-ONE among them, allow only one program. With those, the first program to open the port keeps it.
Release MIDI
Settings → MIDI → Release ports hands the ports to another program without closing the app.
- Click Release ports. The app closes every MIDI port it holds. Your port choices are kept, and Ports released appears in the top bar.
- Use the other program.
- Click Take ports back (or Ports released in the top bar). The app reopens its ports.
If another program still holds a port when you take them back, the line under Ports names it. Close or release the port in the other program and take the ports back again.
A keyboard that another program holds is named in the same way, under the keyboard's menu: “… could not be opened — another program has it”. Close the other program, then press Rescan ports.
What a DAW holding the port looks like
When another program holds the interface, the app may still send but cannot receive. With a UM-ONE and a DAW open, the input delivers nothing while the output works. In the app:
- The status line in the display reads NO REPLY after you select a patch.
- Read from unit in Settings → Instrument reports Read timed out.
- A bank scan stops with "The unit answered nothing for 3 programs in a row".
- The knobs may still change the sound, so the MKS-70 looks connected.
Release the port in the DAW, or close the DAW, then select a patch again.
Status line
The status line in the header display tells you the state of the connection.
| Status | Meaning |
|---|---|
| NO MIDI | No MIDI out is selected. Nothing leaves the app. |
| NO MIDI IN | The app has no open port to read from: no MIDI in is selected, the ports are released, or the app is in Standby. |
| NO REPLY | The app asked the unit for a patch and nothing came back. |
| SYNCING | A read is in progress. |
| SYNCED | The panel shows what the unit sent. |
| EDITED * | You have changed something since the unit last sent its patch. |
| READY | Connected; nothing read yet. |
The same line shows the firmware setting (ORIGINAL ROM, VECOVEN 3 or VECOVEN 4), and MOD or PLAY while the modulation matrix or a pattern is running.