Zebra 3 3.0 RC1 Revision 21793

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Eluwei wrote: Sun Apr 19, 2026 8:36 pm While I've pondered how "post normalize gain:" might be calculated, tbh, I still don't fully grasp that yet, so, I just leave that at 0.
I tried 2 identical profiles, one at gain: 0 and one at gain: +4 and the only thing I noticed is that the +4 sounded louder. So I'm pretty sure it is just a manual adjustment to set the overall level of the profile.
Eluwei wrote: Sun Apr 19, 2026 8:36 pm Obviously, that interacts with the Normalize control in some way. Still hoping that someone on the dev or sound-design teams will illuminate how that's calculated. Not super critical, as the ones I've made work fine with it set to 0.
Normalize parameter adjusts the level of individual partials based on their gain value. If a partial has a positive gain value, then that partial will go up when Normalize is turned down.

Post

...
Last edited by Eluwei on Fri May 01, 2026 5:11 am, edited 1 time in total.

Post

Eluwei wrote: Sun Apr 19, 2026 10:22 pm Thanks. Good information.

I'm curious, when you are designing your modal profiles, what is the typical maximum number of modes you have preferred to define?

Thus far, as above, I've only been defining 32 modes (then I set Density to 32 as well), since I'm using two profiles; one in A and B, and in many cases, they may feature some higher harmonics as a result of calculating different types of series.

String.csv has 128, while Tube.csv features odd harmonics up to 127.
So far, I've tested to understand how they work. For that, 16 partials was enough and using only 16 also spreads them out enough that I could see each one and what it did on the graphical representation as parameters were adjusted.

It's hard to imagine doing more than 32 since it is a lot of manual work. I'm waiting for someone to create a useful utility for generating profiles :tu:

Post

...
Last edited by Eluwei on Fri May 01, 2026 5:11 am, edited 1 time in total.

Post

bmanic wrote: Sun Apr 19, 2026 5:30 pm Sorry for the very late report on this. I now have tried this with two other mice and all of the issues still persist. The only one that feels acceptably fast when mouse cursor is hidden, is the mouse with the slowest polling rate. Here is the rundown:
Thanks so much for doing all those tests. It's a mystery, but we'll figure it out. We'll collect some more mice until we can reproduce this and then fix it.
That QA guy from planet u-he.

Post

bmanic wrote: Sun Apr 19, 2026 5:30 pm The "mouse glitch issue": COPY PASTE from the previous thread, as I didn't notice there was one final version still.
tasmaniandevil wrote: Thu Apr 16, 2026 6:27 am
bmanic wrote: Thu Apr 16, 2026 5:57 am Okay, according to that site, moving the mouse in circles gives me a polling rate of 470Hz.
Thanks. It matters because it doesn’t happen anywhere else, and it’s hard to fix an issue which we cannot reproduce. If you find the time to test the Hide Mouse on Drag feature with another mouse, that would be much appreciated.
System: Mac Mini M1, Sonoma 14.6.2, Reaper (latest version as of this writing), Zebra 3 VST3 plugin version.

Sorry for the very late report on this. I now have tried this with two other mice and all of the issues still persist. The only one that feels acceptably fast when mouse cursor is hidden, is the mouse with the slowest polling rate. Here is the rundown:

1) Logitech G203, my original main mouse. Polling rate 470Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. They randomly glitch and jump.. sometimes suddenly jumping to 0% or to 100% of the range.

- "Hide mouse on drag = ON". This makes the response of the knobs feel like dragging them through mud. It takes extremely large movements to get a knob from 0 to 100%, literally several swipes over the whole mouse pad (I measured it to about 30cm physical travel on the pad).


2) Wife's Steelseries Kinzu v3. Polling rate 260Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. They randomly glitch and jump.. sometimes suddenly jumping to 0% or to 100% of the range.

- "Hide mouse on drag = ON". Slightly better response on knobs. Still feels like it's dragged through mud though. Wouldn't be fun to use.


3) Kid's super basic and cheap Logitech mouse that comes with a keyboard. No idea what model but the whole set costs like 30 euros for both keyboard and mouse. Polling rate 103Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. I think I got a little less sudden jumps with this one and I can't remember getting sudden extreme jumps. It is however glitchy and sometimes the knob goes the opposite way of the mouse drag (mouse + click/drag going down, yet knob going up).

- "Hide mouse on drag = ON". This mouse is acceptable with this setting. It's still at the edge of being annoyingly slow but at least I could work with this for a little while.


Sorry once again for being so late with this. I just didn't get enough time as I hoped and only got around to doing this today. Anyhow, I'm sure you guys will figure this out at some point. Good luck and fortune with the release. I've of course purchased a copy and look forward to the many years of awesomeness with this marvel you all have created!
I had a similar problem before.
Maybe it's not a mouse issue but a Reaper thing.

Could you try turning Reaper's "Save minimal undo states" option on/off and see if anything changes?
I had similar glitches when changing parameters, and turning this option ON fixed it for me.
It changes Reaper's undo behavior a little, so it's a trade-off, but it might help.

