Zebra 3.0 released

[pdxindy]

Here's the current state of my custom skin. I'm still slowly tweaking colors. The good news is that it's easier than ever to make a custom skin.

Z3-Skin-1.jpg

You Bitwig-a-tized it!

I considered using the Bitwig orange...

[WouterSpekkink]

After only doing some surface scratching for the past weeks (which was already great and fun), I just used some time to dive a bit deeper into the oscillators, the various osc fx and so on. It is mind blowing. Amazing how you can get complex but pleasant sounds with just an oscillator. I think I spent hours with just an oscillator and some fx and had tons of fun. And then there is still so much I haven't even tried yet. This really is a dream synth.

[Funky40]

However, it's very easy to change the contrast/brightness of the fonts in Zebra 3. Here, I made the labels full white (a single RBGA value change). Took less time than this post.

Z3-Text-Contrast.jpg

This is exactly what i`d like to have !

[Funky40]

Zebra 3 is incredible for noises and inharmonic percussion!!

reading your posts, seeing some of your thinking, remebering how good your very early Zebralette3 Demos already sounded, i *really* whish to see some sound presets / sound packs coming from you !
i mean as is in -> *really* interested in it

I hope you have intentions to share your own sound works with Zebra3 in one form or another


I personally won`t ever dive deep into Zebra3.
It`s above my head. And i have not the time to be so commited to really dive deep into ( while i AM into sounddesign since 25+ years myself / it`s basically where my time goes. Just today is my own focus on the VST-I postprocessing side of the things.....and to dive into the big universe of "live play" morph controls / no time to do everything side by side.....)

[pdxindy]

This is exactly what i`d like to have !

In the Scripts directory, open the file Zebra3_orig.txt in a text editor.

Line 69 is:

COLOUR name='Module-Label White' rgba='ffffff66'

the rgba value is "ffffff66" - the 66 at the end is the alpha transparency hex value. 66 = 40% opacity.

Change the 66 to cc to get 80% opacity
COLOUR name='Module-Label White' rgba='ffffffcc'

Change the 66 to ff for 100% (example I posted was this one)
COLOUR name='Module-Label White' rgba='ffffffff'

Save the file and open a new instance of Zebra 3 and you should see the change.

[Funky40]

This is exactly what i`d like to have !

In the Scripts directory, open the file Zebra3_orig.txt in a text editor.

Line 69 is:

COLOUR name='Module-Label White' rgba='ffffff66'

the rgba value is "ffffff66" - the 66 at the end is the alpha transparency hex value. 66 = 40% opacity.

Change the 66 to cc to get 80% opacity
COLOUR name='Module-Label White' rgba='ffffffcc'

Change the 66 to ff for 100% (example I posted was this one)
COLOUR name='Module-Label White' rgba='ffffffff'

Save the file and open a new instance of Zebra 3 and you should see the change.

Wow, okay, i managed it !
Thank You very much @pdxindy !

it was line 28 here. ( just counting the lines with actual text / no idea what the correct way is)


