Skip to content
Knobsmith
Menu

In your DAW

Coming soon. The VST3 plug-in is in final testing and is not on the download page yet. It will be a free update for every licence holder, with the same key. This page describes how it will work.

The MKS-70 Controller also comes as a VST3 plug-in. It is the same panel, the same modulation, arpeggiator and sequencer, on an instrument track, saved with your project. The download is on your account page, next to the installer.

  • Windows 10 or 11 (64-bit), or a Mac with macOS 12 or newer (Apple silicon or Intel), and a DAW that loads VST3 or CLAP plug-ins. Both formats are installed. The Audio Unit for Logic Pro and GarageBand is not ready yet; on a Mac with Logic, use the app beside it for now.
  • The plug-in is included with your licence and asks for the same key as the app. It takes the same seat: on a computer where the app is already activated the plug-in opens licensed with nothing to type, and the other way round. It is a separate file from the installer, and you do not need the installer to use it.
  • We are working through the DAWs one by one. The steps below follow each program's own routing; if a menu is named differently in your version the idea is the same, and if a step is wrong, tell us at support and we will correct this page.

Install

  1. Close your DAW.
  2. Unzip the download. Double-click Install.cmd and accept the administrator prompt. It copies the plug-in where every DAW looks for it, and replaces any older copy.
  3. Start the DAW and rescan plug-ins. Two plug-ins appear from the one file: Knobsmith MKS-70 (the instrument, the controller itself) and Knobsmith MKS-70 Audio Tap (an effect that lets the controller hear the MKS-70's sound).

Prefer to copy by hand? Put the folder Knobsmith MKS-70.vst3 into C:\Program Files\Common Files\VST3\.

On a Mac: close the DAW and open the .pkg (the full installer of the Mac build contains the plug-in; a plug-in-only package exists too). If macOS refuses it the first time, open System Settings › Privacy & Security and click Open Anyway. The plug-in goes to /Library/Audio/Plug-Ins/VST3/ and /Library/Audio/Plug-Ins/CLAP/. Then start the DAW and rescan.

First start

  1. Create a software-instrument track and choose Knobsmith MKS-70. Open its window.
  2. The first screen asks for your licence key. Paste it (your pilot key, or the key from your purchase). It is the same key as the app and takes the same seat: on a computer where the app is already activated the plug-in opens with nothing to type.
  3. The plug-in then asks which ROM your MKS-70 has, and shows the connection page described below. You can return to it any time under Settings (the gear) › DAW.

Connecting the MKS-70

Open the plug-in's window and go to Settings (the gear) › DAW. The page walks through three things, in order.

1 · The cable to the MKS-70

By default the plug-in opens the MIDI interface itself, so there is one track and nothing to route.

  • It is picked for you when it can be told: a Roland UM-ONE, or the only MIDI interface the computer has.
  • Otherwise press Find my MKS-70 and turn a knob on the unit's own panel. The plug-in listens on each MIDI input in turn (it sends nothing to the unit) and stops at the one that carries the MKS-70's messages. The output with the same name goes with it.
  • Or choose the ports yourself under MIDI out and MIDI in.

Then set the channel and unit number to the MKS-70's own settings.

Sending always works, even while your DAW has the interface open. Receiving the unit's replies needs the DAW to leave that interface's input alone, because some drivers (the Roland UM-ONE is one) hand their input to one program at a time (on a Mac this rarely applies: macOS lets several programs share an input). If the page says the replies are not arriving, switch that input off in the DAW:

DAW Add the instrument Free the interface's MIDI input Audio Tap
Cubase / Nuendo Project › Add Track › Instrument Studio › Studio Setup › MIDI › MIDI Port Setup: untick Active on the interface's input row Inserts of the audio track
Ableton Live Settings › Plug-ins: VST3 on, rescan; drag it onto a MIDI track Settings › Link, Tempo & MIDI: turn Track, Sync and Remote off for the input Drag it onto the audio track
FL Studio Options › Manage plugins › Find installed plugins; Channels › Add one Options › MIDI settings: select the input, click Disable An effect slot of the mixer insert
Reaper Preferences › Plug-ins › VST › Re-scan; Track › Insert virtual instrument Preferences › Audio › MIDI Devices: untick Enable input The track's FX button
Studio One Drag it from the Instruments tab Nothing: Studio One only opens devices you add under External Devices Inserts of the channel
Bitwig Studio Rescan in the Dashboard; add it from the browser Settings › Controllers: the interface must not be enabled as an input An effect on the audio track
Cakewalk Insert › Soft Synth Preferences › MIDI › Devices: untick the input The track's FX bin

These steps follow each program's own menus. So far the plug-in has been tried in Cubase only; if a step does not match your version, tell us through the report form.

If the DAW must keep the interface for other instruments, switch Connection to Through the DAW instead, and route in the DAW:

  1. MIDI track A (plug-in to MKS-70). Input: the plug-in's MIDI output. Output: the interface. Monitor on.
  2. MIDI track B (MKS-70 to plug-in). Input: the interface. Output: the plug-in. Monitor on.
  3. Cubase: in MIDI Port Setup untick the interface's input in In 'All MIDI Inputs'.

Messages through the DAW can be at most 256 bytes. Every MKS-70 block is smaller, so patches, tones and edits fit. Clock and other real-time bytes do not travel this road; the plug-in follows the DAW's transport instead and needs no clock from the unit.

To check the cable: play a note, then turn a knob or choose a patch on the unit's own panel. When the editor follows it, the replies arrive.

2 · Playing it

Set the instrument track's MIDI input to your keyboard or controller. Whatever you play there plays the MKS-70 on the channel you set, and so do notes drawn on the track, the arpeggiator and the step sequencer.

3 · Hearing it here (levels, analyser, Sampler)

The MKS-70's sound goes through your audio interface into the DAW, not through the plug-in, so the plug-in listens to it from the DAW. On the audio track that carries the MKS-70, add the effect Knobsmith MKS-70 Audio Tap as an insert. It changes nothing in the sound, and the level meters, the analyser, Render and the Sampler read it. The page says Receiving audio when it works.

Time and tempo

The arpeggiator, the step sequencer and the modulation matrix follow the DAW: its tempo, its song position, Play and Stop, and loops. Once the plug-in's window has been opened they keep running when you close it.

If something does not work

  • The plug-in is not in the list. Rescan; check the folder Knobsmith MKS-70.vst3 sits directly in C:\Program Files\Common Files\VST3\ and that you copied the whole folder.
  • It plays but does not answer when you select a patch. The unit's replies are not reaching the plug-in. Direct: free the interface's input in the DAW (see above). Through the DAW: check track B and that its Monitor button is on.
  • The meters and the analyser are empty. Add the Knobsmith MKS-70 Audio Tap effect on the audio track that carries the MKS-70 (the plug-in's DAW page shows Receiving audio when it works).
  • "Read timed out", or the display reads NO REPLY. The same cause. See Connecting for what a held port looks like.
  • The plug-in and the installed app together. One interface cannot be held by both. Go through the DAW, or use Release MIDI in the app.