Zebra 3 Public Beta Revision 20399

[Urs]

I'm experimenting with the math-function in Zebra3 as a way to slew the release of pressure. "Slew with X" kind of works, but it also slews the attack of pressure. In Hive I'm using the Function generator for this, because it has Attack and Decay. Is there a way to do this in Zebra3 that I'm not seeing right now?

And by the way: Would't these Function generators perfectly fit Zebra3? They can be quite handy at times.

On second thought:

What if you also Modulate the Slew in the ModMath with the ModMath itself? I'd like to experiment with that, maybe there's a quick way to achieve this release-smoothing of pressure...

[jnchristp]

I'm experimenting with the math-function in Zebra3 as a way to slew the release of pressure. "Slew with X" kind of works, but it also slews the attack of pressure. In Hive I'm using the Function generator for this, because it has Attack and Decay. Is there a way to do this in Zebra3 that I'm not seeing right now?

And by the way: Would't these Function generators perfectly fit Zebra3? They can be quite handy at times.

On second thought:

What if you also Modulate the Slew in the ModMath with the ModMath itself? I'd like to experiment with that, maybe there's a quick way to achieve this release-smoothing of pressure...

Hm, doesn't seem to work for me. But I like the idea of Envelope Followers.

[FarleyCZ]

I do have a tiny suggestion. I absolutely love the new FMO module, especially after it's dev explained to me in Berlin. It's a very clever design. But from the tutorials I've seen some of the guys are struggling with understanding the modulation flow inside the module. I think it would help immensely if the arrows were much larger. They are easily overlooked by a novice user. ...let alone the fact it's not instinctively clear they're clickable/functional.

[PieBerger]

I do have a tiny suggestion. I absolutely love the new FMO module, especially after it's dev explained to me in Berlin. It's a very clever design. But from the tutorials I've seen some of the guys are struggling with understanding the modulation flow inside the module. I think it would help immensely if the arrows were much larger. They are easily overlooked by a novice user. ...let alone the fact it's not instinctively clear they're clickable/functional.

Maybe people making tutorials should read the manual first, before attempting to educate/demonstrate to, others . In case some of them find their way here, it's p51 under the Feedback header.

[tasmaniandevil]

Windows11:
Error message during installation.
The directory “c:\ProgramData\VSTPlugins 64 bit\U-HE\Zebra3.data” cannot be used.

However, if I create this directory, I can install Zebra3.

This message appears for a reason. Windows will not grant applications the needed permissions to create and edit files in the Program Files and Program Data locations. Zebra 3 will not function properly if the Zebra3.data folder is installed there.

We recommend installing the Zebra3.data folder to a location in the user documents section, as explained in this FAQ article: https://u-he.com/support/faq.html#compa ... -paths-win

[jasperdunn]

Is it possible to type in specific values at the top?
Also, is it possible to change Envelopes so that you can enter time in ms rather than the percentage?

[FarleyCZ]

I do have a tiny suggestion. I absolutely love the new FMO module, especially after it's dev explained to me in Berlin. It's a very clever design. But from the tutorials I've seen some of the guys are struggling with understanding the modulation flow inside the module. I think it would help immensely if the arrows were much larger. They are easily overlooked by a novice user. ...let alone the fact it's not instinctively clear they're clickable/functional.

Maybe people making tutorials should read the manual first, before attempting to educate/demonstrate to, others . In case some of them find their way here, it's p51 under the Feedback header.

I understand what you're saying, but usually there's only one shot for a first impression, right?

Maybe tutorials wasn't the right word. It was more like reviews or first reactions videos. Potential buyer will be relating to those influencers. And if they get lost without a manual, he/she will feel it's their fate as well. I think making two GUI arrows a bit thicker is a small price to pay for overall better readability of the interface.

[PieBerger]

I do have a tiny suggestion. I absolutely love the new FMO module, especially after it's dev explained to me in Berlin. It's a very clever design. But from the tutorials I've seen some of the guys are struggling with understanding the modulation flow inside the module. I think it would help immensely if the arrows were much larger. They are easily overlooked by a novice user. ...let alone the fact it's not instinctively clear they're clickable/functional.

Maybe people making tutorials should read the manual first, before attempting to educate/demonstrate to, others . In case some of them find their way here, it's p51 under the Feedback header.

I understand what you're saying, but usually there's only one shot for a first impression, right?

Maybe tutorials wasn't the right word. It was more like reviews or first reactions videos. Potential buyer will be relating to those influencers. And if they get lost without a manual, he/she will feel it's their fate as well. I think making two GUI arrows a bit thicker is a small price to pay for overall better readability of the interface.

I say let's have both bigger arrows and further UI/UX improvements, but also people should read and or explore more instead of expecting developers to make it intuitive dumb everything down for them.

[Quechh]

A suggestion/request--easy change I hope. Can the default scope setting be the close up--IE where you can actually see the waveform. For me the default is zoomed out and just noisy blur so every time I open I have to slide the slider all the way and fine tune. Or perhaps can the default be saved?'

Aside from that some positive feedback: I have never had a VST that can churn out so many happy accident sounds, one after another with tiny changes to even the simplest settings--really unique and awesome, honestly.

[atmelcool]

Here's a simplistic example of my standard method of getting diatonic chords using Mappers:
CHORDS.h2p.zip

Interesting solution, how did you tune them to the required frequencies, did you use a spectrum analyzer?

[Howard]

Here's a simplistic example of my standard method of getting diatonic chords using Mappers:
CHORDS.h2p.zip

Interesting solution, how did you tune them to the required frequencies, did you use a spectrum analyzer?

Not necessary. The oscillator Tune modulation depth is only 1.00 = a semitone. That's all you need to switch between minor, major and half-diminished chords.

[Urs]

Is it possible to type in specific values at the top?
Also, is it possible to change Envelopes so that you can enter time in ms rather than the percentage?

You can type values if you enable Key Control (between Scope and Undo on the top).

However, at this point there's no conversion between the raw parameter values and times, also as they are interdependent. Like, Decay time gets shorter as Sustain gets higher.

[Andreya_Autumn]

Speaking of values... The Sync oscillator FX depth control is pretty strange. A value of 25 = 5x follower frequency it seems. And 2x/an octave up is 6.26. So, some kind of log scale, which makes sense. But why not semitones I wonder?

[Andreya_Autumn]

Also, lemme humbly join my voice with those who dislike having to hold shift before clicking to fine-tune a param.

The idea was good! But I think the other behavior is so common in other plugs that re-adjusting becomes a bigger nuisance than the problem it was trying to solve IMO.

[Urs]

I'd love to change it, but it is not a quick fix.