WaveEdit 1.2 Release – Editor Waldorf MicroWave 1 using Win, Mac, VST

Relase 1.2 of the SysEx Editor for the original Waldorf MicroWave (so-called version 1) synthesizer delivers some bugfixes and enhancements, like:

– midi in and out LEDs
– you can play a note from the virtual keyboard with an endless echo / loop (standard edition)
– last used sound library files are opened automatically (standard edition)

Screenshot - WaveEdit 1.2 Windows VST in Bitwig Studio
WaveEdit 1.2 Windows VST in Bitwig Studio

Once again, there is a fully working free edition availlable, without some advanced ffeatures and running within limited time after release.

All version use the same installer you can download here, paid standard license is availlable here.

One installer for each plattform (Windows, MacOS) includes standalone and vst, 32 and 64 bit version.

WaveEdit 1.1 Release – Windows, MacOS, VST in&out

The new version of the Waldorf MicroWave 1 Sound Editor supports additional plattforms:

Apple Mac OS-X, starting 10.7, both as standalone app or VST plug-in

VST hosts, that block Midi SysEx data, e.g. Ableton Live

Waveedit 1.1.0 Standard Edition VST OS-X

All version use the same installer you can download here, paid standard license is availlable here.

Using free edition in standalone, you need to send a preset to your device by clicking the send button, in order to listen to all your changes done before, and you can’t rename presets. Free edition in VST mode allows you to test connectivity only.

WaveEdit 1.1.0 Free Edition OS-X
WaveEdit 1.1.0 Free Edition OS-X

Using standard license, in addition to real-time and preset name editing and full VST support, you can store your single sounds in multiple library banks (each with 64 sounds). They get stored in a separate file, compatible wih the original bank dump sysex format. You can import single or bank dump sysex files and send them to your MicroWave. You can send and receive whole sound banks, and have midi thru.

WaveEdit 1.1.0 Standard Edition Windows

For initial setup have a look at Setup And Connect Your Device.

Have fun!

WaveEdit 1.0 Release – the Waldorf MicroWave 1 Sound Editor

Finally the Waldorf MicroWave 1 Sound Editor made it to version 1.0!

WaveEdit now does automatically request sound programs on connect or program change (standalone or standard license) and automatically sends all sounds edits real-time (standard license). An LED light indicates Midi SysEx input.

The UI size is sligthly smaller (1440*720), buttons were rearranged to make that user’s demand possible.

WaveEdit 1.0 Standalone - the Waldorf MicroWave 1 Sound EditorWaveEdit 1.0 Standalone

The VST version got the same changes. The VST version comes with an enhanced own midi out port, so you can use any VST host, wether ist supports midi out from VST with system exclusive messages or not. Standalone and VST are availlable both in 32 and 64 bit. All version use the same installer you can download here, paid standard license is availlable here.

WaveEdit 1.0 in Cubase
WaveEdit 1.0 in Cubase – the Waldorf MicroWave 1 Sound Editor VST

Using free edition in standalone, you need to send a preset to your device by clicking the send button, in order to listen to all your changes done before. Free edition in VST mode allows you to test connectivity only.

Using standard license, in addition to real-time editing and full VST support, you can store your single sounds in multiple library banks (each with 64 sounds). They get stored in a separate file, compatible wih the original bank dump sysex format. You can import single or bank dump sysex files and send them to your MicroWave. You can send and receive whole sound banks, and have midi thru.

For initial setup have a look at Setup And Connect Your Device.

Have fun!

Setup And Connect Your Device

How to start the editor, setup and connect your device?

Device Settings and Cabling

You should set your device id to the default (the first or any) and set the midi channel of your device to 1 or omni. Your MicroWave should be in single mode.

You need to cable the midi out of your device to a midi in port of your pc, and a midi out port of your pc to the midi in of your device.

Run the App

You can start the appliccation (.exe / app) directly. The vst plugin-in should be availlable in your plugin host. If not, you may have to add the install path to your vst2 directories.

If you have any connection problems, you should try the standalone app first.

Midi Settings – Standalone

Go to the File Menu, Preferences, and choose your midi in and out interface and port that you did connect to your device.

filemenu

midisettings

After that, turn midi on with the red button on the panel

midiout

If you’re getting an error message now, you’re midi port is technically not accessible (e.g. used by an other application).

In all other cases you should now see the message above the sound name display changing to “Connected” or telling you details about your device.

message0

message

The first sound program will be loaded automatically as well.

Midi Settings – VST

When running the program as a VST plugin, you can either use the midi out configured in your VST host application, or directly access a midi out port in the plugin. Not all VST host applications support midi sysex data running through a midi out port (e.g. Reaper supports this, Cubase doesn’t). So if host midi out may not work for you, simply have a look than at the chapter “Direct Midi In or Out”.

Midi in of the VST host ist always connected and the 1st midi in – this is useful for playing notes (on your keyboard or from your sequencer), with midi thru on, they get passed on to midi out. For VST host that block midi sysex data (e.g. Live). you can use a 2nd, direct midi in as decribed in “Direct Midi In or Out”!

Host Midi In

The following screenshots are from Reaper, but are similar to most DAWs.

You need to create a new a virtual instrument track and choose the plugin:

reapertrack

The midi in port can be choosen as you you would usually do it in your DAW, in the track settings. It is OK to choose “All” as in, so you can connect both, the midi out of your device and e.g. a midi keyboard simultanously (you may want to enable the plugin’s midi thru as well then):

reapermidiin

Host Midi Out

Not all DAWs support this.

In Reaper, Click on the “Route” symbol of the track.

reapertrackroute

And choose the midi out port that is connected to your device:

reapermidiout

After that, you switch midi out port “on” on the plugin’s panel. Don’t touch the “toggle” button. Or click it repeatedly until “Set in host” is your plugin’s midi out port.

midiouttoggle

Done!

Direct Midi In or Out

The following examples are from Cubase, but should be similar to most DAWs.

You shouldn’t use the same midi in or out port both in your plugin direct in/out and in your VST host. So, first disable the midi in or out port that is connected to your device in your VST host. In Cubase go Devices -> Device Setup and set the corresponding port not beeing “visible”.

devicesetup

You may have to restart your DAW. After that, click repeatedly on the Toggle button in your plugin, until you see the right port name above it (to distinguish similar names, there is also the nunber of the physical out attached to the name).

There is a on/off and a toggle button for both, 2nd midi in and midi out.

When toggling to an accessible port, “Midi On” gets activated automatically. When toggling to a technically inaccessible port, you will see this getting inactive.

You should see the device connecting within seconds, after both in and out port have been set. If not, there may be a filtering issue. See next Chapter.

Disabling SysEx Filter

A lot of VST hosts filter or disable midi sysex messages. For the midi out, we just forget about that and use the plugin’s direct midi out. For midi in, in most cases we just have to find the filter settings and switch them off. In Cubase, go File -> Preferences -> Midi -> Midi Filter and unset the SysEx checkbox for “Record”.

preferences

Enabling Midi Thru (Standard License)

You may want to play notes with your Midi keyboard (and not only the virtual keyboard within the plugin) and edit parameters simultanously. Or you may (of course) want to play back midi notes from your sequencer track to your device within the same session, while you work on parameters. In that cases, you already have multiple midi inputs merged (in your VST host or somehow in hard/software) and need to enable midi thru within the plugin:

thru

All notes played and sent to the plugin’s midi in will then be sent through to the plugin’s midi out and to your device. But no sysex data will be sent through (it is filtered out from thru, otherwise you would risk a message loop).