Zebra 3 - final beta Rev 21625 April 8th

[pdxindy]

I know some people made a point about the knob of the LFO being a bit tedious. Would a reasonable solution be to add a click function to the shapes so that the knob snaps to the shape that is selected? And then just shifting the bipolar/positive selector a little further down.

It was already mentioned that it will be implemented for the release.

[Alexander_D]

+1 about the new UI. Honestly no so excited about this new UI.. looks little strange.. don't know why.. but maybe will be nice to have some options to change it.. I really like Zebra 2 design and Zebralette3 as well. This one is not perfect. All modules looks the same... it just IMHO of course...

[Erdemkeys]

I finally gave Zebra 3 a try yesterday evening and god it sounds amazing.
That UI is very displeasing tho, looks dated and almost cheap, especially compared to Zebralette 3 which looked so slick.

(Also I cant wrap my head around how the FM oscillator work Gonna need to dig deeper into that).

Zebralette3 — top UI. O hope that the team just teasing us with Zebra 3 Beta )

+1 for me, Zebralette 3 design is much smoother with dark and light options!

[ThoughtExperiment]

Not so important, I'd just like to understand. It's entirely possible that it is modulating something and I just can't see it (although I've tried altering the rate and I don't hear anything). Any ideas, anyone?

It's some sort of glitch. LFO3 is not assigned to anything. If you right click on the crosshairs of a modulator, you can see all the assignments. LFO3 has none.

Ok, thanks for that. I did the right-click on the crosshairs but because I didn't see anything I naturally wondered if I'd missed some other way of checking. So I suppose it's good to know it's a glitch

[Viktor [TUC]]

Not so important, I'd just like to understand. It's entirely possible that it is modulating something and I just can't see it (although I've tried altering the rate and I don't hear anything). Any ideas, anyone?

It's some sort of glitch. LFO3 is not assigned to anything. If you right click on the crosshairs of a modulator, you can see all the assignments. LFO3 has none.

Ok, thanks for that. I did the right-click on the crosshairs but because I didn't see anything I naturally wondered if I'd missed some other way of checking. So I suppose it's good to know it's a glitch

Yes and no, in Osc 1, if you switch the OscFX1 to Twinkles, it's the Trigger source for that effect. Was quite the little puzzle to solve.
I'll mention it to the devs, thanks for the find.

[ThoughtExperiment]

I finally gave Zebra 3 a try yesterday evening and god it sounds amazing.
That UI is very displeasing tho, looks dated and almost cheap, especially compared to Zebralette 3 which looked so slick.

(Also I cant wrap my head around how the FM oscillator work Gonna need to dig deeper into that).

Zebralette3 — top UI. O hope that the team just teasing us with Zebra 3 Beta )

+1 for me, Zebralette 3 design is much smoother with dark and light options!

Yes, Zebralette 3 is a nice design but it's worth remembering that there's a heck of a lot more going on with Zebra3...

[Urs]

I know some people made a point about the knob of the LFO being a bit tedious. Would a reasonable solution be to add a click function to the shapes so that the knob snaps to the shape that is selected? And then just shifting the bipolar/positive selector a little further down.

Afaiaa the waveforms will be directly selectable.

[ThoughtExperiment]

Not so important, I'd just like to understand. It's entirely possible that it is modulating something and I just can't see it (although I've tried altering the rate and I don't hear anything). Any ideas, anyone?

It's some sort of glitch. LFO3 is not assigned to anything. If you right click on the crosshairs of a modulator, you can see all the assignments. LFO3 has none.

Ok, thanks for that. I did the right-click on the crosshairs but because I didn't see anything I naturally wondered if I'd missed some other way of checking. So I suppose it's good to know it's a glitch

Yes and no, in Osc 1, if you switch the OscFX1 to Twinkles, it's the Trigger source for that effect. Was quite the little puzzle to solve.
I'll mention it to the devs, thanks for the find.

Wow, even better And well spotted, that was nicely hidden

[pdxindy]

Yes and no, in Osc 1, if you switch the OscFX1 to Twinkles, it's the Trigger source for that effect. Was quite the little puzzle to solve.
I'll mention it to the devs, thanks for the find.

The same thing happens if one puts an Osc into Additive mode, assigns an LFO to say Cluster, then switch back to Wavetable. A more likely occurrence.

[Alexander_D]

Still regarding UI. Now I probably know why Zebra 3 looks strange for me. ALL U-HE stuff looks so good..they have their unique style. But at the same moment I am still know that's it's U-HE. Regarding Zebra 3 it's different feel and vibe. Sorry that I again posting about UI. But I love U-HE and love Zebra 2.

[Yorrrrrr]

What a beast of a synth. However, GUI doesn't look as good as Zebralette 3. I don't know, it looks a little too dark and plain, no contrast, poor legibility, etc. U-He has done way better in the past in this regard.

[MCMorrise]

Still regarding UI. Now I probably know why Zebra 3 looks strange for me. ALL U-HE stuff looks so good..they have their unique style. But at the same moment I am still know that's it's U-HE. Regarding Zebra 3 it's different feel and vibe. Sorry that I again posting about UI. But I love U-HE and love Zebra 2.

As a person with mild visual impairment, my take is twofold:

1. The grey-on-grey design lacks contrast and is therefore straining on the eye.
2. Much of the text is too small to render cleanly on smaller displays. Using Z3 on my 27" 5K iMac screen is great because I can make it take up the whole screen, but using it at a size that fits on my ancient but still-working Cinema HD display (1920x1200) or my (also tiny, idk size) M1 MacBook, it looks blurry.

I haven't ever had an issue with u-he plugins' native UI legibility before this, and we haven't had any grey-on-grey UIs nor so much tiny text before, so I'm reasonably confident that these are the primary issues. I'm content to stick with presets until the inevitable Plugmon skin, but this should be something for the design team to be aware of. From an accessibility standpoint, Z3's native UI has too much small text and too little text/background contrast right now. (FWIW, text shadowing would solve the latter issue.)

[Urs]

Regarding Zebra 3 it's different feel and vibe.

Yes, and so does the beta UI and Zebralette 3 UIs.

It's because we have to go with times and switch to vector skins, which are more bland in general. The new design is however much less bland in this respect than the greenish one. Unlike the beta design, this new design is even reminiscent of much earlier version of Zebra.

The current design bears a lot of functional necessity. I'm itching to make a more outgoing, more characterful design myself. Unfortunately, I have other responsibilities.

[Alexander_D]

Regarding Zebra 3 it's different feel and vibe.

Yes, and so does the beta UI and Zebralette 3 UIs.

It's because we have to go with times and switch to vector skins, which are more bland in general. The new design is however much less bland in this respect than the greenish one. Unlike the beta design, this new design is even reminiscent of much earlier version of Zebra.

The current design bears a lot of functional necessity. I'm itching to make a more outgoing, more characterful design myself. Unfortunately, I have other responsibilities.

Of course I am understand this. Thanks for explain and hope to see some skins in Zebra 3..

[MarcelEE]

One last issue. When a Oscillator is selected i.e. E-piano it is not possible to see that the selection is active. Maybe a point before it can help to find the chosen selection. The same for the selection of te MSEG and the mapper.
Wish you all the best wiith Zebra3