Zebra 3 feature suggestions

[axb312]

Nor would Serum's way of visual modulation (because Urs dislikes it).

It's not that I dislike it. I would love it, if it worked.

The problem with "balls in orbit" around the knobs is that they simply move too fast and the refresh rate of the screens is too low. Because slow modulations are never a big deal, the important (fast) ones become "invisible" due to erraticly jumping dots, or envelopes which may result in a little twitch or not. All you're left with is "oh, this knob gets modulation and that knob does, but I can't really see what's actually happening". In case of which a simple non-jumping indicator is simply enough.

The best visualization is a scope view which provides a history for the modulation in question. That way one can actually see what the modulation looks like. Unfortunately, this doesn't fit next to the knobs. It needs an extra space in the UI and it needs to be an optional view. It also adds CPU impact to the UI, but unlike balls in orbit, it can be disabled. Because, balls in orbit cost CPU too, and often not just a little.

I love the idea of a scope and being able to visualize what exactly is happening to the waves. Great but perhaps not essential.

I am sure you will think of something great UI wise to be able to tell which parameters are being modulated when a modulation source is selected, not necessary jumping dots .

And yes, Evildragon got it right. I would like to see a complete list of all the modulation sources and targets or perhaps even a flowchart of sorts.

[EvilDragon]

A flowchart in a semimodular synth is bound to create even more confusion than just going by the way Zebra is designed

[ojggaspar]

Hello there!

Would it be possible to make Zebrify accept multi-midi channel input support (like Zebra) for a wider range of midi mapping capabilities?

[xx JPRacer xx]

The best visualization is a scope view which provides a history for the modulation in question. That way one can actually see what the modulation looks like. Unfortunately, this doesn't fit next to the knobs

Maybe you could provide an option to right-click a knob and select "visualize modulation in audio scope" for audio-rate modulation?

[EvilDragon]

Right-click option like that would only work in VST3, but not VST2.

[Urs]

Right-click option like that would only work in VST3, but not VST2.

? Why?

[Urs]

Hello there!

Would it be possible to make Zebrify accept multi-midi channel input support (like Zebra) for a wider range of midi mapping capabilities?

Zebrify accepts MIDI CC on all channels. You have a range of 2000+ mappings.

[EvilDragon]

Right-click option like that would only work in VST3, but not VST2.

? Why?

I thought VST2 has nothing defined for right-click behavior so DAW takes that over, whereas in VST3 you have a clearly defined right-click callback, or something to that extent? At least I'm seeing differences in behavior between the same plugin that is VST2 vst VST3, in Reaper.

[Urs]

We do our own right-click stuff in every format. Some offer additional host features though, afaik.

[EvilDragon]

Gotcha. Sorry for misinformation then

[Uggy]

Hello !
Here is 2 features I would like to find in Zebra 3, and why not in a futur update of Zebra 2 since its QoL changes

- Multiple audio output (choose a target output for each lanes, be able to polish different parts of a patch separatly in the host is invaluable for me)
- Stack tune feature like I saw in Diva. Its quite different from the voice/detune options in the OSC modules.

[pdxindy]

32 voice option...

[EvilDragon]

Yes 32 voices would be splendid

[Hanz Meyzer]

Just Hive's unison engine with that fancy mipmap feature or what was it

[ojggaspar]

Hello there!

Would it be possible to make Zebrify accept multi-midi channel input support (like Zebra) for a wider range of midi mapping capabilities?

Zebrify accepts MIDI CC on all channels. You have a range of 2000+ mappings.

HI! Well, Zebra is limited to 1023 CCs (although it truly accepts multi-midi input channels and works wonderfully). But Zebrify only accepts midi channel 01. At least in Ableton and Cubase only midi channel 01 is recognized regardless of the real midi channel number, which only enables 127 CCs. How can I do it then?
Thank you.