Zebra 3 Beta Bug Reports

[colibri]

Apologies if I missed it, but loading my all-new Z3 license card in the current beta doesn't save. Restarting DAW (C15, Win11) it again reads 'registered to beta tester'. Admin mode has no effect.

[Urs]

Apologies if I missed it, but loading my all-new Z3 license card in the current beta doesn't save. Restarting DAW (C15, Win11) it again reads 'registered to beta tester'. Admin mode has no effect.

That's a known issue, it'll automatically resolve with the release (which invalidates the beta license).

You can fix it now by deleting the beta license card (maybe contact our support to get a detailed description on how to do this).

[MacGyver]

I think there are some memory leaks in Zebra 3 beta, at least after some time (like hours in idle), Bitwig is getting unstable and freezes. Might be worth a look.

[PieBerger]

You are probably already aware but just in case you're not:

On p46 of the manual under Demonstration there is reference to a preset 'Ploppsies' which is used as an example to explain the Ease In/Out function of Morph Vectors. 'Ploppsies' doesn't exist as a factory patch nor an Osc preset.

[ffx]

System: macOS 15.7, Zebra 3 beta 2 20549, Bitwig:

Bug:
Disabling/enabling a fx grid module with more than one input will stop/reset MSEG / note playing.

Expected:
Replaying should continue normally

Steps to reproduce:
1. Load preset "Detroit Exploit", add a midi clip with a sustained note, so it replays the preset. Loop that.
2. Now switch on/off "Comp 1" in the out fx chain. Audio output stops, until next note is reached.

Maybe this is not a bug per-se, but could then be improved. Is there really a technical reason to stop replaying in the above scenario?

[Funkybot's Evil Twin]

Zebra Rev 20552, CLAP, Win x64, Reaper

Weird glitches with the Avalanche preset (NaN's?).

TO reproduce:

1. Load Zebra3 on a new track in Reaper - empty project
2. Go to the Preset Browser > Public Beta COllection
3. Load the Avalanche preset
4. Play some sustained, single, bass notes

Result: weird random pops and glitches. CPU meter shows about 15% of a single core, so nothing's spiking.

[Funkybot's Evil Twin]

Zebra Rev 20552, CLAP, Win x64, Reaper

Glitches/spikes when changing presets.

To reproduce:

1. Load Zebra3 on a new track in Reaper - empty project
2. Go to the Preset Browser > Public Beta COllection
3. Load some presets while playing

Result: weird random pops and glitches, meters showing clipped peaks in Reaper.

I've seen that with other plugins, but don't recall it standing out as an issue on any U-he synths. Didn't see it in the release notes.

[Funky40]

Crashing !

latest Zebra 3 Beta update.
Host: GigPerformer (latest) / M4 Mac, Sequoia 15.3
Cause:
i have "open GUI/Plugin" CC mapped to a HW button. So i might open/close it several times per jam.
Closing the GUI has caused now several times a crash



please check Zebra 3 vs. GigPerformer while developing.
it´s the best live- play host out there. (everybody who found its way to GP says same)


And: Thanks for the new Beta !

[joradn]

Revision 20552, AU/VST3, Live 12.3, MacOS Tahoe

Set a modulator to a parameter, right click on parameter and remove modulation. Green dot stays on parameter and depth can be adjusted, despite no modulation. Only a visual bug and fixes itself upon clicking on a modulator.

See detune knob on oscillator:

[tasmaniandevil]

Maybe this is not a bug per-se, but could then be improved. Is there really a technical reason to stop replaying in the above scenario?

The compressor adds some latency, so the host needs to compensate for that, thus the sound cuts out when you activate or deactivate it.

[jrgillam]

Spectral decay osc FX isn't being "retriggered" by env 1 when the envelope is triggered by LFO 1. Env 1 is modulating other parameters as expected. Not sure if this is intended behavior or but it seems unexpected to me. See example preset, made with beta 20552.

[PieBerger]

Revision 20552, AU/VST3, Live 12.3, MacOS Tahoe

Set a modulator to a parameter, right click on parameter and remove modulation. Green dot stays on parameter and depth can be adjusted, despite no modulation. Only a visual bug and fixes itself upon clicking on a modulator.

See detune knob on oscillator:

Same with Rev 20552 VST3 on Win11 in Plugin Buddy

Edit: dragging and dropping from the matrix or the lower source bar to assign modulation, results in the same behaviour. The dot and bar remain, even after initialising a patch.

[tasmaniandevil]

Weird glitches with the Avalanche preset (NaN's?).

Yup, can reproduce this over here.
Might be a voice initialization issue in the filter module, as those glitches vanish after playing the preset for a while.

[tasmaniandevil]

dragging and dropping from the matrix or the lower source bar to assign modulation, results in the same behaviour. The dot and bar remain, even after initialising a patch.

Yep, we can reproduce this.

[tasmaniandevil]

3. Load some presets while playing

Result: weird random pops and glitches, meters showing clipped peaks in Reaper.

I cannot reproduce any strange clicks or glitches while switching presets and playing notes, using the CLAP version in Reaper. Neither on Mac nor on Windows.

Which sample rate and buffer size are you using in Reaper?