Zebra 3 Public Beta (final beta)

[jtsterays]

I absolutely love Zebralette 3 and so this is just amazingly satisfying to faff around with. Yet to encounter any major issues although the "Burn" module tanks my CPU instantly. Must be awesome but I wouldn't know

Never used Zebra before so routing questjon: how do I actually change the routing of oacillatora/filters etc? And what is the logic which governs how routing is predetermined? I assumed each lane would just run in parallel unless I changed this but that doesn't seem to be the case, I instantiate a new filter into lane 2 and oscillators in lane 1 are prerouted into it. Help!

Anyway, i wish I hadn't demoed it because it's going to need buying. Do we know how long the intro offer lasts?

The burn function is to burn your CPU, so no sound change. It's there for technical reasons.

[Urs]

We were gonna post video about the CPU Burner, but I messed up and we have to do another take next week.

[swilow11]

I absolutely love Zebralette 3 and so this is just amazingly satisfying to faff around with. Yet to encounter any major issues although the "Burn" module tanks my CPU instantly. Must be awesome but I wouldn't know

Never used Zebra before so routing questjon: how do I actually change the routing of oacillatora/filters etc? And what is the logic which governs how routing is predetermined? I assumed each lane would just run in parallel unless I changed this but that doesn't seem to be the case, I instantiate a new filter into lane 2 and oscillators in lane 1 are prerouted into it. Help!

Anyway, i wish I hadn't demoed it because it's going to need buying. Do we know how long the intro offer lasts?

The burn function is to burn your CPU, so no sound change. It's there for technical reasons.

Oh well in that case, it works perfectly

Can you expand on that though- or should I just rtfm??

[swilow11]

I would definitely not have a large, persistent routing section carving out the middle vertical third of the screen.

Then it's not Zebra anymore.

Finally it's 2025, sliders should be banned from Envelope UIs in modern sound design synths!!!

Hell no!

I dunno, I came up on synths with sliders and you just have to listen to get where you want to go. But for what I'm doing, typically very tight, strictly timed psytrance bass, being able to define envelope parameters as per project tempo or just temporally is super helpful. Not essential and I could use an MSEG but these are too special and useful to use on just a basic pluck. I really like being able to see the modulation shape too.

Questuon: can we slew/bend envelope curves?

Another questjon: Zebralette 3 has the ability to disable/enable drift- is this possible in Zebra 3?

Eh another question: what is the logic which governs how the pitches modules are assigned? Can I reassign them?

[jtsterays]

I absolutely love Zebralette 3 and so this is just amazingly satisfying to faff around with. Yet to encounter any major issues although the "Burn" module tanks my CPU instantly. Must be awesome but I wouldn't know

Never used Zebra before so routing questjon: how do I actually change the routing of oacillatora/filters etc? And what is the logic which governs how routing is predetermined? I assumed each lane would just run in parallel unless I changed this but that doesn't seem to be the case, I instantiate a new filter into lane 2 and oscillators in lane 1 are prerouted into it. Help!

Anyway, i wish I hadn't demoed it because it's going to need buying. Do we know how long the intro offer lasts?

The burn function is to burn your CPU, so no sound change. It's there for technical reasons.

Oh well in that case, it works perfectly

Can you expand on that though- or should I just rtfm??

Urs explained it somewhere in the Zebra 3 thread (u-he sub). Something to with performance cores, like turning burn on so the built in CPU meter is more accurate.

[jtsterays]

We were gonna post video about the CPU Burner, but I messed up and we have to do another take next week.

I watched a guy first time trying Z3, he turned Burn on and said the sound (DAW crackling) is cool. I think the Burn name and fire GUI is too deceiving. You guys should change it to make it look more technical & obvious.

[Urs]

I absolutely love Zebralette 3 and so this is just amazingly satisfying to faff around with. Yet to encounter any major issues although the "Burn" module tanks my CPU instantly. Must be awesome but I wouldn't know

Never used Zebra before so routing questjon: how do I actually change the routing of oacillatora/filters etc? And what is the logic which governs how routing is predetermined? I assumed each lane would just run in parallel unless I changed this but that doesn't seem to be the case, I instantiate a new filter into lane 2 and oscillators in lane 1 are prerouted into it. Help!

Anyway, i wish I hadn't demoed it because it's going to need buying. Do we know how long the intro offer lasts?

