Zebra 3 final final beta 21764 April 14

[tasmaniandevil]

Hope this helps! Let me know if there is anything else I can do.

This is something we already have in our backlog. It’s happening when you do what you do in the video, going up/down/up/down quickly a lot of times.

What worries me more is your report of the mouse range increasing significantly when you activate the Hide Mouse on Drag feature.

I’ll ask again, what’s the polling rate of your mouse (Hz & DPI), and do you have a way to adjust this rate to test if it improves the situation? Or do you have another mouse you could test this with?

You’re the first one reporting this in the four months since Zebra 3 is in beta, and we never experienced it over here while working on improving the mouse behaviour. That's why it would be good to get more details, so we can find a way to reproduce it.

[bmanic]

Hope this helps! Let me know if there is anything else I can do.

This is something we already have in our backlog. It’s happening when you do what you do in the video, going up/down/up/down quickly a lot of times.

I don't have to go fast.. it can glitch out and get stuck or jump to a random value even when I go slow with the mouse. It seems pretty random / unpredictable when it happens. I just did it fast in the video to get as many glitches as possible recorded in a short clip. Nobody wants to look at me dragging a mouse cursor at slow speeds.

What worries me more is your report of the mouse range increasing significantly when you activate the Hide Mouse on Drag feature.

I’ll ask again, what’s the pulling rate of your mouse (Hz & DPI), and do you have a way to adjust this rate to test if it improves the situation? Or do you have another mouse you could test this with?

I don't have any idea of what the default polling rate of this thing is. My question to you is this though: Why does it matter? It works 100% reliably in all other software. This is the only piece of software where I see this glitch happening. It doesn't happen in Reaper, doesn't happen in any other plugins (and I have literally hundreds that I use weekly), doesn't happen anywhere else.

If it _really_ helps to figure out the polling rate / DPI I am willing to install Logitech G-driver or whatever it's called but on purpose I've tried to keep the system quite minimal and would thus like to avoid installing extra stuff.

I can borrow another mouse. I'm sure one of my kids can part with theirs for a few hours. I'll let you know how that goes.

You’re the first one reporting this in the four months since Zebra 3 is in beta, and we never experienced it over here while working on improving the mouse behaviour. That's why it would be good to get more details, so we can find a way to reproduce it.

.. and I can 100% confirm that this is the first time this is happening and it did NOT happen with the previous two betas that I tried, which was the absolute first public one released and the second update. Not sure if you had any others in between.. but those two with the old GUI did NOT have this problem. I would have noticed as I tinkered with them for hours on end and here the glitch appears virtually immediately.


EDIT: Another idea/possibility. Maybe this mouse is actually faulty and sometimes sends out extremely short sikes of random data points but all other software has strict filtering that takes these out? Anybody know a debugger of sorts where I could monitor the exact numerical output of my mouse movements? I'll of course test with another mouse too but that'll have to wait until the evening and this is something I could try right away.

[pdxindy]

I don't have any idea of what the default polling rate of this thing is. My question to you is this though: Why does it matter? It works 100% reliably in all other software. This is the only piece of software where I see this glitch happening. It doesn't happen in Reaper, doesn't happen in any other plugins (and I have literally hundreds that I use weekly), doesn't happen anywhere else.

It matters for tracking down the issue.

You can try this website to measure the polling rate.
https://testufo.com/mouserate

See if that works. There are other sites to try if that one doesn't work.

[bmanic]

I don't have any idea of what the default polling rate of this thing is. My question to you is this though: Why does it matter? It works 100% reliably in all other software. This is the only piece of software where I see this glitch happening. It doesn't happen in Reaper, doesn't happen in any other plugins (and I have literally hundreds that I use weekly), doesn't happen anywhere else.

It matters for tracking down the issue.

You can try this website to measure the polling rate.
https://testufo.com/mouserate

See if that works. There are other sites to try if that one doesn't work.

Okay, according to that site, moving the mouse in circles gives me a polling rate of 470Hz.

[johnnyberrygoode]

Hello, this may sound a little too much, but if you move the letter "D" in the envelope module one pixel to the right, it would be perfect.

[tasmaniandevil]

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.

[loctune]

As far as I can see there isn’t any easy way to sync oscs in Zebra 3 yet. What would be the ideal way to create a sub osc then?

[Urs]

