Zebra 3 final final beta 21764 April 14

[loctune]

...
The MSEG animation does not look good and doesn't really serve a lot of visualization purposes by itself... If time is a concern I'd highly recommend simply removing it from the UI element.
75c09c44-b250-4fac-ba83-2026c8c9e6c6.png
...

It's very preset dependent. There is indeed a lot of presets using the MSEG to modulate parameters in a more complex manner. It helps understanding the patch in my book. Your screenshot is showing the "default mseg curve". There is also an option inside the preferences where you can set mappers and mseg rack modules not to be shown. Cheers!

I have no issue with the modules, it’s only the animation UI on this MESG:

1) has been squeezed too much that it doesn’t look good anyway
2) only shows the basic shape so it can’t provide enough useful information from a glance
3) cannot be used to edit the curve directly so does not provide additional functionality

I would personally think the MSEG module from the last beta serves a better purpose as a UI element since it allows for users to manipulate the curve directly and see the curve in a clearer way. It’s cool to show the advanced controls but the curve itself should still be the heart of MSEG and the most important thing for users… Maybe it’s possible to put the knobs to the right and make more room for an editable curve display?

[pdxindy]

It's very preset dependent. There is indeed a lot of presets using the MSEG to modulate parameters in a more complex manner. It helps understanding the patch in my book. Your screenshot is showing the "default mseg curve". There is also an option inside the preferences where you can set mappers and mseg rack modules not to be shown. Cheers!

Since the editable curve was removed for the MSEG's, I don't use the MSEG module anymore. I'd rather just hide the MSEG modules from the modulator lane. However, I do like adjusting the Mappers there. So for the future, please add the preferences options:
Show Both
Hide Both
Hide MSEG's
Hide Mappers.

[Urs]

(uh... I thought we had that... apparently not...)

[Muryx]

Unter MacOS 15 in Logic Pro ARM Version hat oft unter "Perform" der "Transpose" bei mir keine Wirkung. Leider kann ich nicht reproduzieren woran das liegt. Das passiert oft bei eigenen Patches. Wenn ich das Projekt speichere und wieder öffne bleibt das Problem. Erst nach dem Init vom Patch oder Zebra als Instanz entferne und eine Neue erzeuge, geht es dann wieder.

Wenn ich den OSC in FMO route bei der Einstellung "Dry" klingt jeder Tastenanschlag anders, dass ich auch im Scope sehen kann. OSC ohne FMO verhält sich normal und OSC ohne FMO auch normal. Wobei ich beim FMO keine Modulation eingestellt habe, lediglich den Input auf 100, mehr nicht. Sobald ich Modulation reindrehe, ist der Effekt nicht mehr so stark, aber immer noch vorhanden. Wollte ich nur erwähnen, falls das nicht so sein sollte, wie beschrieben.

----

On macOS 15, using Logic Pro ARM, the "Transpose" option under "Perform" often has no effect for me. Unfortunately, I can't reproduce the cause. This frequently happens with my own patches. If I save and reopen the project, the problem persists. It only works again after initializing the patch or removing the Zebra instance and creating a new one.

When I route the oscillator in FMO with the "Dry" setting, each keystroke sounds different, which I can also see in the scope. The oscillator behaves normally without FMO, and vice versa. I haven't set any modulation in FMO, only the input to 100, nothing more. As soon as I enable modulation, the effect is less pronounced, but still present. I just wanted to mention this in case it's not as described.

[johnnyberrygoode]

Unter MacOS 15 in Logic Pro ARM Version hat oft unter "Perform" der "Transpose" bei mir keine Wirkung. Leider kann ich nicht reproduzieren woran das liegt. Das passiert oft bei eigenen Patches. Wenn ich das Projekt speichere und wieder öffne bleibt das Problem. Erst nach dem Init vom Patch oder Zebra als Instanz entferne und eine Neue erzeuge, geht es dann wieder. Bei Zebralette3 taucht das Problem nicht auf.

