Zebra 3 Beta Bug Reports

[Dirkitator]

Incorrect key assignment for grouping modules:

From the Hanfbuch, page 14:
"Ctrl (PC) / command (Mac) + click adds or removes individual modules".
This is the usual behaviour in Windows.

In Z3bra, however, I have to hold down the ALT key instead of the CTRL key.

Clap version on Windows 10 in Bitwig

[Urs]

*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.

I don't recall for the Vanilla filter, but for Expanse that is due to the way it's set up. I deliberately added it this way to have this as a character.

[miegler]

Modulation visibility in the moduls:
It is very hard to grab the value (arrow) versus the modulation amount (dot) when the knobs are small
The modulation value dots disappear, when the plug-in is closed and re-opened.
They become visible then when they are clicked in the mod matrix.
Visibility and naming for wave tables presets.
It would be great to have named wavetables presets which are indicated and can be selected in the osc tab
like in other wavetable synths.

[WalterH]

there is a typo in Z3 Docs or mistake in OSC's behavior:

Detune
"The function of this knob depends on the Unison setting: With Unison at 1 it fine tunes +/- 50 cent,
while for all other values it spreads the tuning of the unison 'voices'. Of course you can always fine
tune the overall pitch via Shift+Tune, whatever the Unison setting."

But OSC's detune isn't +-50, it's 100 cents left 100 cents right.

[Harmes]

Not sure if this is a bug or an intention (cannot find it in the bug report list):
Insert a Modal module, click on +, now if you press any of the arrows next to Factory profile it only switches between two cvs, but factory profile isn’t affected.

[Urs]

Not sure if this is a bug or an intention (cannot find it in the bug report list):
Insert a Modal module, click on +, now if you press any of the arrows next to Factory profile it only switches between two cvs, but factory profile isn’t affected.

I think that may be related to the current selection of profiles. The control is designed for them to be sorted into folders, so they can be browsed by folder/category. This works in a similar way for Hive's wavetables. But I guess currently they're all in one folder or so?

[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.

I don't recall for the Vanilla filter, but for Expanse that is due to the way it's set up. I deliberately added it this way to have this as a character.

Bleed isn't exactly the right word. When the resonance is turned off completely, it just acts like an HP Filter. When you engage the resonance, it turns into some sort of HP/Bell curve filter (both Expanse and Vanilla are doing this). Sure, if that is inteded for Expanse, fine. But i would expect that a vanilla filter does a normal HP, tbh

[magickalmutagen]

Some bugs I've come across:

1. No "none" option is available for Microtune, so once it's set it cannot be reset (other than by undoing or loading the init patch).
2. Scroll-wheeling (e.g. upwards) on the UI (e.g. on Osc 1's background) rather than on one of its controls (e.g. Osc 1's Pan) can cause the scroll-wheel to temporarily stop manipulating control values until having scrolled long enough on a control (try both up- and downwards), re-retargeted it with the mouse, or resetting it to its default value.
3. Plot Sources for the Oscs in the lower panel only shows the selected value in the control bar's read out when hovering over the first option (the sine icon). Ideally, when hovering over each of the options, the read out would display the hovered over name. As it stands, you have no idea what the other 3 options are until you select them, re-click them, or hover over the first option to show the selected option's name in the read out.
4. The module selection panel closes when clicked on some blank areas (the list's bottom or between its categories), but not when on other blank areas (e.g. to the list's right). It should do so consistently
5. Hairline graphics issue: Thin gap across the bottom of the module selection panel (can see through to the modulators rack).

rev 20399, CLAP, Bitwig Studio 6.0.0b9, Windows 11 x64

[tasmaniandevil]

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.

From the known issues section:
* The key control selection box does not adjust its position when using the scrollbar

[SamDi]

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

No override. The flip settings influence halfway the auto-flip, but in a non-consistent way.

[ThoughtExperiment]

Some bugs I've come across:

1. No "none" option is available for Microtune, so once it's set it cannot be reset (other than by undoing or loading the init patch).
   ...

rev 20399, CLAP, Bitwig Studio 6.0.0b9, Windows 11 x64

Not as obvious as 'none', but switching to 'Default Scale' has the same effect.

[magickalmutagen]

Not as obvious as 'none', but switching to 'Default Scale' has the same effect.

Ah, yes. Thanks, I didn't catch that. The initial value could probably read "Default Scale" instead then, although "none" is a bit more consistent, and less ambiguous because one could wonder what the default scale actually is (therefore I'd argue that the list option should read "none" instead).

[eclipse_soundlab]

Is it known that importing presets from Zebralette to Zebra3 doesn't work for all parameters? LFO settings aren't copied in full, pitch of OSC 1 is set to KeyFollow and not to pitches 1 so the transpose settings aren't working, no FX.

Yea. I had to call up the modulation matrix screens of Zebralette and Zebra and transfer the values ​​manually.

[Super Piano Hater 64]

Quoting my own post in another thread:

When you hover over most of these, a target reticle appears, and you just drag it to the control you want to modulate. (In the matrix, the reticle doesn't appear until you start dragging. I'm not sure if that's a bug.)

I checked the manual (where the squircles are called source pips) but didn't see any mention of this (minor) difference in UI behavior. I guess this thread is the place to ask: Is this difference intentional, or an oversight?

[exmatproton]

When using 'spectral decay' as a modifier, retriggering seems to be broken when you use 16 voices. The decay isn't being triggered when all voices have been used. At 15 polyphonic voices or less, this isn't happening. Actually, at 15 voices or less it happens as well, but less often. Same issue when selecting MONO + Overlap MONO