Patch editor for the Alesis Midiverb III hardware FX unit.
Download the latest build for your OS. It may require some OS permissions to launch.
All the app settings and the default bank are stored at your home folder, inside .mverb3 hidden directory.
For advanced users: you can download the sources as Python package, install the dependencies with pip3 install -r pyproject.toml
and run python3 -m mverb3 with the same result. This should be a foolproof option if you have some compatibility problems
with the app.
Of course, you need a Midiverb III connected to your MIDI interface.
Go to File/Settings (midiverb3/Preferences on Mac) and set up your Midiverb ports and MIDI channel.
Go to Device/Request Bank and wait until the bank is loaded (~10s).
Ignore the next step you don't need to store programs on the device and only wish to edit the parameters of the current buffer / store them manually from the device.
Dump the same bank back to the device unless you set up the MIDI program id to Midiverb program id mapping table by yourself. The editor is organized in such a way that it maps all the editable presets to program numbers from 0 to 100. I.e. preset 100 becomes MIDI prog num 0, preset 101 becomes 1 etc...
NOTE: Midiverb III is an old artefact. To make the work process more smooth and to preserve the device memory the editor
doesn't send parameter changes to the device buffer automatically. So if you have loaded a program or bank what is not
stored on the device you have to manually send that program to the device buffer using SYNC button.
(However, when you edit particular parameters from the UI their values are synchronized instantly).
Select a program slot. Check that the device changed its program number on the LCD.
Edit some parameters. Check that the device noticed that (a dot should appear on the LCD).
Use File/Save Bank to save to the current bank on the computer or File/Export Program to export as a single
program SYX file. You can then load it to any other slot in any bank.
If you also want to store the edited parameters on the device itself, use Device/Store Program. It will be stored
to the currently selected program slot.
Create a new bank from the default template and open it. The action will NOT automatically sync the bank to the device.
Open a bank or a single program in the sysex format from a file. This way you can import banks and programs. The action will NOT automatically sync the bank to the device.
Save the current bank changes on the computer. The buffer is saved to the currently selected program slot. The action will NOT automatically sync the bank to the device.
Copy the current bank to another location on the computer. You can use this for backups. The action will NOT automatically sync the bank to the device.
Save a content of the buffer to a sysex file. Note that the program is stored with its current program id. The action will NOT automatically sync the bank to the device.
Copy the content of the buffer to the clipboard.
Paste the content of the buffer from the clipboard. You can use this to copy patches between the slots. This will automatically sync the buffer on the device but will NOT store in in the program slot.
Send the whole bank to the device. This operation may take up to 10 seconds. CAUTION: This operation will overwrite all the device data.
Request the whole bank from the device. CAUTION: This operation will overwrite all the bank data on the computer.
Input EQ which is actually a lowpass filter.
Select a chorus or flanger algorithm. Letters XS to XL indicate the depth of the effect. The slider indicates
the rate (speed) of the effect.
The delay parameters. The time is in milliseconds. Regen is the feedback level. Level indicates how much of the
delay is routed to the mix.
Decay is the reverb decay, Level indicates how much of the reverb is routed to the mix. ALGORITHM allows you to
select the reverb algorithm.
Another lowpass filter may be either delay or reverb feedback signal filter depending on the algorithm.
You can select the source and the destination for the MIDI modulation of one of the delay parameter (yes, only one). The modulation itself can be kinda glitchy, so I'd recommend limiting the rate of MIDI messages and use mono mode if using the note number or velocity modulation. The slider indicates the depth of the modulation.
Send current buffer (GUI values) to the device. To do this automatically on program switch you can set
Send buffer to device on prog change flag in the app settings. By default on program change the device retains its
stored program.
Discard the edit buffer and revert to the program stored in the local bank (not on the device).
Although not ideal, there's a certain notation for the internal routing in the algorithm select menu. You may try to get familiar with it or just tweak by ear.
LP- input lowpass filter (EQ in the manual)CHS- chorus or flangerDLY- standard delay up to 100msXDLY- extended delay up to 500msREV- reverb>- section routed to another, for exampleCHS > DLYmeans chorus routed to reverb( )- section is not mixed to the output bus, for example(LP)means that the lowpass filtered signal, although routed somewhere, is not directly mixed to the output. Note that both delay and reverb may be routed to the mix bus, but their level may be set to zero. The chorus doesn't have a separate level parameter, so it's eiter all or nothing.|- parallel routing, for exampleCHS > DLY | CHS > REVmeans chorus routed to the reverb and to the delay in parallel
Examples:
(LP) > CHS > DLY | (LP) > CHS > REV
Lowpass filter is routed to the chorus which routed to the delay. Also in parallel lowpass filter is routed to the chorus which is routed to the reverb. Lowpass filter is not mixed to the output.
(LP) > (CHS) > XDLY
Lowpass filter is routed to the chorus which is routed to the extended delay. Both the lowpass filter and the chorus are not routed to the mix bus, but delay is.
I don't have one, so I don't know.
The editor stores everything in the Midiverb III sysex format (programs and banks). Since Midiverb doesn't have program names, the names are stored separately in a text file. You should be able to load any Midiverb III sysex data into the editor without a problem.
There's no program bank feature on the Midiverb III, so the total number of selectable programs is limited to 127. Currently, I don't have a feature to manually map those slots from the editor, but it's planned for the future.
By default, the app is configured such way that it uses the internal memory as less as possible.
You can press Device/Store Program button to actually save the program in the selected program slot. Alternatively
you can store your banks / programs on the computer and use the SYNC button to load single patches into the current
device buffer only when you need them.
Try going to your user home folder, locate and delete .mverb3/settings.json file.
This should reset the app to its default settings.
Check that the program change option is enabled on your MidiVerb device.
To minimize the load on the device the sliders are designed to send their values only when you release the slider.
Click on a slider once and then use the arrow up/down keys to set the exact value.
Yes, there is some mandatory MIDI lag, which is recommended by the Midiverb III service manual. It's an old piece of gear after all.
Well, for old hardware with a 3 mips CPU it's kinda expected. I've noticed that the unit can handle certain modulations better than another. Note number modulation works much better for chorus speed than for delay time for example. You have to experiment.
Cheers.