My system: Windows11, Reaper v7.69, Zebra3 VST3 RC1, Ryzen9/RX7600M

Post

mem303 wrote: Mon Apr 20, 2026 4:51 am
bmanic wrote: Sun Apr 19, 2026 5:30 pm The "mouse glitch issue": COPY PASTE from the previous thread, as I didn't notice there was one final version still.
tasmaniandevil wrote: Thu Apr 16, 2026 6:27 am
bmanic wrote: Thu Apr 16, 2026 5:57 am Okay, according to that site, moving the mouse in circles gives me a polling rate of 470Hz.
Thanks. It matters because it doesn’t happen anywhere else, and it’s hard to fix an issue which we cannot reproduce. If you find the time to test the Hide Mouse on Drag feature with another mouse, that would be much appreciated.
System: Mac Mini M1, Sonoma 14.6.2, Reaper (latest version as of this writing), Zebra 3 VST3 plugin version.

Sorry for the very late report on this. I now have tried this with two other mice and all of the issues still persist. The only one that feels acceptably fast when mouse cursor is hidden, is the mouse with the slowest polling rate. Here is the rundown:

1) Logitech G203, my original main mouse. Polling rate 470Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. They randomly glitch and jump.. sometimes suddenly jumping to 0% or to 100% of the range.

- "Hide mouse on drag = ON". This makes the response of the knobs feel like dragging them through mud. It takes extremely large movements to get a knob from 0 to 100%, literally several swipes over the whole mouse pad (I measured it to about 30cm physical travel on the pad).


2) Wife's Steelseries Kinzu v3. Polling rate 260Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. They randomly glitch and jump.. sometimes suddenly jumping to 0% or to 100% of the range.

- "Hide mouse on drag = ON". Slightly better response on knobs. Still feels like it's dragged through mud though. Wouldn't be fun to use.


3) Kid's super basic and cheap Logitech mouse that comes with a keyboard. No idea what model but the whole set costs like 30 euros for both keyboard and mouse. Polling rate 103Hz.

- Randomly glitchy knob behavior, no matter how fast or slow you tweak a knob. I think I got a little less sudden jumps with this one and I can't remember getting sudden extreme jumps. It is however glitchy and sometimes the knob goes the opposite way of the mouse drag (mouse + click/drag going down, yet knob going up).

- "Hide mouse on drag = ON". This mouse is acceptable with this setting. It's still at the edge of being annoyingly slow but at least I could work with this for a little while.


Sorry once again for being so late with this. I just didn't get enough time as I hoped and only got around to doing this today. Anyhow, I'm sure you guys will figure this out at some point. Good luck and fortune with the release. I've of course purchased a copy and look forward to the many years of awesomeness with this marvel you all have created!
I had a similar problem before.
Maybe it's not a mouse issue but a Reaper thing.

Could you try turning Reaper's "Save minimal undo states" option on/off and see if anything changes?
I had similar glitches when changing parameters, and turning this option ON fixed it for me.
It changes Reaper's undo behavior a little, so it's a trade-off, but it might help.

My system: Windows11, Reaper v7.69, Zebra3 VST3 RC1, Ryzen9/RX7600M
No. I had the same in FL Studio and Bitwig. Although, not very often.

Post

Those momentary hangs are something we can reproduce.
The issue we cannot reproduce is the extrem slow-down of the mouse travel for bmanic when he's using the Hide Mouse on Drag feature.
That QA guy from planet u-he.

Post

tasmaniandevil wrote: Mon Apr 20, 2026 7:47 am Those momentary hangs are something we can reproduce.
The issue we cannot reproduce is the extrem slow-down of the mouse travel for bmanic when he's using the Hide Mouse on Drag feature.
I can't either. Not experiencing that. Those glitchy movements from time to time; yes

Post

...
Last edited by Eluwei on Fri May 01, 2026 5:10 am, edited 1 time in total.

Post

...
Last edited by Eluwei on Fri May 01, 2026 5:10 am, edited 1 time in total.

Post

Indeed. Congrats U-He team...must have been a crazy period. 🥳

Post

Sampleconstruct wrote: Sun Apr 19, 2026 10:35 am Is it intended that when I load a saved OSC wavetable into an existing patch all modulations get unassigned and the OSC FX disappear? If so, that's a pity...
It’s a bit of a workaround but there's a manual fix for this.

Open the .h2p file with a text editor and strip out most of the parameter lines. Zebra3 will skip the missing parts when loading, effectively replacing only the waveforms while keeping your other parameters intact.

Check the attached sample to see how it's done!
You do not have the required permissions to view the files attached to this post.
ImageMONA, the new skin for DIVA is released! | Follow me on Twitter.

Post

Awesome release guys. Delighted to own a copy of this wonderful synth. Thank you.

Post

...
Last edited by Eluwei on Fri May 01, 2026 5:10 am, edited 1 time in total.

Post Reply

Return to “u-he”