Zebra 3 and Zebra Legacy

[Urs]

Also, vacation, Covid, CLAP, birthday parties, vacation and other random obligations have interrupted my flow with Zebra3 for a few months, so I'm currently in the process of figuring out how to get rid of other obligations and back to development.

[Sound Author]

This has probably been discussed on this thread already, but I'm wondering if we will get the spectral oscillator effects right out of the gate. For whatever reason, I hardly ever used them in the past, but I'm finally starting to use them a lot more these days. They really are very useful.

To me a long time as well to grasp their usefulness and I still use probably just a fraction of them. Which of them are you using and for what?

My favorites are "Brilliance" (because you can darken waveforms that are a bit too bright), "Scrambler", "Turbulence", "Scatter", "Exophase" and "Hypercomb".

Turbulence is really cool because there's this movement that's already happening without any modulation that you can control the rate of with oscillator resolution. As per the manual, Turbulence sounds really cool with a small handful of harmonics in SpectroBlend mode.

Also, I love Exophase, which I use to sprinkle weird randomly modulated resonances all throughout the high frequency domain.

[gentleclockdivider]

My absolute favourite osc effects
Pd-phase dist. ..( spectromorph or geomorph mode ) and tiny bit of modulated dx in the second slot ( which is a 2 operator , 1:1 ratio algo) .
Smear effect on a simple sine , and even-odd effect in the second slot , reminds me a lot of my nord modular spectral osc.
THe osc effects are gold

[Urs]

In Z3 they can have more than 1 parameter. I think they'll be extremely powerful.

[TENETfanboy]

I can’t wait to see a first look at the UI, I know the sound will be amazing so I’m almost more excited to see what it looks like

[Urs]

I can’t wait to see a first look at the UI, I know the sound will be amazing so I’m almost more excited to see what it looks like

There are mostly just some mock ups, wireframes and mood pics, nothing final...

The design heavily depends on the tools we're creating, e.g. how much space the large visual editors take up. And those are still, metaphorically and literally, growing.

[Double Tap]

I can’t wait to see a first look at the UI, I know the sound will be amazing so I’m almost more excited to see what it looks like

There are mostly just some mock ups, wireframes and mood pics, nothing final...

The design heavily depends on the tools we're creating, e.g. how much space the large visual editors take up. And those are still, metaphorically and literally, growing.

I’m sure there are practical and commercial reasons why it would be a bad idea. But I’d love to see a “how we designed this synth” behind the scenes documentary, following the process from start to finish.

[_morton_]

I wouldn't want the task of editing 10 years worth of footage

[carrieres]

I wouldn't want the task of editing 10 years worth of footage

[Lyhrus]

I can’t wait to see a first look at the UI, I know the sound will be amazing so I’m almost more excited to see what it looks like

There are mostly just some mock ups, wireframes and mood pics, nothing final...

The design heavily depends on the tools we're creating, e.g. how much space the large visual editors take up. And those are still, metaphorically and literally, growing.

Zebra2/TDZ is in the centre of my DAW, I work with it all day long. And I look at it all day long.

I love the sound, the advanced modular concept, and the clever disposal of modules in the UI, but I'm not a huge fan of the graphical design of the UI (color schemes, 2D vs. 3D layouts, etc.). It's a matter of taste. On u-he's Patch Lib we can find some alternative skins, but they are not very elaborated or over-elaborated IMO.
As for Z3, I either would greatly appreciate some more skin alternatives in different styles created by u-he (as for me, I prefer more plain UIs as the bright one of Massive X. I like UIs with quite low saturated colors and almost no 3D effects. But this is just me!). Or – the best thing – if we could get an extra skin designer tool. I would love to pay for it, it does not have to be for low or nothing!

Again, Zebra is my daily workhorse, I expect Z3 to become the same – and I'm looking forward to it. But is there a way to get the graphical aspects (especially the color schemes) a bit more flexible? I expect working with it for years, so ...

[Mmk41]

Since you are still working on it, I have a few requests regarding the UI.
Would it be possible to have only knobs, faders and menus in the main window? I find it very difficult to work for long periods when the interface is animated. I would love to be able to hide the waveform and filter displays on Hive, for instance.

And I had rather have only one way to add modulators. Either a matrix or modulation slots in the modules, but not both, because you would have to check in two different places to see whether a parameter is being modulated or not.

[Hanz Meyzer]

I have a suggestion: If you publish "Zebra Legacy", why not put everything into one plugin, so there only is one Zebra2 (including all HZ stuff, too)? Or would this lead into backward compatibility issues, due different VST identifier? The ZebraHZ version then could be simply a "loader" of the other plugin, similar to what SymbiosisVST does. I've seen such loader wrappers in wild quite a bunch of times...

[Urs]

Yes, backwards compatibility issues. Some hosts partly identify plug-ins by their file path and executable name.

[pdxindy]

And I had rather have only one way to add modulators. Either a matrix or modulation slots in the modules, but not both, because you would have to check in two different places to see whether a parameter is being modulated or not.

One way to solve that could be a more unlimited mod matrix in terms of total slots and then whenever you add a modulation in the module, it is also visible in the matrix. That way all modulations can be seen in one place (mod matrix) when needed.

[NAD]

Some hosts partly identify plug-ins by their file path and executable name.

That's weird. Does CLAP allow the same freedom for hosts to identify plugins?