Zebra 3 Beta Bug Reports

[Urs]

Is it known that importing presets from Zebralette to Zebra3 doesn't work for all parameters?

Yes, mentioned in the first post of the beta thread...

The preset adapter to load Zebralette 3 presets inside Zebra 3 is still work in progress

[dengste]

(EDIT: Just saw this is already reported, sorry for the noise...)

Another thing: I have mapped controller knobs to CC 2,11,75 and 76, so that they can control the "Ctrl A-D" knobs. This works, however, the knobs are not visually moving alongside inside the VST (they do for MW and PB, though). Again: the CC reaches the VST just fine and modulates the sound accordingly, just visually the knobs stay at zero.

[jnchristp]

Is it known that importing presets from Zebralette to Zebra3 doesn't work for all parameters?

Yes, mentioned in the first post of the beta thread...

The preset adapter to load Zebralette 3 presets inside Zebra 3 is still work in progress

OK, sorry, just ignore my post...

[Urs]

No worries!

[SamDi]

Inconsitency error in draw shape flip settings vs. auto flip:

Pre:
-Flip X and Flip Y are unset
-Shape auto flip activated
-take e.g. shape 5

Action:
-Drag in grid from top left to down right. Shape is drawn in grid as shown in the tool windows --> OK

-Activate Flip X and Flip Y. Shape is drawn in the tool windows correctly (180° turn) --> OK
-Drag in grid from top left to down right. Shape is drawn in the grid as in the tool windows (180° turn) --> OK

-Deactivate Flip X, activate Flip Y. Shape is drawn in the tool windows correctly (horizontally flipped) --> OK
-Drag in grid from top left to down right. Shape is NOT drawn in the grid as in the tool windows (drawn as unflipped) --> NOK

-Activate Flip X, deactivate Flip Y. Shape is drawn in the tool windows correctly (vertically flipped) --> OK
-Drag in grid from top left to down right. Shape is NOT drawn in the grid as in the tool windows (drawn as HORIZONTALLY flipped) --> NOK

Expectation:
Drawing from top left to down right draws the shape in the grid as it is shown in the tool windows with the according flip settings.

[Urs]

I wonder if auto-flip overrides the shape flip settings? Not sure...

[WalterH]

It's hard to find bugs other than those already been appointed, Z3 is very well done, hats off.

I have feature request
I'm working with quite complex sound and have 3 OSCs + all LFO's at work + 2 effects, and I will have to have notepad to memorize all that when it will go even more complicated, would be nice to write notes directly into a modules, or maybe just ability rename modules, I dunno.

will add another one if I may.
locked knob with yellow quite big locker icon is too big, I'm sure transpharent white minimalistic style locker will be better, locked parameters can be adjusted even when they are locked and you can't see where that knob tick is moving as locker covers 50% of knob, nothing too terrible but anyway..

[exmatproton]

*When one uses the Expanse and Vanilla filters (HP, 12dB, 24dB) there is always bleed of the unaffected input. Unless the resonance is completely off.

[Harmes]

There’s a small bug: when key control is activated and any encoder of a module is selected in any of the both selection areas the white square won’t disappear or stay at the encoder when you scroll up or down.

[bluemoonone]

When using the reverb in classic mode and increasing the wet amount, the channel balance shifts - the higher the wet value, the louder the left channel becomes.

[bluemoonone]

Known Issues:

• There is a modulation depth indicator glitch when swapping Osc FX slots

It seems that the modulation is not always properly synchronized — not only when swapping the OSC FX slot, but also when changing the modulation depth. However, I haven't been able to reliably reproduce the issue yet. It might be related to where the modulation depth was adjusted last, for example via the modulation matrix versus directly at the modulation target.

Additionally, Zebra only opens on the second attempt for me. On the first attempt, Cubase (Windows 11) appears to try to create the window, but it only actually opens on the second try.

I'm not sure whether the following behavior is a bug, but I noticed something when using MMap (Key mode) to control OSC volume. The idea is that higher notes should reduce the volume more strongly, while lower notes reduce it less. This works as expected, but only up to a certain modulation depth. If the modulation depth is set too high, the behavior flips: the highest notes no longer reduce the volume the most.

Example:
MMap (Key mode) > OSC 1 Volume
OSC Volume set to 80
MMap ramp from the lowest to the highest note (88 keys / steps)
Modulation set to unipolar, so low notes produce minimal modulation and high notes the maximum

If the modulation value stays below the target offset (e.g. –78), everything behaves as expected: the highest note produces a very quiet signal.
If the modulation value exceeds the target offset (e.g. –82), the behavior flips around the zero point: the highest notes become louder, or are modulated less than some lower notes. Logically, I would expect the highest note to produce no signal at all, since the volume should already be reduced to zero.

While we're on MMap: I’m glad it wasn't removed.
It would be great if the steps could be defined manually.

[WalterH]

*When one uses the Expanse and Vanilla filters (HP, 12dB, 24dB) there is always bleed of the unaffected input. Unless the resonance is completely off.

yes, when increasing resonance on abovementioned filters low frequency starts to kick in, quite a lot btw...

[WalterH]

Can anyone explain why simple sinewave have that clapping sound ??
You can play sound directly in browser from that dropbox link..

https://www.dropbox.com/scl/fi/9c8tojbz ... gxz0m&dl=0



This clap only happens if attack is 0, but should it be like that, why 0 attack introduces sound that has nothing to do with original wave ?

[joradn]

Can anyone explain why simple sinewave have that clapping sound ??
You can play sound directly in browser from that dropbox link..

This clap only happens if attack is 0, but should it be like that, why 0 attack introduces sound that has nothing to do with original wave ?

Because the starting phase of your waveform is at maximum amplitude, so you are essentially sending a sudden impulse of all frequencies when you begin playing a note. Increasing attack will ease the amplitude in. If you use the phase rotate tool to shift the start of your waveform to the zero crossing, it will begin smoothly.

[WalterH]

I think you mean certer vertical line as zero crossing (where there is no sound), well it claps anyway.

Oh.. I guess I need to enable phase Reset there, now it makes sense, ok thanks !