On Intel Mac, box appears around the LFO tool while selecting it. This is not the case though on ARM chip which is working as expected. Contrast is much better, although there is some shading differences between the LFOs/ MSEGS on the outlines of the knobs compared to the filter and OSC sides (left/right). Also some small general shading and colour issues around the knobs of some modules. Personally I would go slightly darker shades around the grey OSCs and a slightly lighter line. UX wise I think the Synthesis, Pitches, and Presets boxes could be a fraction bigger seems a little silly to have space around those selectors while things like undo take up the whole height of that top bar. Other than that for me as a user, it's good to go!

If Intel Mac and Apple silicon render differently, that's entirely an issue with the graphics pipelines installed there. There is no difference in the data we feed it. Are you using the same monitor and colour profile?

[Urs]

As far as I can see there isn’t any easy way to sync oscs in Zebra 3 yet. What would be the ideal way to create a sub osc then?

Use two oscillators and reset phase.

Personally I prefer free running oscillators an octave below the main oscillators. If I need the harmonic structure of a waveform + a square wave an octave or two below, I'd usually bake it into the waveform itself.

[loctune]

As far as I can see there isn’t any easy way to sync oscs in Zebra 3 yet. What would be the ideal way to create a sub osc then?

Use two oscillators and reset phase.

Personally I prefer free running oscillators an octave below the main oscillators. If I need the harmonic structure of a waveform + a square wave an octave or two below, I'd usually bake it into the waveform itself.

Yeah, reset phase feels less ideal but probably the only way to do it with more than simple analog waveforms for now. I guess this could also be a feature request for future.

And before getting into the true hard sync territory, how about the idea of having an osc fx which adds the sub osc waveform based on the current setting? Seems like this could be pre-calculated and wouldn’t be super complicated to implement…

[Urs]

Yeah, that could be doable...

[Milkman]

Almost all of these presets are examples of my favorite characteristics of sound design, of music genres generally, and of electronic music performance (macros and playable controls). All my DAWs are happy with it, and Z3 is already teetering on the edge of being my #1 soft synth in the last 26 years, easily. Thanks for this...

[bartoszkwiecinski]

Hey Urs and the entire u-he team,
thanks for making such beautiful plugins and finally letting Zebra loose into the wild world of freedom!
I'm not sure if this is the right place to ask, and I couldn't find any relevant information in the manual either.
How do I see which wavetable is selected in a preset? When I press OSC I can see the wavetables, but I can't figure out which one is currently selected.
Kind regards

I'm not from u-he, but until they respond, maybe this can help. When you click on an OSC, you'll see the OSC page below. You'll see a small downward-pointing arrow on the selected wavetable. Turning the Curve Morph knob moves the arrow head (or playhead) allowing you to select different wavetables.

Hey, thanks for the response, but I don't really get it. As an example—the wonderful Felt Piano preset! If I change the oscillator or the wavetable, I can't get it back to the original settings when I reopen the preset. I can't see which wavetable is being used. (BTW: this is an amazing preset and emulation of a piano!)

[aMUSEd]

Hey Urs and the entire u-he team,
thanks for making such beautiful plugins and finally letting Zebra loose into the wild world of freedom!
I'm not sure if this is the right place to ask, and I couldn't find any relevant information in the manual either.
How do I see which wavetable is selected in a preset? When I press OSC I can see the wavetables, but I can't figure out which one is currently selected.
Kind regards

I'm not from u-he, but until they respond, maybe this can help. When you click on an OSC, you'll see the OSC page below. You'll see a small downward-pointing arrow on the selected wavetable. Turning the Curve Morph knob moves the arrow head (or playhead) allowing you to select different wavetables.

Hey, thanks for the response, but I don't really get it. As an example—the wonderful Felt Piano preset! If I change the oscillator or the wavetable, I can't get it back to the original settings when I reopen the preset. I can't see which wavetable is being used. (BTW: this is an amazing preset and emulation of a piano!)

I think you are misunderstanding what that drop down is - it allows people to load and save OSC settings but it is not a wavetable loader in the traditional sense. The OSC shapes in that patch were probably drawn just for that patch, not built from a pre existing OSC, so you are not going to be able to get it back from anything in that dropdown - but you could save it yourself - give it a memorable name - then reuse it in other patches.

[bartoszkwiecinski]

Ah okay, so now I get it. Thanks a lot!