My Mantis just arrived.
Fantastic thing, I’ve been jamming all evening long yesterday. The sound is rather unpolished and full of character, so there will be a learning curve.
Anyone with experience on PWM Mantis Sysex implementatiion so far?
First draft on the preset. early works still. Not everything is tested.
Hi,
preset should be useable now. There are some (probably) bugs on the PWM side. I’ve informed them about it. These controls are now indicated in red in the preset.
Later on, I’ll add parsing.
2 Likes
PWM Mantis - with patch parsing
V1 by NewIgnis
- Synth must be on firmware V2 or above
What’s in the preset
- Various controls darken or are hidden when not in use
- All 15 waveforms, including the Oscar wavetables, are controlled with a single waveform control
- ‘Freeze LFO’ is not on the original synth. It allows the LFO to stop temporarily. Same as moving LFO rate full left.
- Patch parsing
Use of colors
- Green: controls found on the Mantis panel
- White: same as green, but controls volume levels
- Blue: same as green, but controls modulation or timing.
- Yellow: same as green, but for cutoff or controls, indicated by LED’s
- Grey: controls using Shift. Touch the button to see the synth’s shift command in the lower right corner.
- Controls in (brackets): control responds to parsing, but is not sending anything back yet to the Mantis
Still to come
- Adding the preset names of bank 1
- Test if we can store patch names in the Mantis
- Try out a third LFO
- Add an additional mod matrix via the E1
1 Like
For those interested to work with the Mantis SysEx (info from Ben Supper of PWM):
Requesting a patch dump:
F0 00 21 47 7E bank patch F7
where bank is 0 for A and 1 for B; patch is 00-63h (0-99).
Requesting the patch currently in memory:
F0 00 21 47 7E 7F 7F F7
Responses (patches generally) always start
F0 00 21 47 bank patch.
The rest, up to the terminal F7, is payload.
The patch Names , such as ‘\x00MantisP’ in ASCII is always in the first eight bytes.
The 8-bit memory space of Mantis is rendered transmissible in the standard MIDI 1.0 way: the first byte of every eight-byte group is the high bits for the next seven. (See the ‘FILE DUMP’ part of the MIDI 1.0 spec). So actually ‘\x00MantisP’ is just an encoding of the word ‘MantisP’ in the memory space. Then the next number is a patch version for future expansion − currently 1 − and then the parameters follow.
You can play back ‘7F 7F’ patches into the current patch memory. You can also load things into the save slots, which completely overrides bank protection, but you need to change the bank numbers to 70h or 71h (112 or 113 instead of 0 or 1) so you can’t easily do that by accident.
New Mantis preset with patch parsing, patch naming and extra modulation
V2
- Synth must be on firmware V2 or above
New in V2
- All factory patch names of bank A are shown, even though the Mantis doesn’t store them.
- Patch saving, where you can also rename a preset. By default the choice for bank A is hidden. A saved patch name will be recalled when recalling the patch and then temporarily stored on the E1.
- Additional modulation paths (not found on the Mantis) are in development, not ready yet
1 Like
New version 3 : now the Voice Spread and the filter Type behave like on the original Mantis
1 Like
Version 4 is ready. Electra One App
What it can do:
- controls all Mantis parameters
- combines all 15 waveforms in one parameter
- shows the shift-key combination for specific parameters
- adds a ‘freeze LFO’ option
- retrieves all parameter settings from the Mantis when recalling a patch
- shows the factory patch names (if unchanged)
- lets you save patches
- lets you name patches
- provides 10 more modulation paths, but these are not stored with the patches (2 destinations for modwheel, pitchbend, velocity, aftertouch and note number)
That preset is finished now 
4 Likes