Zebra 3 Public Beta Revision 20399

[stippenstoh]

I never used the internal reverb in Zebra2 as I always preferred my go-to external ones. So I automatically turned off the reverb in Zebra3's presets until I found that the internal one actually sounded better in some cases.

Is Zebra3 reverb (much) different to Zebra2?

[Urs]

I never used the internal reverb in Zebra2 as I always preferred my go-to external ones. So I automatically turned off the reverb in Zebra3's presets until I found that the internal one actually sounded better in some cases.

Is Zebra3 reverb (much) different to Zebra2?

The Classic mode in Zebra 3 is very similar to NuVerb in Zebra 2, but not 100% the same.

[Urs]

Any chance we have dedicated bug report section for Z3 today ?

viewtopic.php?t=626139

[Rnaroth]

OMG, This is a life saver. Thank you!

Z3-save.jpg

[Matty686]

after a couple of hours of playing with this awesome update; here are my first 2 cents;



-16 voices -> 32 or 64

-Ctrl a,b,c,d -> make them visible to the daw for automation

-Ctrl a,b,c,d -> make 4 more (a,b,c,d,e,f,g,h)

-add a hard limiter (with on/off switch) before the output

-pitches -> add a quantize option 'post everything' so that modulation gets quantized as well (fun stuff)

-pitches -> calibration; add an extreme knob (times 10, or 100) for more effect

-fx -> make it possible to collapse the fx ui's, a la bitwig (et al)

Yah I need access to the Ctrl settings ion daw automation for my workflow two I am using Bitwig and feel this is a necessity

[ThoughtExperiment]

Just to be clear on CPU usage - Urs' original post waaay back on page1 mentioned 'no multicore support yet'. That seemed clear enough to me then, but somewhere along the way I read a post which mentioned something about utilising DAW multicore support? Up to now, I've been assuming that by the final release we'll have multicore support and the one or two patches which crackle (slightly) on my PC (Ryzen 5, 3.7GHz, 32GB RAM) will probably no longer crackle. Am I right to assume that or should I regard those patches as the outer limit of my CPU power?

Nah..i was talking about multiple instances (or, i meant using multiple instances). The context was adding 16 more voices to Z3.

Ok, thanks for clearing that up. I'm not ready to build another PC, this one's only about a year old

[ThoughtExperiment]

Just to be clear on CPU usage - Urs' original post waaay back on page1 mentioned 'no multicore support yet'. That seemed clear enough to me then, but somewhere along the way I read a post which mentioned something about utilising DAW multicore support? Up to now, I've been assuming that by the final release we'll have multicore support and the one or two patches which crackle (slightly) on my PC (Ryzen 5, 3.7GHz, 32GB RAM) will probably no longer crackle. Am I right to assume that or should I regard those patches as the outer limit of my CPU power?

We internally have a multicore option, but it has been glitchy. We'll make it available once and if we can unglitch it.

However, many of the modules (and presets!) will be further optimised.

Also, I have recorded a video today about optimisation and the built-in tools, but I don't think it'll be ready before Monday/Tuesday.

Thanks Urs, I can wait - as I said, it's only a couple of patches that make my CPU writhe a little

[viraven8]

Can there please be a faster way to remove modules in the center routing section?


Also Zebralette3 allows for deleting curves with the delete button... but not in Zebra3 ? Every time I want to experiment or initialize, I have to right click a bunch of times to fix this.

Every time I Initialize I have to do this, I made my own init patch but it's not as easy to access as simply clicking "init"

would save a TON of time for sound designers/ experimenters

[viraven8]

One Huge disappointment imo:

In Zebralette3, you are limited to only 1 oscillator, so if you want to create a "curve filter" or use spectral distortion along a curve/guide, you must use your only 1 oscillator.


Why doesn't Zebra 3 allow for me to use another oscillator's wavetable to create a curve filter for ANOTHER oscillator? This was something I was expecting when I was demoing Zebralette 3, and I'm surprised that Zebra 3 doesn't expand on this.

Everything else is beautiful, I Love Zebra3, but will this feature be added in the future? This would be a HUGE feature for sound design, as I can create my own additive filter without messing up a waveform in another oscillator.

[Lbdunequest]

Zebra 3 sounds really amazing, but man, cpu is quite high even on r9 7950x

[Urs]

Also Zebralette3 allows for deleting curves with the delete button... but not in Zebra3 ? Every time I want to experiment or initialize, I have to right click a bunch of times to fix this.

Turn on Key Control.

[djb123]

Played with it a couple hours today. It sounds great. The synthesis ideas and feature set are amazing even after only a couple hours use. The UI design is so good. This type of design is what I hope other developers try to emulate. This thing took a long time but now that we have it, it's clear why.

[0degree]

bought the update for 30€ without even trying, there's no way i'm not getting that anyway. thanks for the generous upgrade price.

That was pretty much my though process too
But hey, I'm a certified U-he fanboy © anyway

[HelloDave]

Awesome !! are you offering discounts for new reproduceable bugs ?

[pierb]

The Classic mode in Zebra 3 is very similar to NuVerb in Zebra 2, but not 100% the same.

Are there any plans on improving this?

As a sound designer I want to deliver presets that sound as finished as possible. Having better reverb(s) would really help.

I would pay extra for having the whole Uhbik suite inside of Zebra