with Zebra 3 finally out in the wild, you might occasionally stumble over some leftover lasagna quirks or bugs. In the last weeks and months, we’ve been working tirelessly to fix as many of the remaining quirks as possible, but a day is still limited to a meagre 24 hours.
We will, of course, continue to iron out the remaining issues over time. There might also be some things we overlooked. Let’s use this thread as an overview and as a space to collect any additional issues you find while playing with Zebra 3.
Please feel free to post any reproducible quirks and bugs which are not listed in the first post of this thread yet. We’ll update the list with any confirmed issues, so you don’t need to scroll through the whole thread.
Automation
- Parameter automation in projects created using the Zebra 3 beta versions will be partly broken, as we had to adjust the automation list multiple times.
Curve Editor
- Importing .wav files is an experimental feature. Importing large files might temporarily freeze the plugin or even lead to a crash. We decided to keep the feature nonetheless, since it can be useful, e.g. when importing small files or single cycle waveforms. We’ll revisit the feature for an update.
- Drag & dropping .wav files from a host’s internal media manager to the plugin will not work in all hosts (e.g. Tracktion Waveform). Drag the files from your system’s file manager instead.
- Guide curves 2 and 3 are not saved for MSEG 2 to 4.
- On Linux, the mouse cursor icons are not working yet.
- The X/Y grid constraints cannot be changed in the small OSC editor.
- The MSEG editor grid numbers will disappear if the grid is too large.
- The Listen button does not switch off when a new preset is loaded.
- Creating and instantly dragging a point while holding the Option/Alt key won't work, as Alt-drag is used to expand the current selection.
- Using the Handle Rotate function can lead to visual glitches.
- The first segment sometimes isn’t altered when using Sine-O-Matic.
- The Warp tool can sometimes act erratically.
- Selecting curve slots can accidentally move them on the timeline. (added 2026-04-29)
- Entering value strings on the keyboard will not work correctly for some parameters. Key Control is a work in progress feature. We’ll continue to improve this in subsequent updates.
- If you’re having trouble with accidental parameter changes, a new preference lets you decide if you want to use the scroll wheel purely for scrolling racks, or if you want to use it for parameter adjustments too.
- Rack scrolling currently won’t work if the cursor hovers directly next to a parameter, as the area belongs to the parameter’s modulation depth control.
- This is also the reason why the key control frame looks off-center if there is no modulation assigned to a parameter.
- There is a rare quirk that causes the rack to scroll to the top during certain mouse actions, e.g. when expanding the FMO module or clicking the EQ display. We have not found a way to reproduce this yet.
- On Windows, using Backspace to delete modules from the grid does not work.
- Switching GUI themes requires to close and reopen the GUI in order to load all elements correctly.
- Rapid mouse movements in opposite directions can momentarily stall a parameter.
- In the OSC FX section, the Window effect’s Polarity parameter has a wrong label and click-method (drop-down instead of alternating) on OSC 2-4.
- In Bitwig, when loading our init preset using the CLAP version, remnants of the previously loaded preset might remain. This is a bug introduced with their new Undo system in Bitwig 5.3. Please contact Bitwig and ask them to look into this (we, of course, reported this, too).
- In Studio One (both the Presonus and the Fender versions), sending polyphonic Aftertouch values will crash the CLAP version. This is an issue in Studio One’s CLAP implementation.
- In Digital Performer, the VST3 version will fail the plugin verification scan. We are not sure if it’s on their side or if it’s something we can fix.
- In Ableton Live, if the Hide Mouse on Drag preference is used, the cursor will reappear if a key is pressed while dragging the mouse.
- We see MIDI controllers, like Mod Wheel and Ctrl A-D, primarily as a tool for live performances. Their settings are currently not stored within presets or host projects.
- MIDI program changes will not work in Cubase or Nuendo. In the past, we had deactivated this feature for Steinberg hosts, due to a bug in Cubase that could lead to projects reloading the wrong presets. We might reenable this feature in a future update.
- When using the MPE pitch-sliding feature with the CLAP version in Bitwig, repeatedly playing the same note after using the slide introduces a very short glitch at the start of the note. Only happens in Bitwig, not in Reaper. Use the VST3 version as a temporary workaround. (added 2026-04-22)
- CLAP modulation of Ctrl A-D in Bitwig not working as expected. (added 2026-04-22)
- There is no multicore support yet. Before implementing this, we first want to find a way to deal with modern, asymmetric CPU structures, e.g. Apple silicon chips with their mix of performance and efficiency cores, which can lead to perceived performance issues.
- Dialog windows (registration, preset saving) will appear brighter than usual in Logic Pro. Apple acknowledged it’s a bug introduced by macOS Tahoe.
- On Linux, we do not support drag & drop yet. We recently made some baby steps in the right direction, though.
- In Pro Tools, the Mod Wheel won’t show up if it’s assigned to a slot. The modulation depth slider will stay invisible as well. This is a visual bug, the assignment still works and you can set the modulation depth.
- In Pro Tools, assigning the Mod Wheel to a direct modulation slot, i.e. directly beneath a parameter instead of the mod matrix, one cannot set the modulation depth, as clicking the mod depth parameter opens the modulation source list. To set the modulation depth, switch to any other mod source, e.g. to Constant, set the depth, then switch back to the Mod Wheel.
- Right-clicking a direct modulation slot’s depth parameter will display the list of modulation sources. The list is not sorted correctly.
- After assigning the Ctrl A-D parameters to modulation targets, the colour coding of the modulation depth parameter sometimes switches to blue.
- After deleting a direct modulation source, the modulation depth ring will still be visible. Set the modulation depth to zero before deleting the source to avoid this.
- The Target Finder won’t find assignments that are not visible on the GUI.
- The Target Finder’s context menu does not show sources that are used as Trigger Source in modules or as Via source in the mod matrix.
- Sometimes, adjusting a modulation depth control next to the target parameter will not display the values. When this happens, adjust the depth in the mod matrix to fix it.
- After deleting a mod slot, the mod depth sliders can control the wrong parameter (visual glitch). (added 2026-04-29)
- A rare glitch in the Filter module can lead to the preset falling silent. You might have to reload the plugin to get the sound back.
- On Linux, the Modal Resonator’s partial display has drawing issues.
- The Burn module to test CPU performance has been removed. We plan to add this to the Module Performance Meter.
- Currently, curve sets are saved within the OSC and MSEG module presets. We’ll add an option to save the pure curve sets with an update.
- Currently, all module presets are displayed in a dropdown list. We’ll figure out which modules would benefit from a dedicated module preset browser and add this later on.
- Zebra 2 presets are not compatible with Zebra 3. We are keeping Zebra Legacy alive in parallel to Zebra 3.
- The Showcase presets will show up even if the Showcase smart folder has been added to the hidden folders.
- Importing presets from Zebralette 3 into Zebra 3 does not work perfectly yet. We’ll improve this, but a few parameters, such as the reverb and delay settings, cannot be translated perfectly.
- Preset loading can be slower when using an odd-numbered GUI size (e.g. 130% or 170%).
- Switching to a different curve slot and then using Undo and Redo can switch the waveforms of the two slots.
