Zebra 3.0 released

[pdxindy]

Is it possible or will it be possible to make skins or themes?

Yes, it is possible... and relatively easy.

[yp1]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Ok, I get that... super hard to reliably do.

What we could do and what I've been thinking for a while is to add copy to the graph output to maybe copy the waveform and be able to paste it into the osc. This would only be an approximation though, just like importing single cycle waveform from .wav files.

Yeah, I realized at some point that something like this would also address my question from the
Zebralette thread. That idea of a "resampling workflow" for Curves actually inspired me to build something: Curve Sampler, a plugin that converts incoming audio into Zebra(lette) 3 style curves.

Here (https://github.com/alexandernutz/curve-sampler) it is. (Hope it's ok to mention it here, lmk if not and I can delete or move it.)

Synopsis: Curve Sampler is a VST3/CLAP that's basically an oscilloscope and spectrum analyzer with "capture to curve" buttons for each. One can put Curve Sampler into any audio chain, and it will extract the current single cycle into a Zebra 3 SVG curve — which can be directly pasted into the Zebra 3 editor. The width of the single cycle is determined either by incoming MIDI notes, or by manually setting a frequency.

Don't expect a surgical tool (afaiu it's theoretically impossible to "un-render" such a waveform). I see this as a playground to experiment with this format.