Wenn ich den OSC in FMO route bei der Einstellung "Dry" klingt jeder Tastenanschlag anders, dass ich auch im Scope sehen kann. OSC ohne FMO verhält sich normal und OSC ohne FMO auch normal. Wobei ich beim FMO keine Modulation eingestellt habe, lediglich den Input auf 100, mehr nicht. Sobald ich Modulation reindrehe, ist der Effekt nicht mehr so stark, aber immer noch vorhanden. Wollte ich nur erwähnen, falls das nicht so sein sollte, wie beschrieben.

----

On macOS 15, using Logic Pro ARM, the "Transpose" option under "Perform" often has no effect for me. Unfortunately, I can't reproduce the cause. This frequently happens with my own patches. If I save and reopen the project, the problem persists. It only works again after initializing the patch or removing the Zebra instance and creating a new one. The problem doesn't occur with Zebralette 3.

When I route the oscillator in FMO with the "Dry" setting, each keystroke sounds different, which I can also see in the scope. The oscillator behaves normally without FMO, and vice versa. I haven't set any modulation in FMO, only the input to 100, nothing more. As soon as I enable modulation, the effect is less pronounced, but still present. I just wanted to mention this in case it's not as described.

About fmo. Try in the oscillator that you send to the fmo, switch the phase to "reset", because the signal from the fmo (if you haven't touched any parameters anymore, then it should be a pure sine wave) is added to the signal from the oscillator and in the "random" phase mode, with each new note, the signal will always be different.

[Muryx]

About fmo. Try in the oscillator that you send to the fmo, switch the phase to "reset", because the signal from the fmo (if you haven't touched any parameters anymore, then it should be a pure sine wave) is added to the signal from the oscillator and in the "random" phase mode, with each new note, the signal will always be different.

Thanks

[bartoszkwiecinski]

Hey Urs and the entire u-he team,
thanks for making such beautiful plugins and finally letting Zebra loose into the wild world of freedom!
I'm not sure if this is the right place to ask, and I couldn't find any relevant information in the manual either.
How do I see which wavetable is selected in a preset? When I press OSC I can see the wavetables, but I can't figure out which one is currently selected.
Kind regards

[Milkman]

Im happy to say Ive learned about howard scarr through Z3. Ive become such a fan of the existing presets that I began doing internet searches on the names of the sound designers listed in the UI so I could learn a bit more about them. You guys have worked with some fantastic sound designers, and this helped me expand my knowledge of that community of artists! Thanks.

[leclebau]

Hello,

Possible bug:

I'm working on Windows 11 with Reaper and an Arturia KeyLab 88. From time to time (not constantly, but regularly), I get a stuck note.

The only way to fix it is to change the patch.

I don’t experience this issue with other synths.

[exmatproton]

Found this a bit strange;

Pitches.jpg

Is there a reason for that border around PITCH1? I have PITCH1 and PITCH2 in use...i am not sure why that border is there..it is not 'selected' or something..

[Urs]

I think it's because it's the main one that all others refer to.

[exmatproton]

I think it's because it's the main one that all others refer to.

okay

[Paragonfx]

When I open a project in Bitwig, the fader positions for the mod wheel and Macros A - D are set to zero. This happens with both VST3 and Clap.

[Milkman]

Hello,

Possible bug:

I'm working on Windows 11 with Reaper and an Arturia KeyLab 88. From time to time (not constantly, but regularly), I get a stuck note.

The only way to fix it is to change the patch.

I don’t experience this issue with other synths.

I second this. Also on windows11. I use a rolling midi / audio buffer (rewind), and have found a stuck, very low note (I think it was like 5-6 octaves below C3, but dont recall the actual value) 1 or 2 times now. Ive also heard a stuck note, did not find "midi panic", and so I also just switched preset to kill it.

This has happened maybe 2 times. Ill watch for more details if it happens again.

[sarmad5]

Hey Urs and the entire u-he team,
thanks for making such beautiful plugins and finally letting Zebra loose into the wild world of freedom!
I'm not sure if this is the right place to ask, and I couldn't find any relevant information in the manual either.
How do I see which wavetable is selected in a preset? When I press OSC I can see the wavetables, but I can't figure out which one is currently selected.
Kind regards

I'm not from u-he, but until they respond, maybe this can help. When you click on an OSC, you'll see the OSC page below. You'll see a small downward-pointing arrow on the selected wavetable. Turning the Curve Morph knob moves the arrow head (or playhead) allowing you to select different wavetables.