Zebra 3.0.2 Update (rev. 22175)

[sl23]

I'm also wondering if removing those roundy ends from scrollbars altogether would make them look more modern.

don't you mean, more retro!

[johnnyberrygoode]

I even completely reinstalled zebra. The problem still exists.

Yes, I noticed that the issue is back in the current 3.0.2 release version. We had fixed this right after you mentioned it the first time and it was fine, this was all tested and verified as fixed. There must have been a later commit which accidentally reverted this fix.

Will you fix it in the next big patch or sometime soon? I just want to know if I should expect a patch in the near future.

[Urs]

We'll certainly fix it in the next release, but I'm afraid that won't happen in the near future. We can't really justify a full rollout of a new version for what I consider minor UI errors ("Bipolar" isn't so far off from "Polarity", it isn't as if the label makes the software unusable). However, we'd be happy to provide a modified script file for those who are bothered by it, maybe some time after the summer holiday season.

[Zakast]

Hello, thank you for update, but there are some issues that have not been fixed in the zebra3 3.0.2 version.
1. In the oscillator effects, in the "Window" effect, the first oscillator says "polarity", but in oscillators 2-4 it says "bipolar".

You can:

1. Make a copy of the "Zebra3_orig.txt" file somewhere, just in case
2. Make sure Zebra3 is not being used by your DAW
3. Search for value="Bipolar" and replace those instances with value="Polarity"
4. Save the file and reload Zebra 3

These are the lines that should have been altered...

Line 26996:
PROPERTY control='tosc1-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line 27201:
PROPERTY control='tosc1-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28075:
PROPERTY control='tosc2-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28280:
PROPERTY control='tosc2-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28958:
PROPERTY control='tosc3-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29163:
PROPERTY control='tosc3-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29916:
PROPERTY control='tosc4-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 30121:
PROPERTY control='tosc4-f1lbl-pol' name='labeltext' id='0' value='Polarity'

[johnnyberrygoode]

Hello, thank you for update, but there are some issues that have not been fixed in the zebra3 3.0.2 version.
1. In the oscillator effects, in the "Window" effect, the first oscillator says "polarity", but in oscillators 2-4 it says "bipolar".

You can:

1. Make a copy of the "Zebra3_orig.txt" file somewhere, just in case
2. Make sure Zebra3 is not being used by your DAW
3. Search for value="Bipolar" and replace those instances with value="Polarity"
4. Save the file and reload Zebra 3

These are the lines that should have been altered...

Line 26996:
PROPERTY control='tosc1-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line 27201:
PROPERTY control='tosc1-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28075:
PROPERTY control='tosc2-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28280:
PROPERTY control='tosc2-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28958:
PROPERTY control='tosc3-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29163:
PROPERTY control='tosc3-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29916:
PROPERTY control='tosc4-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 30121:
PROPERTY control='tosc4-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Thank you

[johnnyberrygoode]

Hello, thank you for update, but there are some issues that have not been fixed in the zebra3 3.0.2 version.
1. In the oscillator effects, in the "Window" effect, the first oscillator says "polarity", but in oscillators 2-4 it says "bipolar".

You can:

1. Make a copy of the "Zebra3_orig.txt" file somewhere, just in case
2. Make sure Zebra3 is not being used by your DAW
3. Search for value="Bipolar" and replace those instances with value="Polarity"
4. Save the file and reload Zebra 3

These are the lines that should have been altered...

Line 26996:
PROPERTY control='tosc1-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line 27201:
PROPERTY control='tosc1-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28075:
PROPERTY control='tosc2-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28280:
PROPERTY control='tosc2-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 28958:
PROPERTY control='tosc3-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29163:
PROPERTY control='tosc3-f1lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 29916:
PROPERTY control='tosc4-f2lbl-pol' name='labeltext' id='0' value='Polarity'

Line: 30121:
PROPERTY control='tosc4-f1lbl-pol' name='labeltext' id='0' value='Polarity'

It would be great if you could tell me how to change the coordinates of this label.

Edit: It took some time, but I found it.

[ffx]

The FMO modules seem to produce a DC offset. e.g. in preset "Angelic Chariots". Why is that, can I prevent that in this preset? It is only happing in "ModFM" mode.



... Because ModFM is e^x, with x>=0? Might be mathematically correct, but maybe a dc offset filter still would not hurt here?

In Six Sines, the exp mode, not sure if the same:
https://github.com/baconpaul/six-sines/ ... ode.h#L188

[cullenspub]

Thank you for a fantastic update. Using the new Linux build I have been able to drag files between instances of the plugin as well as from outside into the plugin. Nice work!

I may have found a regression.
My Linux build of Zebra 3.0.2 (rev 22175) does not draw target finders (no Highlights, Tentacles, or Lasers).

To Reproduce:
Init a preset sound and add a LFO 1 modulation on Osc 1 Curve Morph. Hover over the The Env 1 or the LFO 1 pip. Expecting the target finder to render but it does not draw.

OS:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.7.2
Kernel Version: 7.1.3-101.fc43.x86_64 (64-bit)
Graphics Platform: Wayland

DAW:
Reaper v7.77

[Viktor [TUC]]

... but maybe a dc offset filter still would not hurt here?

In general we kept the option to have DC offsets if needed (can make a difference when going into filters or distortion modules) - to remove them you add a Utility module at the end, switch to Signal mode and turn on DC Block.

Viktor
u-he team

[ffx]

In general we kept the option to have DC offsets if needed (can make a difference when going into filters or distortion modules) - to remove them you add a Utility module at the end, switch to Signal mode and turn on DC Block.

Ah, thanks! totally missed the "signal mode" of the utility. Now it makes all sense

[ffx]

In general we kept the option to have DC offsets if needed (can make a difference when going into filters or distortion modules) - to remove them you add a Utility module at the end, switch to Signal mode and turn on DC Block.

I've just tried that, sadly the DC offset filter is not killing the dc offset of the FMO1, instead it inverts the signal:

util-bug.h2p.zip

I would assume that an automatic DC offset filter on each synthesis slots end, before it flows into fx, would be much better. The synth end output should be DC offset fixed in any case, IMHO.

Currently FMO will produce DC offset in some cases, and avoiding it requires a lot of detail knowledge already. It should be the opposite, DC offset fixed by default, and with DC offset, if you specifically want that. At least my two cents here.

[Urs]

In general we kept the option to have DC offsets if needed (can make a difference when going into filters or distortion modules) - to remove them you add a Utility module at the end, switch to Signal mode and turn on DC Block.

I've just tried that, sadly the DC offset filter is not killing the dc offset of the FMO1, instead it inverts the signal: util-bug.h2p.zip

I would assume that an automatic DC offset filter on each synthesis slots end, before it flows into fx, would be much better. The synth end output should be DC offset fixed in any case, IMHO.

Currently FMO will produce DC offset in some cases, and avoiding it requires a lot of detail knowledge already. It should be the opposite, DC offset fixed by default, and with DC offset, if you specifically want that. At least my two cents here.

When I play your preset, I get the following output:

Screenshot 2026-07-23 at 20.58.29.jpg

As the upright area above the zero line is the same size as the flat area below it, there is no DC offset.

[ffx]

Ah! ok, should have checked more carefully

[ptnah]

[*]New "Global" trigger option for MSEGs

thank you so much, Urs.
love it!!

^^bumping my own comment from the other (now abandoned) thread.
i am using it all the time, so so cool to have it! thanks again, Urs.