本文へスキップ
Knobsmith
メニュー

このページは英語です。

Firmware

The MKS-70 accepts edits differently depending on which ROM is fitted. The app cannot detect the ROM, so you tell it which one you have.

Choosing the setting

The app asks on first launch. To change it later:

  1. Open Settings (the gear icon) and choose the Instrument tab.
  2. Under Firmware ROM, set Fitted ROM to Original Roland, Vecoven 3.x or Vecoven 4.x.

The header display shows the current setting: ORIGINAL ROM, VECOVEN 3 or VECOVEN 4.

If you are not sure which ROM is fitted, choose Original Roland. Every unit accepts it, including units with Vecoven firmware.

How edits are sent

Setting How an edit reaches the unit
Original Roland A complete patch or tone block (All Parameters, APR) for every change.
Vecoven 3.x One parameter per message (Individual Parameter, IPR), sent the moment you move a control.
Vecoven 4.x As 3.x, plus five parameters that only 4.x has.

Original Roland ROM

The original ROM ignores single-parameter messages when it receives them. It acts only on whole blocks, so the app sends the whole patch block or tone block each time you move a control.

The app builds that block from what the unit sent it. That has two consequences:

  • Read the patch first. Until the unit has sent its current patch, the app has no block to edit and edits are not sent. Select a patch in the Patch Browser, or use Read from unit in Settings → Instrument. If you push a sound before that, the app reports how many parameters reached the unit and tells you to read first.
  • Tones the app has not seen are held. When you select a different stored tone for a half, the original ROM loads it without sending it back. The app uses its own copy of that tone if it has seen it before, from an earlier patch or a bank scan. If it has not, the Tones panel shows TONE NOT READ for that half and holds back edits to it, so an edit cannot put the previous tone back. Select a patch that uses the tone, or scan the bank, to fill it in.

Because every change is a whole block, each edit is larger on the MIDI cable. This matters most for the modulation matrix and sequencer lanes, which send many edits a second. The bus meter in the Modulation window takes the firmware into account. See Modulation.

Vecoven 3.x and 4.x

Vecoven firmware accepts a single parameter per message. Each control sends only its own parameter, as you move it.

What Vecoven 4.x adds

Vecoven 4.x has five tone parameters that the original ROM and Vecoven 3.x do not:

Control Range
DCO1 PWM 0 to 127
DCO2 PWM 0 to 127
LFO Fine (LFO Rate Fine) 0 to 127
KF Fine (VCF Key-Follow Fine) 0 to 127
LFO Phase (LFO Phase Reset) Off, On Note, On Trig, Always

They appear in the Vecoven 4.x · PWM section of the panel only when the setting is Vecoven 4.x. Under any other setting that section explains where to change the setting, and the app never sends these addresses, from the panel, a stored sound, an import or the modulation matrix.

Choosing the wrong setting

You choose Your unit has What happens
Vecoven 3.x or 4.x Original Roland ROM Controls move on screen and the sound does not change.
Vecoven 4.x Vecoven 3.x The five 4.x controls appear and do nothing. Everything else works.
Original Roland Vecoven 3.x or 4.x Everything works. Each edit sends a whole block instead of one parameter, and the five 4.x controls are hidden.

Portamento

The Porta switch and Porta Time knob in the Chorus · Glide panel work on every setting, but they write different bytes:

  • Original Roland: the switch turns on the Porta switch of both halves and sets the time. The patch-level portamento byte is left alone.
  • Vecoven: the switch sets the patch-level portamento byte and the time together.

Moving Porta Time above 0 switches portamento on; setting it to 0 switches it off. The MKS-70 glides only between notes that overlap, so a staccato line has no glide whatever the setting.

What the app does not do

  • It does not install or update firmware on the MKS-70.
  • It does not use NRPN. All editing is by SysEx.