And: of course is that not my ideal picture of a final appeareance. I mean, i see where the idea with the grey text was coming from. It created a distinguishisation between text of different parts of a module section. I lose that for now. But i can live with that. The text is now "everywhere" clearly visible and readable. I mean, it literally jumps into my face. But i like that better ! It`s not like it would make the whole thing dazzling for my eyes.

Great ! Much Thanks !


edit: ahh, i had "ff", i just switched to "cc". Guess i leave it there for now

[pdxindy]

edit: ahh, i had "ff", i just switched to "cc". Guess i leave it there for now

Glad it worked!!

If there's any other simpler adjustments you want, let me know. I've got most stuff figured out.

[enCiphered]

I can’t find the feature request thread guys, is there one?

Currently, accessing the OSC or MSEG curve editor requires manually clicking the “Editor” tab first. A much faster and more intuitive workflow would be the ability to open the editor directly by double-clicking the curve slot or icon itself.

In practice, when working quickly, I often instinctively double-click the curve I want to edit. Having that action automatically switch to the Editor view and open the selected curve would make the editing feel significantly more fluid and immediate.

I mean double clicking this little icon:


As curve editing is such a central part of the instrument, this small interaction change could have a surprisingly large impact on usability.

Thank you.

[Dalle]

A much faster and more intuitive workflow would be the ability to open the editor directly by double-clicking the curve slot or icon itself.

A double click is already used to set the morph position. It never occurred to me this should or could open the editor so I wouldn't call this intuitive.

[Chalisque]

I love U-He as a developer of synths.
I love the labour of love that has gone into Zebra 2.
I love the Diva filters in Zebra HZ.
I home one day there are the MS20 filters in Zebra 3.
Without them, Zebra 3 is not as much fun.
And Zebra 2/HZ was almost good enough anyway.

Now the fun part.
How to use the free tier of LLM's and basically the art of getting them on a ball of string and having safe fun playing with them.
Music generated by AI is garbage.
But a real artist can, in fact, make art out of garbage.

Anyway, my question is this: WHAT MAKES SENSE?
Reply, and bear in mind that the answer to that question can and likely will vary depending on who is reading it. I just work that way.

If you want to see my professional mathematical qually stuff, ask what you want or need to know (indicate want/need as this distinction is critical). Then I'll tell you which LLM to ask and what to prompt them with. I struggle to communicate. I am autistic, and psychiatric drugs prescribed by force by doctors who didn't understand me, and didn't realise that they didn't understand me (i.e. NOT THEIR FAULT)... yada yada.

p.s. I've had a bit much to drink, but all of the above is genuine so far as I am concerned. I'm not _that_ drunk.

[ThoughtExperiment]

... yada yada....

FTFY

[valdelobo]

Wow! What an Upgrade!
I'm having a great time playing around with the new Z3 Physical modeling capabilities!

I noticed that the Modal component allows to load user-defined csv files.
And they are actually just simple text files with semicolon separated values!

I'm also aware that there are Tools like Loris or Spear that allow to analyze samples to produce a modal definition file.

But I did not find out how to map any of these formats to the Zebra Modal CSV format.
Any ideas how to achieve this kind of mapping?

[cvale]

Wow! What an Upgrade!
I'm having a great time playing around with the new Z3 Physical modeling capabilities!

I noticed that the Modal component allows to load user-defined csv files.
And they are actually just simple text files with semicolon separated values!

I'm also aware that there are Tools like Loris or Spear that allow to analyze samples to produce a modal definition file.

But I did not find out how to map any of these formats to the Zebra Modal CSV format.
Any ideas how to achieve this kind of mapping?

I hate to say it, but this is definitely a job for AI. I haven't used Loris specifically, but I have:
1. Uploaded an example modal .csv file in the format that Zebra 3 expects, and then given it prompts about what type of instrument sound I wanted based on that, with pretty good results.
2. Uploaded spectral data from analysis done with Audacity and had it adapt this to make Zebra 3 modal profiles.
Both tasks were trivial for ChatGPT.

[valdelobo]

Works like a charm! Thanks for your help!

[Funky40]

A very little but special feature request please. Very little:

Zebra3 / top left side / editor select -> | Synthesis | Pitches | Presets. - make "this" CC selectable please ! (one single CC control)
( it would be about host automation, not direct CC mapping to Zebra3. Since that`s how my liveplay host works)



reason:
Zebra3 is the top of the pops of the Synths in my unisverse.
Im doing unbelivably good things with it in my live play host.
And: i CC map ALOTS of things out to HW control.

Not necessarily the parameters itself, just few. But for example:
- open close (GUI)
- bypass
That`s always CC mapped with my instruments ( and with many more plugins in the meantime)


But with Zebra3 would i like to optimise the HW based workflow even deeper down.
People claim that HW wins just alone for its haptics.
This is nolonger true. NOT when compared to my ITB setup, when taking already existing patches as a measure. And this small stuff is one little part of that full deal.