Zebra 3 - final beta Rev 21625 April 8th

[ThoughtExperiment]

I took a deeper look into Zebra Legacy these days, and my gut feeling is there are still quite a number of things you can't possibly do in Zebra 3 (yet):

Zebra 3 has only 4 filter slots (although they sound better to my ears) compared to the 4 VCF/2 XMF/8 Diva filters in Zebra Legacy. No notch filter as filter option. All single filter so no SEM style morph/sweep. Zebra 3 also only has linear envelopes and 4 (morphable) MSEGs, so a few things might be harder to do in Zebra 3 as well.

Maybe we'll get there one day...

To be fair, after posting I did go back and open Zebra 2 and played around with the formant filter in there and it wasn't as cool as I remembered it being In fact, I'm pretty sure it's just a crossfade similar to what we have now in Zebra 3. So I might have been talking out my ass on that particular point, although I do stand strongly by my larger point about Guides not being the ideal way to handle morphing of oscillator FX parameters. And I'm definitely surprised more people don't seem to care (yet).

Maybe they don't care because they don't agree with your opinion?

Tautology alert.

Don't think so...

Not a matter of opinion, unfortunately (for you).

Hey, don't get upset about it

[brightonrock]

Hi - I get big volume changes on the init patch when I change from curve geometry to curve spectrum in Osc 1 on the init patch. Has that always been the case? (CLAP version on MacOS). Thanks.

[cvale]

although I do stand strongly by my larger point about Guides not being the ideal way to handle morphing of oscillator FX parameters. And I'm definitely surprised more people don't seem to care (yet).

IMO, the Guides cover most use cases. Much of the time, a single Guide curve is sufficient.

And when morphing is desired, there's the option to use Curves to create complex morphs.

Well, I'm glad it works for you. Each of us can only speak for our personal use-cases. It's one of those things where you obviously won't care about it until you do, which obviously maybe you specifically never will. Of all the concerns people have brought up in this thread, it strikes me as more bizarre than anything that my particular observation has incited such defensiveness. I don't agree with a lot of the other supposed issues that people have brought up here but I am not going to tell them that it's not a problem *for them* just because it's not a problem for me. As for the Guides in specific use-cases, the proposed workarounds are objectively not ideal for reasons I've already mentioned. And Urs himself admitting that the Guides themselves were "tucked on" [sic] is certainly not a glowing endorsement of feature that doesn't warrant some further scrutiny.

But really, I am done arguing about this and won't be responding to future replies about this issue. I have a reasonable point, which isn't invalidated by whatever number of people don't care. You've got people posting about how this or that line shouldn't be there in the UI, but apparently a constructive post about actual functionality is causing a fuss, so you'll pardon me for thinking that's ridiculous. To be clear, I'm not saying you specifically are doing all this, but I just want to conclude my thoughts on this and then if everyone wants to go full KVR on me, that's their prerogative. This is not my first rodeo - I left KVR years ago because of exactly this kind of nonsense. I only reluctantly came back because u-he doesn't have a proper support forum. I knew what I was probably in store for, but this place hasn't changed a bit, unfortunately.

[ffx]

Ouch - so multiple outputs didn't make it into final 1.0? That hurts...

Is it still on the list for later versions? Was there already some develpment here? Thanks.

[trevdog]

i think Mouse Wheel Focus should be set to scroll only by default
scrolling and inadvertently changing parameters when going through modules will frustrate most users i'm guessing.
Otherwise, UI is fine and looking forward to new skins.

[pdxindy]

Hi - I get big volume changes on the init patch when I change from curve geometry to curve spectrum in Osc 1 on the init patch. Has that always been the case? (CLAP version on MacOS). Thanks.

Yes... though it depends on the curve shape. With Spectrum, the curve points that go up to the top can get loud.

[Adminu]

is it possible to order Zebra 3 without VAT ? I am located outside of EU

anybody please ?

[Seafire Mk2]

Have you tried, does it auto recognise your location?

[Adminu]

Have you tried, does it auto recognise your location?

yes, in recognises the location outside the EU, but adds the VAT into price calculation.

P.S. it looks that I've misinterpreted the displayed price due to currency conversion, and VAT is just included in the listed 179EUR price, so my question is not actual anymore.

[Urs]

Hi - I get big volume changes on the init patch when I change from curve geometry to curve spectrum in Osc 1 on the init patch. Has that always been the case? (CLAP version on MacOS). Thanks.

They produce very different results.

It is coincidence that the falling sawtooth that was the default in earlier versions was kind of a similar waveform - the spectrum of a sawtooth looks a bit like a sawtooth, too, but that is a rare exception.

[Urs]

Ouch - so multiple outputs didn't make it into final 1.0? That hurts...

Is it still on the list for later versions? Was there already some develpment here? Thanks.

Yes, we have this functioning to some degree on a branch, but we had to freeze the initial feature set at some point.

[GusGranite]

Apologies of already covered (these threads move fast!) but is there audio input for FX, or plans for a Zebrify style FX unit?

[Urs]

Apologies of already covered (these threads move fast!) but is there audio input for FX, or plans for a Zebrify style FX unit?

That is in the same state as multiple outputs. Same project that we want to get back to once we find the time to do it.

[Urs]

And Urs himself admitting that the Guides themselves were "tucked on" [sic] is certainly not a glowing endorsement of feature that doesn't warrant some further scrutiny.

I think you misread me. I meant that originally the Guides were added to aid some FX in a very experimental and "let's see what it does" way. But it turned out to be pretty good so, in the future we will have some discussion as to where we take it. It just won't happen over night.

[loctune]

It would be nice to say there isn't anything in Zebra 2 that you can't do in Zebra 3, at least.

I took a deeper look into Zebra Legacy these days, and my gut feeling is there are still quite a number of things you can't possibly do in Zebra 3 (yet):

Zebra 3 has only 4 filter slots (although they sound better to my ears) compared to the 4 VCF/2 XMF/8 Diva filters in Zebra Legacy. No notch filter as filter option. All single filter so no SEM style morph/sweep. Zebra 3 also only has linear envelopes and 4 (morphable) MSEGs, so a few things might be harder to do in Zebra 3 as well.

Maybe we'll get there one day...

Closer than you think. There are also filters built into the osc FX, and the Eq's can also behave (are essentially) filters (maybe 6 notch filters if you want)
Envelopes, explore the vary1 and vary2 parameters, vary 2 'feedback' can turn them logarythmic or exponential. MSEGS, you draw them (hint hint)
morpheable: check out the mixers and in4 modules and roll your own.

It seems to me that the mixer doesn’t really do filter morphing, only crossfading between multiple filters. The curve filter osc fx feels like more or less the same thing, plus it’s limited to single osc behavior and cannot be used after say FMO modulation… A morphable SEM style LP-BP-HP filter option in Zebra would be more than welcome.

While the EQ can be used like a filter of any kind, I am also not so sure if it handles cutoff sweeps the same way as filters. I can use this as a workaround, but a notch filter type as option feels more straightforward in the workflow…