Zebra 3 and Zebra Legacy

[Urs]

Thanks for that. You mean Have or Hive 2? A hive oscillator on my 2016 Dell XPS 13 takes anywhere from 4-6% at 16x unison. Maybe it's the DAW reading?

Dunno, I've got a built-in CPU meter for each algorithm. It's very precise.
...

Can we get it as a modulation source?

LOL, no.

As it uses extra CPU, t's only active in development builds.

(I have thought about using it though, like show the user which parts of a patch are responsible for most CPU consumption, but then we can as well just rate different algorithms for their CPU usage in the user guides)

[Fannon]

CPU usage as modulation source sounds really funny.

But it would be nice as a user to also understand better which parts of the patch design contribute how much to CPU usage. Then you could learn from that feedback to build more CPU efficient patches, if that's your goal. This would work best, if you could see the individual contributions, not just total.

[PieBerger]

CPU usage as modulation source sounds really funny.

I'm not spending another penny with u-he until this gets implemented

[u-u-u]

(I have thought about using it though, like show the user which parts of a patch are responsible for most CPU consumption, but then we can as well just rate different algorithms for their CPU usage in the user guides)

Or maybe make the GUI glow red (and sound distorted) in parts where much CPU is used and make them look (and sound) more worn-out over time. Or moving towards Carbon-neutral music production... if the plugins would report and show how much CPU they burn and the daw does as well it could encourage producers to use more economic algorithms, pay for certificates, plant trees and stuff like this
Reporting CPU-consumption might be an interesting CLAP extension, I guess

Edit: ... of course the energy used for developing, distribution of the software has to be evaluated as well. And playing concerts that support climate projects could contribute to a positive climate karma as well.

[lucassantana]

For Zebra 3 - will the structure of the skins also be different compared to Zebra 2? Because I've a some custom-made skins for Zebra 2 and would hope to port them over to Zebra 3. Thanks!

[Urs]

There'll be completely new user interface elements. The whole UI will be built up from scratch.

[lucassantana]

There'll be completely new user interface elements. The whole UI will be built up from scratch.

Oh geez. Looks like I'll have to start from scratch too then. Haha.

Okay, well thanks Urs for all your hard work! Can't wait for Z3!

[MitchK1989]

CPU usage as modulation source sounds really funny.

especially if you wind up in a situation where the modulation going up increases the CPU load of the patch

[glokraw]

CPU usage as modulation source sounds really funny.

I'd like sales data as a modulation source. The more sales occur, the better the modulation sounds

[glokraw]

Or maybe make the GUI glow red (and sound distorted) in parts where much CPU is used and make them look (and sound) more worn-out over time.

Making the cpu glow red is more fun, and saved on firewood in a recent blizzard

[Tuskerfort]

In zebra 3 would it please be possible to add a slew limiter or utilize the portamento as a mod source?

(Or MSEGs with legato contingent triggering.)

Legato contingent triggering would increase the melodic expressivity of the synth by controlling the timbral transitions between notes.

[Urs]

Set MSEGs to "single" trigger, that should do the trick!

But yes, controlled modulation that spans multiple notes in several ways is something I've become fond of, as for example explored in Hive. I'm sure Z3 will have such concepts, too. One thing I would like to try is glide for velocity, which has been suggested a few times.

[JochenCX3]

One thing I would like to try is glide for velocity, which has been suggested a few times.

Yeeeees!

[Hanz Meyzer]

Tonight I found the wisdom in a bottle of gin. Suddenly I realized what is missing in Zebra currently: Proper visualization. A graph with a bar showing the env and the position. A highlighting bar on any lfo, showing the current position in the LFO shape. a oscilloscope for each osc and the sum. Also compensated for frequency, just like .

And then of course visualization of the attached automation on each control. Like Vital. Basically position indicators everywhere and output visualisation. Even showing the animation of the automation.

[Funkybot's Evil Twin]

I kind of expect, and maybe that's just wishful thinking on my part, that Z3 would include:

1. Hive's scope with drag and drop
2. Hive's drag and drop modulation system and ability to modulate just about anything
3. Some additional modulators from Hive (FG's, Shape SEQ)

I'd also like to see that sort of stuff in a Diva2 someday.