Zebra 3 Beta Bug Reports

[jooster]

Forgive me if this has been reported already;
1. Selecting ENV2 for to modulate noise 1 source stays controlled by ENV1 even though the source reads ENV2.
2. Noice --> Modal with marimba selected doesn't sound anywhere near a marimba; lots of noise coming through. Selecting any other modal css does change the character of the sound somewhat but it's all mostly the same.
3. Moving Z3 between my two monitors sometimes leaves a large square section of the plugin flashing fast (as if the monitor is bad). I had this with Zebralette 3 quite often, seems less with Z3.
4. Opening any of my zebralette3 patch with z3 have wrong LFO settings. Actually the _visual_ settings seem correct but what I hear is much too slow. I know zebralette --> z patch behavior is being worked on, thought I would mention it.

macOS 15.6.1/M2 Studio/Logic Pro 11.2.2

[icaria36]

I have purchased a license (yay!) but I cannot import it. When I try, something goes wrong and I can only reload Zebra 3 and start again..

Bitwig beta 11 on Ubuntu 25.10 up to date.

1. Get a license card.
2. Add the Zebra 3 to a Bitwig instrument track.
3. Click the "Show plugin window" icon. The Zebra 3 UI renders without problems.
4. Click "Import a License Card". An Ubuntu dialog opens to let you select the folder and file.

However, the dialog doesn't respond to the mouse, and after a couple of seconds, another Ubuntu dialog appears: ""Bitwig Studio" is not responding." with the options "Force Quit" and "Wait".

In fact, at this point both Bitwig and Zebra 3 are still functional. For instance, if you press keys in your MIDI keyboard, the preset will sound normally, and if you turn mapped controls in Bitwig, the preset will respond correctly. But eventually Bitwig will also complain with a dialog: "Plug-in host is not responding" with the option "Terminate Plug-in Sandbox". When I click this button another dialog appears""Plug-in crashed!" with the option "Reload crashed plugins". Clicking this button leaves us to square zero.

I have tried bypassing the initial dialog and then clicking the u-he logo > Import a License Card. The result is the same.

Meanwhile, Zebra 3 just works normally in my setup. After trying all the 300 factory presets, the only crash I get is this one with the License Card.

Maybe the bug is not in Zebra 3 but somewhere else in the stack, but I thought about reporting it here because I have been able to activate other plugins before, including u-he's Repro using the traditional license code. It would be good to have another test with the Bitwig-Ubuntu combo to see if it can reproduced. In any case, I'm not in a rush to have this problem fixed.

[Urs]

Send email to support at u-he dot com - might take a day or two due to holidays, but they're usually clued in.

[icaria36]

I reported the problem and, in short, I got it working and it wasn't u-he's fault. Sharing the details here just in case they are useful to other Linux users.

u-he responded almost first thing this morning -- impressive. They gave me instructions to debug the problem.

The mouse input problem was something in my system (nvidia, multi-monitor setup, boring problems) that I could bypass by using another monitor (older, humbler specs).

Bitwig seems to "lose sight" of the plugin while the system dialog is open to navigate to the licnese card and select it. Bitwig report that the plugin as crashed or is unresponsive, but it's not true, the plugin is alive and kicking. Whether this is a Bitwig problem or a CLAP problem, I don't know, but definitely not a u-he problem.

After selecting the license card, Bitwig error message goes away, Zebra 3 is happy, and everything works as expected: Zebra 3 recognizes me as a user with a registered license and Bitwig is just a nice host. No crashes, no error messages, just musical enjoyment.

[ffx]

Happy new year to you!

I found this really awesome online wavetable generator: https://www.carvetoy.online/edit

I've tried to import some result table into Zebra 3, which kind of works. But I think it leaves out some samples or so, this is the original wavetable, it will sound very smooth sinoid like:

ct-wt-1767268173-unnamed_project-256-128-32.zip

If you import it into Zebra 3, there will be some overtones which arent in the waveform files, just like Zebra 3 is leaving out some sample(s) on the end or start, so the end and start point do not exactly match anymore.

I've compared the import with MSoundFactory, and here it clearly has no overtones, used this multiwaveform file (which does not work correctly at all with Zebra 3):

ct-wt-1767267962-unnamed_project-256-64-32.wav

So my assumption would be that something is wrong regards the detection of the single waveform length or so...? Maybe it is a known problem, just wanted to report it, so it's not missed.

[ffx]

Ah, maybe it's caused by the approximation, or optimization of points? cross point seems to be good.

[wpostma]

I guess I would have expected a new file extension for presets then?

[Urs]

I guess I would have expected a new file extension for presets then?

Why? - All our products use the same preset file format and extension.

[Q-Bass]

Hello.
I made one patch, that drops out after I re-opened a project with it in Bitwig after few days. When I was playing with it for the first time, it worked fine. It is for the first time this happened (out of maybe 10 patches/projects).
Because I only worked with the CLAP version so far, I tried to replace the instance with VST3 version and now it plays as intended. Maybe I dialed some strange combination of modulations. But it is not big/complicated patch. Anyway find it strange that it works in one format and not the other..
Here it is attached to check.

(Bitwig 5.1.9 - Windows 10 - CLAP vs. VST3)

[Sampleconstruct]

Is it a bug or a feature that the ModFX module outputs constant noise at around -75 dB (100% wet Flanger) and -80 dB (100% wet Chorus) when no signal is passing through? The phaser is clean/no noise output.

[Urs]

Is it a bug or a feature that the ModFX module outputs constant noise at around -75 dB (100% wet Flanger) and -80 dB (100% wet Chorus) when no signal is passing through? The phaser is clean/no noise output.

It's a feature of the analogue modes. No noise if you use digital, and there's a way to reduce the noise in a hidden parameter. Check out attached screenshot for a momentary workaround until we implement Constant and/or a separate control.

[Sampleconstruct]

Is it a bug or a feature that the ModFX module outputs constant noise at around -75 dB (100% wet Flanger) and -80 dB (100% wet Chorus) when no signal is passing through? The phaser is clean/no noise output.

It's a feature of the analogue modes. No noise if you use digital, and there's a way to reduce the noise in a hidden parameter. Check out attached screenshot for a momentary workaround until we implement Constant and/or a separate control.

Great, thanks.

[Freaqpeak]

VST3 crashing in Cubase 15 (Win11) after a minute of preset browsing.. Didn't try again after that but I'll prepare with log file (zebra3.log on Desktop?) next time I have time to sit in the studio..

[tasmaniandevil]

Didn't try again after that but I'll prepare with log file (zebra3.log on Desktop?) next time I have time to sit in the studio..

Just put a folder named u-he-log on your Desktop before you start Cubase.

It's that already known crash happening randomly while switching presets.
But since we have a hard time reproducing this particular issue on our machines, every bit of data is welcome.

[pummel]

Using 'osc filter' effect on a spectral saw sounds great, but causes the note loudness per key to decay along the keyboard the way the saw tooth fundamentals decay in magnitude -- loud at the low end, near zero at the high end. ( OCS page 'wave form plot' shows the correct cycle shape both c1 and c5. Adjusting 'key follow' makes a barely noticeable difference.