Just like regular guide curves, but you have more morph options.
Zebra 3 Public Beta Revision 20399
-
eclipse_soundlab eclipse_soundlab https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=724571
- KVRist
- 79 posts since 6 Nov, 2024
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
No worries, we're thinking about several concepts. None of these ideas are implemented quickly though.stippenstoh wrote: Sun Dec 21, 2025 1:22 pm Here's a suggestion, taking inspiration from Waveform Pro DAW and Davinci Resolve for video color grading and editing:
In any case, I'm already experimenting with an idea that at least shows if a knob has any modulation. A right-click will then unveil what it is being modulated with, and lets you select that source for editing.
-
- KVRist
- 251 posts since 4 Apr, 2020
Nice!
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
I totally get that, because what we did is highly unusual, but at the same time very simple and efficient.
So, regardless of OscFX, with Curve Morph you can choose the waveform of the oscillator. You set up a couple of waveforms, and then you morph through them just like you would a wavetable. So far so good...
So in the OscFX you have a second (and possibly a third) Curve Morph knob, if the option is set to "Curves" instead of "Guides". It takes the same set of waveforms as the main oscillator, but at a different morph position.
So instead of adding more and more waveforms to edit for more and more options to use them, we have just a single set of waveforms, and you can reuse them wherever and whichever way you want. If you need them to be independent, just take the first half for the oscillator and the second half for the OscFX.
This may look a bit "Uhm, okay..." at first, but it greatly enhances the possibilities without adding much more complexity.
(maybe this would be a good opportunity to as some AI to explain this more clearly... I might do that when I'm in the office later)
-
- KVRer
- 5 posts since 26 Sep, 2024
thank you, thatll do for nowjohanhov wrote: Sat Dec 20, 2025 10:36 pmWorkaround in Bitwig: Insert a MIDI CC device before Zebra 3 and assign CC 2, CC 11, CC 75 and CC 76 to the first 4 knobs.tildesounds wrote: Sat Dec 20, 2025 5:34 pm Not sure if this counts as a bug, but the 4 macro controls are not available as automation parameters to the DAW (Bitwig in my case).
Seems like a pretty massive oversight.
- KVRist
- 152 posts since 4 Oct, 2014 from Russia
In what other position? I think I need a video guide about the device with a visual example. Thank you.Urs wrote: Sun Dec 21, 2025 1:42 pm It takes the same set of waveforms as the main oscillator, but at a different morph position.
You do not have the required permissions to view the files attached to this post.
Last edited by atmelcool on Sun Dec 21, 2025 2:56 pm, edited 1 time in total.
Live and learn forever!
-
- KVRer
- 21 posts since 5 Sep, 2016
Thanks for the tip, Urs. It does work and is easier to setup. Nonetheless: Simple random value in V1 or V2 would be nice...Urs wrote: Sun Dec 21, 2025 11:11 amYou can save a lot of assignments by modulating Stretch or Feedback in the envelopes, which affect all phases.jnchristp wrote: Sat Dec 20, 2025 5:00 pm While programming some sounds in Zebra3, I tried to set up an "analog style" polypatch. It's really easy to use the pitches for pitch-variations, assigning the oscillators to different pitch-sources. Still, I wish there was an equally easy way to do the same thing for envelopes. It's nice to have little variations in envelope-times PER VOICE. At the moment it needs many, many random-modulators or mod-noises to achieve this.
Long story short: Would it be possible to have some kind of randomisation in the envelopes? Maybe as an option under "V1" or "V2"?
I would also usually turn to Mappers set to the same number of steps as there are voices, and "Increment" with no specific trigger source. Then you get repeated patterns by the number of voices.
(I had thought about randomisation in V1/V2, but am still not sure if it makes enough sense... happy to continue the discussion)Indeed, I'm surprised myself since Hive has copy/paste, so I thought we definitely have this here, too. Maybe it didn't fit, I'll ask...Last thing: Would be great if one could easily duplicate a modulation in the matrix and assign the duplicate to a different target...
- KVRist
- 152 posts since 4 Oct, 2014 from Russia
Is it even clear how to separate them? You're a developer and it's clear to you, but I can't grasp the concept of what's connected to what. maybe there is a block diagram?Urs wrote: Sun Dec 21, 2025 1:42 pm If you need them to be independent, just take the first half for the oscillator and the second half for the OscFX.
Last edited by atmelcool on Sun Dec 21, 2025 2:58 pm, edited 1 time in total.
Live and learn forever!
-
- KVRian
- 694 posts since 9 Dec, 2021
Now you mentioned it, I remember being confused when the first Zebralette 3 came out. I think it would be great if they replace the morph knob with the actual curve representation (think Hive's Osc waveform preview). It would be super easy to understand and look cool too.
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
Hehehe, maybe this helps:
You do not have the required permissions to view the files attached to this post.
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
It is literally the same Curves that the oscillator uses, but with an independent control of where in the "timeline" the curve is taken from.
- KVRist
- 152 posts since 4 Oct, 2014 from Russia
Everything in the Hive is very user-friendly and intuitive, it's a cool synthesizer. Zebra is cool too, but I'd like to understand what to turn and why, rather than just tweaking it by guesswork and ear.jtsterays wrote: Sun Dec 21, 2025 2:56 pmNow you mentioned it, I remember being confused when the first Zebralette 3 came out. I think it would be great if they replace the morph knob with the actual curve representation (think Hive's Osc waveform preview). It would be super easy to understand and look cool too.
Live and learn forever!
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
Also, the graph in the background will actually show what the curve used by the FX looks like if you switch the Plot to "FX1", as shown here:
Here, morph is set to like 60%, which corresponds to the position of the sine wave in the default Curve Set. By switching the plot to FX 1, you can see the sine wave in the background graph.
Here, morph is set to like 60%, which corresponds to the position of the sine wave in the default Curve Set. By switching the plot to FX 1, you can see the sine wave in the background graph.
You do not have the required permissions to view the files attached to this post.
- KVRist
- 152 posts since 4 Oct, 2014 from Russia
Got it, thanks.Urs wrote: Sun Dec 21, 2025 3:22 pm It is literally the same Curves that the oscillator uses, but with an independent control of where in the "timeline" the curve is taken from.
Live and learn forever!
-
- KVRer
- 17 posts since 29 Sep, 2016
If it doesn't work, check the CC numbers inside the T-tab behind the cogwheel, and either adjust these or the numbers in the device panel of the midi cc device.tildesounds wrote: Sun Dec 21, 2025 2:30 pmthank you, thatll do for nowjohanhov wrote: Sat Dec 20, 2025 10:36 pmWorkaround in Bitwig: Insert a MIDI CC device before Zebra 3 and assign CC 2, CC 11, CC 75 and CC 76 to the first 4 knobs.tildesounds wrote: Sat Dec 20, 2025 5:34 pm Not sure if this counts as a bug, but the 4 macro controls are not available as automation parameters to the DAW (Bitwig in my case).
Seems like a pretty massive oversight.