There is also Curve Jumbler, which provides some curve transformations as a simple web app — have a look if you like (https://alexandernutz.github.io/curve-sampler/). (It's a bit less polished than Curve Sampler, but no installation needed. If there's interest, I'm happy to improve it too.)

Also, I'm not trying to be annoying to the u-he devs by "hacking" into their fresh interface — lmk if I am, I can try to adjust things.

Anyone curious, please try it out — feedback very welcome!

[Matty686]

Congratulations Urs
I am so happy for you. If Im correct in guessing this is your life's work
I think the way you approach MSEGS is amazing and the idea of vector wavetables combined with these had me so interested. I love that the MSEGS have an attack and release knob because one day I can use velocity and release velocity to modulate these (when release velocity is finally available)
also I love how nothing retains internal preset names this means I don't have to OCD about weird names in my patches. I know some people like the names of the oscillator presets they use to show up but after a wile it becomes a nightmare especially if you don't have the preset being refreanced anymore because you deleted it or changed it. I think the way you handle module preset loading is awesome because it just copys the preset you select and dosent show a name this in my mind is one of the coolest improvements over other synths.
I also love that the presets that come with zebra 3 actually sound like things I could use in a song

[Genetic_Junk]

I've been enjoying learning Zebra3. Still have lots of exploring to do with the oscillator module. I made a keys/pad patch and rendered some midi noodling with it: https://supercooltunes.com/wp-content/u ... Osc-li.mp3

[tribalogical]

Truly a blow to all of us who are deeply vested in NI's ecosystem. Here's hoping they manage to pull through at least mostly or somewhat intact.

In any case, thank you for all your hard work on Zebra 3, Urs, and congratulations to you and the team for finally getting it out there. I have to say, it was definitely worth the wait. Cheers!

[ edited to correct my ever-ubiquitous typos ]

[tribalogical]

To aMUSEd:

For some reason, I couldn't reply directly to your post (without going private). Just wanted to say thank you for the "Zebra 3 NKS" bundle.

I haven't installed it yet, but I suspect (and hope) it maps those four CTRL knobs, at the least. I use a KK 61 Mk2, and that's the main thing I wanted immediate control over. Especially for Howard Scarr's patches where he makes incredible use of them. Anyway, thanks again for posting that.

Cheers!

[Sound_Trace]

quick patch question- what would be the best way to implement a (random) sequential switch/shift register/hocket device between four voices in zebra 3? it feels like a job for the Mappers but can't quite see how best to implement this- so you could randomly cycle through activating four voices independently.

[Urs]

Hocketing is really something you do if you have a single source off notes and you want to distribute it across multiple voices. Polyphonic synths do this automatically for you, by iterating through the voices for each note.

If you want four voices to sound different, Mappers are indeed meant to help you here. Set them to 4 steps ans "iterate" with no mod source selected, and you can have different values every note (repeating after the 4th) to map onto various parameters.

So unlike a modular synth where you'd take Intellijel "Shifty" or sth to iterate a sequence through 4 absolutely different voices, you iterate through the same voices, but use Mappers to implement differences.

[aMUSEd]

To aMUSEd:

For some reason, I couldn't reply directly to your post (without going private). Just wanted to say thank you for the "Zebra 3 NKS" bundle.

I haven't installed it yet, but I suspect (and hope) it maps those four CTRL knobs, at the least. I use a KK 61 Mk2, and that's the main thing I wanted immediate control over. Especially for Howard Scarr's patches where he makes incredible use of them. Anyway, thanks again for posting that.

Cheers!

Thanks. I had to be selective of course, I did make an attempt to map all the modules at first but when it got to over 50 user pages and not even half done I knew it was time to give up. So I mapped the params I turn to when I want to play it live, so of course the CTRLS come first Then the morphers and OSC FX, Then filters. Finally a selection of modules, couple of Modals, combs but I suspect most people will just use the first couple of pages, as will I most of the time

[maxchristensenaudio]

I'm doing my 1st live stream with Observant Sound to check out the new eagerly awaited Zebra 3 synth from U-HE
Join me as I dive into the new modules and oscillator engines to design some patches from scratch in real-time. Let's find out together if this is a worthy successor to my favorite synth ever!

When: Sunday, May 10th
Timezones:
• 14:30 (Berlin / CEST)
• 13:30 (London / BST)
• 08:30 AM (New York / EDT)
• 05:30 AM (Los Angeles / PDT)

Where:

[Andrei Marchenko]

I know that here most of you a so excited about new interface but it's still a big grey spot. I have a great idea about Zebra 3 UI — why not to use Plugmon's work as a reference? Guy literally create a future vision of the product.

https://plugmon.jp/product/neumann-pro

You don't need to be a designer to understand simple rules of color theory. In my daily work I don't trust AI much but for UX standards of accessibility it can be used for sure:



P.S.: No hate here. I still can't understand why Zebralette 3 UI ignored and not re-used in Zebra 3.

[Urs]

Funnily, our own attempt at scoring with AI yields 98/100. Just tells you what you want to hear.

[machinesworking]

I know that here most of you a so excited about new interface but it's still a big grey spot. I have a great idea about Zebra 3 UI — why not to use Plugmon's work as a reference? Guy literally create a future vision of the product.

https://plugmon.jp/product/neumann-pro

You don't need to be a designer to understand simple rules of color theory. In my daily work I don't trust AI much but for UX standards of accessibility it can be used for sure:



P.S.: No hate here. I still can't understand why Zebralette 3 UI ignored and not re-used in Zebra 3.

I'm curious though, did you put any other complex audio instrument plugin though this engine? also what is the website or app you used to get this score? To me the best GUI for a complex plugin is Pigments, and even though I love it, the worst is probably Falcon.

[VitaminD]

I know that here most of you a so excited about new interface but it's still a big grey spot. I have a great idea about Zebra 3 UI — why not to use Plugmon's work as a reference? Guy literally create a future vision of the product.

https://plugmon.jp/product/neumann-pro

You don't need to be a designer to understand simple rules of color theory. In my daily work I don't trust AI much but for UX standards of accessibility it can be used for sure:



P.S.: No hate here. I still can't understand why Zebralette 3 UI ignored and not re-used in Zebra 3.

I'd be more interested in how it came to those values. Is it tuned based on some other human's subjective likes and dislikes? (likely a huge yes)

The machine isn't the aribiter of good and bad. It's dangerous times when we try to use them as definitive answers.

[Urs]

I'd recommend to accompany the screenshot with the actual user guide, so the AI gets to know about key commands, mouse interaction, UI sizes, visual hints, colour concepts etc.

Claude 4.6 for instance has this verdict:

"Aesthetics

The dark colour scheme with muted blues and purples is tasteful and avoids the garish neon look of many competitors. The knob rendering is clean — they appear to be simple round knobs with visible position indicators, no unnecessary skeuomorphism. The colour coding in the module palette (red for oscillators, blue-green for physical modelling, pale blue for filters, warm tones for manglers) provides useful categorical grouping. The overall visual language is restrained and professional — it conveys "serious tool" rather than "flashy toy," which aligns well with the target demographic.

Summary Verdict

The UI is a sophisticated, information-dense design that rewards investment. The main grid routing concept is excellent and the three-column layout is sound. The primary risks are in discoverability for new users (the modulation assigner bar, the editor bar tab proliferation, the multi-layered navigation) and in legibility at default sizes (label contrast, small text on rack panels). For the existing u-he audience — experienced synthesists who will read this guide — it works well. For younger or more casual users, the learning cliff is steep, and the UI offers little in the way of progressive disclosure or guided entry points."

This is in line with our goals, which is to make an interface that is not dumbed down just for the sake of quick sales. We will eventually provide educational videos and content, and this will do the trick in the long run, encourage people while keeping the workflow streamlined for people who actually want to go all in.