Zebra 3 Public Beta Revision 20399

Official support for: u-he.com
Locked New Topic
RELATED
PRODUCTS
Zebra Legacy (Zebra2)

Post

This may be a bug or a feature request because I can't tell whether the behavior is intentional or not, so I'll just post it here and hope for the best. It's a bit tricky to explain but I'll do my best.

So I've come to realize that the ModMapper in "Map Smooth" mode basically maps any modulator onto a piecewise linear curve, which is actually incredibly useful. I had previously thought it's the same as "Map Quantize" with some slew limiting (or filtering) applied, which is not nearly as useful, but using the wonderful new Scope viewer has opened my eyes. This way you can have a mod source travel though a number of fixed "stations" while "lerping" in between them. Super cool.

There's a little problem with this though which I'll try to demonstrate with a simple example. Let's say we'd like the modwheel to open a filter all the way in the first half of its travel and then halfway close the filter in the second half. In midi CC terms it's like if we linearly mapped the modwheel range of 0-64 onto 0-127, and the range of 64-127 onto 127-64 (not sure if that helps, but I'll add a picture later). So we'll set the modmapper to Map Smooth with ModWhl as the source, set the number of steps to 3, and then set the first step to 0, the second to 100, and the third to 50 (and obviously modulate filter cutoff with that modmapper). This ALMOST works exactly as I described, except it actually maps the range onto 3 segments rather than 2, with the last segment just outputting the constant value of the last step.

For the following screenshot I set the modmapper source to a rising saw lfo to hopefully make it obvious what the modmapper is doing in the scope. As you can see, in the first third it rises from 0 to 100, in the second third it decreases from 100 to 50, and in the final third it just sits at a constant 50.

Image

What I would have expected (or preferred more accurately) is for the first and last steps of the modmapper to be treated as endpoints of the transfer function, such that if you have n steps there would be n-1 segments. But maybe that's just me! I'm afraid that changing this behavior might make some presets sound a bit different but hopefully it's early enough in development to be acceptable.

As a side note, if the modmath X parameter went higher than 1 you could fix this by multiplying the modwheel by 1.5 and the using that as the source for the modmapper but that's another FR for another post...
Image

Post

I think I did that for a reason, but can't really think of any...

Post

Arguably my suggested behavior would still allow the current behavior because you could always add an extra step with the same value.
Image

Post

Merry Christmas to everyone and thanks U-He for the early present :hug:

Post

Yeah I agree NADs proposal would make more sense. Mapping the first and last values to the start/end of the range.

...oh and yeah. Frohe Weihnachten, gutes neues, und vielen dank fürs alles! :party:

Post

It would be nice if we could change the osc default preset, I dont like the current one.

Post

Urs wrote: Mon Dec 22, 2025 10:54 pm
jasperdunn wrote: Mon Dec 22, 2025 9:15 pm Is there currently a way to change the modulation offset for a knob so that it can go above AND below the base position? Bipolar modulation? I've found this especially useful with LFO modulation.
Yes...?

Can you be more specific, like give an example of what you want to achieve?
https://imgur.com/a/tCWn1jo

As in this picture ^, Alchemy let's you set the LFO to be bipolar so that the modulation goes into the negative and positive values.

Post

I think the visualization simply doesn't show if it's bilpolar, but it actually is bipolar then. Yes, that's not really helpful.

Post

Hello Urs, this may seem strange, but I felt there was a lack of ability to bind the exciter pulse to the keys, so that the height of the pulse would change along with the keys. How do you look at this?
Look at this patch and imagine if there was such an opportunity, what would it sound like?
You do not have the required permissions to view the files attached to this post.
Live and learn forever!

Post

atmelcool wrote: Thu Dec 25, 2025 4:08 pm Hello Urs, this may seem strange, but I felt there was a lack of ability to bind the exciter pulse to the keys, so that the height of the pulse would change along with the keys. How do you look at this?
Look at this patch and imagine if there was such an opportunity, what would it sound like?
I hope that I did not misunderstand you but you can drag they "Key" function onto the "Numbers" from the exciter so you have keyfollow on the numbers of impulses.
Key1.jpg
You do not have the required permissions to view the files attached to this post.
Last edited by Beachboy on Fri Dec 26, 2025 7:21 am, edited 1 time in total.

Post

Could you guys make the Width knob in the Osc module 100 by default instead of 50? A small QoL.
Edit: noise module too.

Post

jtsterays wrote: Thu Dec 25, 2025 5:23 pm Could you guys make the Width knob in the Osc module 100 by default instead of 50? A small QoL.
Edit: noise module too.
Just a suggestion as a workaround: If you put the attached "Default" preset into the Local folder then you have all osc and noise modules set to width=100. You find the Local folder when you go to presets and right click on "Local" and "open folder in explorer (might be similar on Mac). Every time you open Zebra after that it uses that default preset.
Default.zip
You do not have the required permissions to view the files attached to this post.

Post

Beachboy wrote: Thu Dec 25, 2025 6:10 pm
jtsterays wrote: Thu Dec 25, 2025 5:23 pm Could you guys make the Width knob in the Osc module 100 by default instead of 50? A small QoL.
Edit: noise module too.
Just a suggestion as a workaround: If you put the attached "Default" preset into the Local folder then you have all osc and noise modules set to width=100. You find the Local folder when you go to presets and right click on "Local" and "open folder in explorer (might be similar on Mac). Every time you open Zebra after that it uses that default preset. Default.zip
I see, thanks. Looks like I can customize my own default preset.

Post

photo_2025-12-25_20-18-25.jpg
I would like the entire MSEG button field to accept drag-and-drop commands, rather than just the tiny dot/rounded square. Additionally, I'd like the (clicking) dot/rounded square to function as a (for example): 'show MSEG 1 modulation on all visible panels', without switching to the MSEG 1 mini-editor.
You do not have the required permissions to view the files attached to this post.

Post

ffx wrote: Thu Dec 25, 2025 12:33 pm I think the visualization simply doesn't show if it's bilpolar, but it actually is bipolar then. Yes, that's not really helpful.
Yeah that's what I meant, sorry was late at night. It would be nice if the visualisation on the knob showed that it was bipolar.

Locked

Return to “u-he”