Zebra 3 Beta Bug Reports

[Urs]

I'm not sure if this has been mentioned: Controls A-D don't visually reflect their saved positions when reloading a patch, the saved values are correct but the knobs are all turned hard left.

It's a general problem that we have to address, and a decision to be made whether or not to save them with preset (macro function) or keep them solely as modulators (MIDI, Expression, Automation).

I'm tending towards *not* saving them with preset, but adding a button to "bake them in". Or, adding options to allow for either, which is a bit more tricky. OTOH I'll probably just try what happens if they can be saved and recalled.

My hope is that we can avoid setting up MIDI CCs, Macros and (automatable) Expressions with 3 different systems that more often than not affect the same parameters.

[crimclark]

donkbug.h2p.zip

I have a patch (attached above) where the sound changes when I open the plugin UI.

In other words, I program a midi sequence and save the project in my DAW. When I reopen the project it sounds different until I open Zebra. It almost sounds like it is pitched up an octave, which I think is related to the Delta X effect I am using. When I open Zebra the sound pitches back down.

In Ableton the sound changes immediately. In Renoise I have to tweak a couple parameters for it to flip back.

I tried to simplify the patch to isolate the issue, but haven't been able to figure it out exactly what is causing it.

[Fannon]

It's a general problem that we have to address, and a decision to be made whether or not to save them with preset (macro function) or keep them solely as modulators (MIDI, Expression, Automation).

I'm tending towards *not* saving them with preset, but adding a button to "bake them in". Or, adding options to allow for either, which is a bit more tricky. OTOH I'll probably just try what happens if they can be saved and recalled.

My hope is that we can avoid setting up MIDI CCs, Macros and (automatable) Expressions with 3 different systems that more often than not affect the same parameters.

With Expressions do you mean Mod-Wheel and MPE Timbre or something else, too?

Curious what you'll arrive here as a solution. Interesting idea to only optionally bake in the values of Macros, but I wonder if that might be confusing if you don't know this. What would be the advantage of not baking it in vs. setting them all to 0 when saving the preset?

Baking them in might also have the advantage that your macro might be setup bipolar (then set it to 50) or has a default sweet spot somewhere between 0 and 100.

You also mentioned somewhere that the resolution of automation is not as good as MIDI CC directly - does this also apply to the CLAP format?

[ThomasHelzle]

I'll mention my problem with a Wacom pen in absolute mode here in this thread as well, as it may have gone buried in the other:
When I move any rotary control in Zebra 3 with the pen (I don't have a mouse attached), it shoots to either extreme very fast, making it almost impossible to use.
This isn't an issue in Zebra 2/HZ.

This is on Windows 11 Home 24H2 with a Wacom Intuos 5 Touch (with touch disabled) in Wintab mode ("Use Windows Ink" unchecked in the driver). Driver version 6.3.46-2 (Last supported version).

WacomSetting.png

This usually happens in Software that uses some kind of mouse virtualisation which fights against the absolute position of the Wacom pen.
Bitwig calls the setting to fix the issue "Absolute Mouse Mode" (needs to be checked), VCV-Rack calls it "Lock Cursor While Dragging" (needs to be unchecked).

Would be very cool to have this as an option either in the GUI or some text config file.

Thanks a lot - Zebra 3 looks amazing otherwise!

Cheers,

Tom

[Urs]

Tom, switch mouse hiding off, that should fix issues with mouse travel.

[Urs]

It's a general problem that we have to address, and a decision to be made whether or not to save them with preset (macro function) or keep them solely as modulators (MIDI, Expression, Automation).

I'm tending towards *not* saving them with preset, but adding a button to "bake them in". Or, adding options to allow for either, which is a bit more tricky. OTOH I'll probably just try what happens if they can be saved and recalled.

My hope is that we can avoid setting up MIDI CCs, Macros and (automatable) Expressions with 3 different systems that more often than not affect the same parameters.

With Expressions do you mean Mod-Wheel and MPE Timbre or something else, too?

Curious what you'll arrive here as a solution. Interesting idea to only optionally bake in the values of Macros, but I wonder if that might be confusing if you don't know this. What would be the advantage of not baking it in vs. setting them all to 0 when saving the preset?

Baking them in might also have the advantage that your macro might be setup bipolar (then set it to 50) or has a default sweet spot somewhere between 0 and 100.

You also mentioned somewhere that the resolution of automation is not as good as MIDI CC directly - does this also apply to the CLAP format?

MIDI has a higher temporal resolution than automation (which is also smoothed more). In CLAP, Parameter Modulation has the same resolution (64 samples granularity vs buffer size)

[ThomasHelzle]

Tom, switch mouse hiding off, that should fix issues with mouse travel.

Ah! I looked through the settings but this didn't click for me namewise.
Thanks a ton, all good now.

Cheers and thanks!

Tom

[Urs]

Yay

[misterandy]

In Osc editor, when source is set to Curve Spectrum, and using the grid tool to draw in partials in the harmonic grid, then one partial is generated when maths is set to either Rough or Fast - as expected - but when set to Precise the neighboring partial to the right is also generated. As shown in the pictures below. A bug? The same in Zebralette 3.

Math Fast_Rough.png

Math Precise.png

[Urs]

I have to check... the precise rendering pretty definitely has "use max value on vertical segments". It's totally possible that fast/rough have "use last value on vertical segments". That would explain the difference. Might make sense to unify this...

[misterandy]

Great! It would make most sense to change the Precise math to behave as fast/rough though, right? Then we have the possibility to actually draw in single partials with grid tool AND have all the possibilities with the other curve tools

[Urs]

Sure! OTOH we also want to introduce a drawing tool specifically for partials. Not sure when this is going too happen though...

[misterandy]

That would be much appreciated!

[NAD]

OTOH we also want to introduce a drawing tool specifically for partials.

This makes me happy.

[Urs]

Mind you, it's not going to be individual values. It's just going to be a tool that breaks up the curve on vertical grid lines and moves the value along them. The result will still be a curve, but it'll be quicker and easier to edit a specific spectrum within this system.