| Name | midiverb3 JSON |
| Version |
1.0.2
JSON |
| download |
| home_page | None |
| Summary | Alesis MidiVerb III editor |
| upload_time | 2025-01-14 15:46:52 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | None |
| keywords |
reverb
music
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# MidiVerb 3
Patch editor for the [Alesis Midiverb III](https://www.vintagedigital.com.au/alesis-midiverb-iii/) hardware FX unit.
- [INSTALLATION](#Installation)
- [CONFIGURATION](#configuration)
- [USAGE](#usage)
- [MENU REFERENCE](#menu-reference)
- [PATCH REFERENCE](#patch-reference)
- [ROUTING](#routing)
- [MIDIVERB TIPS](#midiverb-tips)
- [TROUBLESHOOTING](#troubleshooting)
## Installation
Go to the [release page](https://github.com/violet-black/midiverb3/releases) and download the binary for your OS.
It may require permissions to access the user directory, since the app stores its settings in `.mverb3`
hidden folder inside the user directory.
Alternatively there's a [Python package](https://pypi.org/project/midiverb3/) available, which can be installed via
pip and run by executing `midiverb3` command in the terminal (or alternatively `python3 -m midiverb3`).
The app uses [pySide6](https://doc.qt.io/qtforpython-6/) Qt binding for the GUI.
## Configuration
1. Be sure that the MidiVerb is on and both MIDI in and MIDI out are plugged in.
2. Start the app, open `File/Settings` (or `midiverb3/Preferences` on Mac). Set MIDI in and MIDI out
to the MidiVerb ports. Click OK.
3. Go to `Device/Request Bank` menu. The MidiVerb will now dump its current bank to the app.
Then the bank will be sent back to the device. This operation may take up to 20 seconds. Once finished,
you won't need to do it again or even use the device MIDI output.
4. Try to switch programs from the app to verify that the device is reacting to it.
## Usage
The easiest way to work with the app is to tweak sliders in the UI, then click `File/Save Single` and save the buffer
to a sysex file. Once you need it again, you can `File/Open` it. This will also automatically send the data to
the MidiVerb buffer.
This type of workflow doesn't require either storing data in a bank or saving it to the device program memory.
Alternatively you can duplicate the current bank by using `File/Save As`. Go to the settings and click
`Send buffer to device on prog change` checkbox. Now you can work with your bank, change presets, and they will be
automatically sent to the MidiVerb buffer. I.e. the bank itself is stored entirely on your computer, but the sliders
and switches are synchronized with the device. This way you can manage multiple banks at once by switching them using
`File/Open`.
If you actually need to store programs on the device, use `Device/Store Program` or `Device/Store Bank`. MidiVerb 3
can store only one bank and 100 user programs (slots 100-199).
## Menu Reference
### File/New
Create a new bank from the default template and open it.
The action will NOT automatically sync the bank to the device.
### File/Open
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.
### File/Save
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.
### File/Save As
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.
### File/Save Single
Save a content of the buffer to a sysex file.
The action will NOT automatically sync the bank to the device.
### Device/Store Program
Store the current buffer in the selected program slot *in the device memory*.
### Device/Store Bank
Send the whole bank to the device. This operation may take up to 10 seconds.
CAUTION: This operation will overwrite all the device data.
### Device/Request Bank
Request the whole bank from the device.
CAUTION: This operation will overwrite all the bank data on the computer.
## Patch reference
### LPF
Input EQ which is actually a lowpass filter.
### CHORUS
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.
### DELAY
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.
### REVERB
`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.
### LPF
Another lowpass filter may be either delay or reverb feedback signal filter depending on the algorithm.
### MODULATION
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.
### SYNC
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.
### RECALL
Discard the edit buffer and revert to the program stored in the local bank (not on the device).
## Routing
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 flanger
- `DLY` - standard delay up to 100ms
- `XDLY` - extended delay up to 500ms
- `REV` - reverb
- `>` - section routed to another, for example `CHS > DLY` means *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 example `CHS > DLY | CHS > REV` means *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.*
## MidiVerb Tips
Route your piano or another keyboard to the delay input in your DAW and apply note number modulation to the delay time.
It will create 'random' glitchy echoes when played.
Alternatively try using negative reverb level / decay modulation on note velocity to create a glitchy 'compression' effect.
Use routing algorithms with extended delay (XDLY) to get delay time longer than 100ms.
Overload the input to produce ugly lo-fi digital distortion.
## Troubleshooting
### Will the app work with Midiverb I / II?
I don't have one, so I don't know. Probably it won't. I wouldn't recommend that.
### Unable to select programs below 100
This is intentional, because there's no way to edit factory programs anyways and there are only 127 possible MIDI program
numbers. On bank import the app will remap all program slots to presets 100-199
to be able to navigate between them using MIDI program change messages.
### Presets are not saved on the device
By default, the app is configured such way that it uses the internal memory as less as possible (who knows how many
writes it can withstand). The idea is that you load your device bank in the computer, and then you operate locally
only sending changes to the device buffer while you are using it.
You can press `Device/Store Program` button to actually save the program in the selected program slot.
### The app doesn't start anymore
Go to your user folder, locate and delete `mverb3/` directory. This will reset the app to its default settings.
### App doesn't switch programs etc
Check that the `program change` option is enabled on your MidiVerb unit.
### There's lag between switching programs or other operations
It's by design. The official MidiVerb service guide says that the device requires at least 40 ms in between messages.
It's a very old hardware after all, and midi processing speed is pretty limited, so some lags should be expected.
### The device produces pops / clicks when using MIDI modulators
Well, it's an old hardware with 3 MIPS CPU so what can you do? It's a miracle that it even works. For such values as
note number modulation or velocity modulation I'd suggest using mono note input. Note number modulation of the delay time
can provide quite interesting results when used carefully.
Cheers.
Raw data
{
"_id": null,
"home_page": null,
"name": "midiverb3",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "reverb, music",
"author": null,
"author_email": "violet-black <violetblackdev@gmail.com>",
"download_url": null,
"platform": null,
"description": "# MidiVerb 3\n\nPatch editor for the [Alesis Midiverb III](https://www.vintagedigital.com.au/alesis-midiverb-iii/) hardware FX unit.\n\n\n\n- [INSTALLATION](#Installation)\n- [CONFIGURATION](#configuration)\n- [USAGE](#usage)\n- [MENU REFERENCE](#menu-reference)\n- [PATCH REFERENCE](#patch-reference)\n- [ROUTING](#routing)\n- [MIDIVERB TIPS](#midiverb-tips)\n- [TROUBLESHOOTING](#troubleshooting)\n\n## Installation\n\nGo to the [release page](https://github.com/violet-black/midiverb3/releases) and download the binary for your OS.\n\nIt may require permissions to access the user directory, since the app stores its settings in `.mverb3`\nhidden folder inside the user directory.\n\nAlternatively there's a [Python package](https://pypi.org/project/midiverb3/) available, which can be installed via\npip and run by executing `midiverb3` command in the terminal (or alternatively `python3 -m midiverb3`).\nThe app uses [pySide6](https://doc.qt.io/qtforpython-6/) Qt binding for the GUI.\n\n## Configuration\n\n1. Be sure that the MidiVerb is on and both MIDI in and MIDI out are plugged in.\n\n2. Start the app, open `File/Settings` (or `midiverb3/Preferences` on Mac). Set MIDI in and MIDI out\n to the MidiVerb ports. Click OK.\n\n3. Go to `Device/Request Bank` menu. The MidiVerb will now dump its current bank to the app.\n Then the bank will be sent back to the device. This operation may take up to 20 seconds. Once finished,\n you won't need to do it again or even use the device MIDI output.\n\n4. Try to switch programs from the app to verify that the device is reacting to it.\n\n## Usage\n\nThe easiest way to work with the app is to tweak sliders in the UI, then click `File/Save Single` and save the buffer\nto a sysex file. Once you need it again, you can `File/Open` it. This will also automatically send the data to\nthe MidiVerb buffer.\n\nThis type of workflow doesn't require either storing data in a bank or saving it to the device program memory.\n\nAlternatively you can duplicate the current bank by using `File/Save As`. Go to the settings and click\n`Send buffer to device on prog change` checkbox. Now you can work with your bank, change presets, and they will be\nautomatically sent to the MidiVerb buffer. I.e. the bank itself is stored entirely on your computer, but the sliders\nand switches are synchronized with the device. This way you can manage multiple banks at once by switching them using\n`File/Open`.\n\nIf you actually need to store programs on the device, use `Device/Store Program` or `Device/Store Bank`. MidiVerb 3\ncan store only one bank and 100 user programs (slots 100-199).\n\n## Menu Reference\n\n### File/New\n\nCreate a new bank from the default template and open it.\nThe action will NOT automatically sync the bank to the device.\n\n### File/Open\n\nOpen a bank or a single program in the sysex format from a file. This way you can import banks and programs.\nThe action will NOT automatically sync the bank to the device.\n\n### File/Save\n\nSave the current bank changes on the computer. The buffer is saved to the currently selected program slot.\nThe action will NOT automatically sync the bank to the device.\n\n### File/Save As\n\nCopy the current bank to another location on the computer. You can use this for backups.\nThe action will NOT automatically sync the bank to the device.\n\n### File/Save Single\n\nSave a content of the buffer to a sysex file.\nThe action will NOT automatically sync the bank to the device.\n\n### Device/Store Program\n\nStore the current buffer in the selected program slot *in the device memory*. \n\n### Device/Store Bank\n\nSend the whole bank to the device. This operation may take up to 10 seconds.\nCAUTION: This operation will overwrite all the device data.\n\n### Device/Request Bank\n\nRequest the whole bank from the device.\nCAUTION: This operation will overwrite all the bank data on the computer.\n\n## Patch reference\n\n### LPF\n\nInput EQ which is actually a lowpass filter.\n\n### CHORUS\n\nSelect a chorus or flanger algorithm. Letters `XS` to `XL` indicate the depth of the effect. The slider indicates\nthe rate (speed) of the effect.\n\n### DELAY\n\nThe delay parameters. The `time` is in milliseconds. `Regen` is the feedback level. `Level` indicates how much of the\ndelay is routed to the mix.\n\n### REVERB\n\n`Decay` is the reverb decay, `Level` indicates how much of the reverb is routed to the mix. `ALGORITHM` allows you to\nselect the reverb algorithm.\n\n### LPF\n\nAnother lowpass filter may be either delay or reverb feedback signal filter depending on the algorithm.\n\n### MODULATION\n\nYou can select the source and the destination for the MIDI modulation of one of the delay parameter (yes, only one).\nThe modulation itself can be kinda glitchy, so I'd recommend limiting the rate of MIDI messages and use mono mode\nif using the note number or velocity modulation. The slider indicates the depth of the modulation.\n\n### SYNC\n\nSend current buffer (GUI values) to the device. To do this automatically on program switch you can set\n`Send buffer to device on prog change` flag in the app settings. By default on program change the device retains its\nstored program.\n\n### RECALL\n\nDiscard the edit buffer and revert to the program stored in the local bank (not on the device).\n\n## Routing\n\nAlthough not ideal, there's a certain notation for the internal routing in the algorithm select menu. You may try to\nget familiar with it or just tweak by ear.\n\n- `LP` - input lowpass filter (*EQ* in the manual)\n- `CHS` - chorus or flanger\n- `DLY` - standard delay up to 100ms\n- `XDLY` - extended delay up to 500ms\n- `REV` - reverb\n- `>` - section routed to another, for example `CHS > DLY` means *chorus routed to reverb*\n- `( )` - section is not mixed to the output bus, for example `(LP)` means that the lowpass filtered signal,\n although routed somewhere, is not *directly* mixed to the output. Note that both delay and reverb may be routed to\n the mix bus, but their level may be set to zero. The chorus doesn't have a separate level parameter, so it's eiter\n all or nothing.\n- `|` - parallel routing, for example `CHS > DLY | CHS > REV` means *chorus routed to the reverb and to the delay in parallel*\n\nExamples:\n\n`(LP) > CHS > DLY | (LP) > CHS > REV`\n\n*Lowpass filter is routed to the chorus which routed to the delay. Also in parallel lowpass filter is routed to the chorus\nwhich is routed to the reverb. Lowpass filter is not mixed to the output.*\n\n`(LP) > (CHS) > XDLY`\n\n*Lowpass filter is routed to the chorus which is routed to the extended delay.\nBoth the lowpass filter and the chorus are not routed to the mix bus, but delay is.*\n\n## MidiVerb Tips\n\nRoute your piano or another keyboard to the delay input in your DAW and apply note number modulation to the delay time.\nIt will create 'random' glitchy echoes when played.\n\nAlternatively try using negative reverb level / decay modulation on note velocity to create a glitchy 'compression' effect.\n\nUse routing algorithms with extended delay (XDLY) to get delay time longer than 100ms.\n\nOverload the input to produce ugly lo-fi digital distortion.\n\n## Troubleshooting\n\n### Will the app work with Midiverb I / II?\n\nI don't have one, so I don't know. Probably it won't. I wouldn't recommend that.\n\n### Unable to select programs below 100\n\nThis is intentional, because there's no way to edit factory programs anyways and there are only 127 possible MIDI program\nnumbers. On bank import the app will remap all program slots to presets 100-199\nto be able to navigate between them using MIDI program change messages.\n\n### Presets are not saved on the device\n\nBy default, the app is configured such way that it uses the internal memory as less as possible (who knows how many\nwrites it can withstand). The idea is that you load your device bank in the computer, and then you operate locally\nonly sending changes to the device buffer while you are using it.\n\nYou can press `Device/Store Program` button to actually save the program in the selected program slot.\n\n### The app doesn't start anymore\n\nGo to your user folder, locate and delete `mverb3/` directory. This will reset the app to its default settings.\n\n### App doesn't switch programs etc\n\nCheck that the `program change` option is enabled on your MidiVerb unit.\n\n### There's lag between switching programs or other operations\n\nIt's by design. The official MidiVerb service guide says that the device requires at least 40 ms in between messages.\nIt's a very old hardware after all, and midi processing speed is pretty limited, so some lags should be expected.\n\n### The device produces pops / clicks when using MIDI modulators\n\nWell, it's an old hardware with 3 MIPS CPU so what can you do? It's a miracle that it even works. For such values as\nnote number modulation or velocity modulation I'd suggest using mono note input. Note number modulation of the delay time\ncan provide quite interesting results when used carefully.\n\nCheers.\n",
"bugtrack_url": null,
"license": null,
"summary": "Alesis MidiVerb III editor",
"version": "1.0.2",
"project_urls": {
"Homepage": "https://github.com/violet-black/midiverb3"
},
"split_keywords": [
"reverb",
" music"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "c592709f69a956b730ec6a00407e10e7244909dbc34ba478e2f56f9292d5cb66",
"md5": "b4754f85a54b70935aa04951f636a8e3",
"sha256": "56b1c8e600d245563a001ecbef099aaa3308848073c549bdecaa974ded100e4d"
},
"downloads": -1,
"filename": "midiverb3-1.0.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "b4754f85a54b70935aa04951f636a8e3",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 22866,
"upload_time": "2025-01-14T15:46:52",
"upload_time_iso_8601": "2025-01-14T15:46:52.116142Z",
"url": "https://files.pythonhosted.org/packages/c5/92/709f69a956b730ec6a00407e10e7244909dbc34ba478e2f56f9292d5cb66/midiverb3-1.0.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-01-14 15:46:52",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "violet-black",
"github_project": "midiverb3",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "midiverb3"
}