The burn function is to burn your CPU, so no sound change. It's there for technical reasons.

Oh well in that case, it works perfectly

Can you expand on that though- or should I just rtfm??

Urs explained it somewhere in the Zebra 3 thread (u-he sub). Something to with performance cores, like turning burn on so the built in CPU meter is more accurate.

Short version:

- under the u-he logo is the Module Performance Meter
- it measures the CPU usage of all modules to help optimise presets or benchmark things
- on asymmetric CPUs with efficiency cores and performance cores, one will want to always render on performance cores
- otherwise CPU measurements are not comparable
- Burning CPU forces the plug-in to be run on performance cores

[Urs]

We were gonna post video about the CPU Burner, but I messed up and we have to do another take next week.

I watched a guy first time trying Z3, he turned Burn on and said the sound (DAW crackling) is cool. I think the Burn name and fire GUI is too deceiving. You guys should change it to make it look more technical & obvious.

Yeah... maybe also we drop it, dunno...

[jtsterays]

We were gonna post video about the CPU Burner, but I messed up and we have to do another take next week.

I watched a guy first time trying Z3, he turned Burn on and said the sound (DAW crackling) is cool. I think the Burn name and fire GUI is too deceiving. You guys should change it to make it look more technical & obvious.

Yeah... maybe also we drop it, dunno...

Chuck it in the performance meter, seems appropriate.

[EvilDragon]

Yup that's a good idea, it should be a checkbox in the perf meter, seems a lot better there, it's more contextual.

[Urs]

Questuon: can we slew/bend envelope curves?

Yes, using the Feedback modifier or having the new modulate itself.

We might add some kind of slope control. Not sure yet.

Another questjon: Zebralette 3 has the ability to disable/enable drift- is this possible in Zebra 3?

Zebra 3 has Calibration in the Pitches modules instead. More control.

Eh another question: what is the logic which governs how the pitches modules are assigned? Can I reassign them?

Any module that takes pitch information (Oscillators, FMOs, Modal Resonators, filters etc...) has a drop down where you can assign one. By default all modules take Pitch from Pitch 1, and all other Pitch modules inherit their setting from Pitch 1 too.

One can do crazy good things with this, from very vibrant and alive oscillator detuning patterns to live playable arpeggios.

[Urs]

Chuck it in the performance meter, seems appropriate.

Yep, very good idea.

It ended up in the FX section because it was effortless to put it there, when it was meant to be a temporary module to debug things. Then we added the performance meter, giving it new purpose, but we didn't think as far as to simply put it elsewhere

[kraster]

I would definitely not have a large, persistent routing section carving out the middle vertical third of the screen.

Then it's not Zebra anymore.

Finally it's 2025, sliders should be banned from Envelope UIs in modern sound design synths!!!

Hell no!

I dunno, I came up on synths with sliders and you just have to listen to get where you want to go. But for what I'm doing, typically very tight, strictly timed psytrance bass, being able to define envelope parameters as per project tempo or just temporally is super helpful. Not essential and I could use an MSEG but these are too special and useful to use on just a basic pluck. I really like being able to see the modulation shape too.

Questuon: can we slew/bend envelope curves?

Another questjon: Zebralette 3 has the ability to disable/enable drift- is this possible in Zebra 3?

Eh another question: what is the logic which governs how the pitches modules are assigned? Can I reassign them?

In the pitch page you can set drift per pitch module under the calibrate setting and select to decalibrate.

The pitch modules appear in each oscillator and filter just select it in the drop down.

So each of the four main oscillators and filters can have their own individual drift, vibrato glide, pitch modulation, key tracking, fine tune, scale quantize.

[Touch The Universe]

I happen to find the auto up and auto down to be unique. I love the results. Thanks for that. Hopefully you also have quantize in there to that can glisten up the pitch in scales or what not - glide up - bot only harmonically relative to the notes gliding. Imposcar something like that and I "think" that iis what is going on, though not sure.

[Touch The Universe]

Unison has spread. Can Filters have spread amongst a layer with unison? <-- lush 101 has this and it's gorgeous, especially with high resonance. The spread essentially generates four or however may unison layers streams of filter position relative to the global filter positon - with highest resonance and sweeping - of course can add formant like quality. I'd be happy to make a video what I mean.