"Neumann" GUI for Zebra²/Zebralette

[aMUSEd]

So Neumann is for Zebra and Neumann Pro for Zebra HZ?

I am using Neumann Pro for both Zebra and Dark Zebra. this skin seems to work for both of them.

What about Neumann? The pro version seems too big but I would like a HZ skin too.

[darkinners]

So Neumann is for Zebra and Neumann Pro for Zebra HZ?

I am using Neumann Pro for both Zebra and Dark Zebra. this skin seems to work for both of them.

What about Neumann? The pro version seems too big but I would like a HZ skin too.

So far the only difference I can tell between Neumann and Neumann Pro is
Neumann Pro layout all 3 lanes(OSC, Mdoluation and Effects) in a single page
Neumann show only 2 lanes (OSC and Modulation/Effects)

So yeah if you think Pro using too much of your screen real estate, you can switch to Neumann
You get Neumann skin too when you purchase Neumann Pro anyways.

[aMUSEd]

So there is also Neumann for HZ?

[robisme]

Yes, it works for HZ, I have it.
Pro is certainly a bit too big, but it's very practical, for exemple, to keep seeing the main modules screen, while browsing presets (gives at a glance which modules are used in this preset).

[Tekkera]

Found this.

When "selected on top" is enabled and the patch has enough modules where it needs to pull it from the bottom, adding a diva high pass filter (zebrahz obviously) will brick the vst and daw? Tested only in FL Studio 20, nowhere else yet but the behavior is consistent on my machine and does NOT occur in the included default zebrahz skin.

Steps to repeat
0) load zebraHZ w/ neumann pro
1) enable selected on top for the oscillator modules
2) add a ton of modules enough so it is a scrolling patch
3) add a diva high pass filter
4) ????
5) Profit!

[plugmon]

Found this.

When "selected on top" is enabled and the patch has enough modules where it needs to pull it from the bottom, adding a diva high pass filter (zebrahz obviously) will brick the vst and daw? Tested only in FL Studio 20, nowhere else yet but the behavior is consistent on my machine and does NOT occur in the included default zebrahz skin.

Steps to repeat
0) load zebraHZ w/ neumann pro
1) enable selected on top for the oscillator modules
2) add a ton of modules enough so it is a scrolling patch
3) add a diva high pass filter
4) ????
5) Profit!

Thanks for the report, I confirm that this happens in my environment too.
I vaguely remember that in the past similar issue related to "selected on top" option occurred in Massive Modular skin.
gonna look into the matter and (hopefully) fix it!!

[Yahnee]

Hi!

Is there somebody who could help me!

I have installed Neumann Pro skin to My Documents:u-he:ZebraHZ:Support:Themes folder and installed the fonts to Data:Fonts folder. But my HZ doesn't see the skin, and i can't change it under the preferences or with right click.

It only shows the options for different GUI sizes. I have used it before but had to reinstall HZ because presets didn't show up. Presets are now showing fine but im unable to change the skin.

Thanks!

Edit:

Just found solution to my problem. Found the right folder by going to C:Program Files/Common Files/VST3 and clicking the shortcut to Zebra HZ.data and it pointed me to the right place.

[aMUSEd]

Bought it - is a skin for Zebrify planned?

[plugmon]

Bought it - is a skin for Zebrify planned?

Not planning of Zebrify...

[sekka]

SOS!! needed!

Just bought a Pro skin. Really disappointed by the purchase. Could not test these features just by looking at the screenshots!

1. Why there is no highlighting/autoselecting of the clicked osc/modulation/fx module??? This works on every skin I've tried (except for fxs). I could probably live with that if Zebra's "Selected on top" option would work as expected! But this just gets reset any time I reopen Zebra. I understand that this is not the skins fault. But the combination of these *** things just makes everything stupid slow squared instead of speeding up the existing process... Also when in regular Neumann, selecting a modulation knob and not being able to see the modulator itself because fx tab is opened is such a disadvantage compared to all regular skins.

2. Why moving SB and Mixer and Shaper to a separate tab instead of keeping them in one common "grid" tab? If that were to speed up the process by separating the types, why then filters doesn't have their own section? Why are Dist and Fold separated from the Shaper??? In the end I consider this to be an unlogical decission which on top just added one unnessary click (multiplied by many times) for the selection of synthesis modules.. the process that itself has the issue discribed in point 1.

3. It just doesn't fit well on my screen (1920 x 1080). Neumann doesn't fit vertically on 120% and 110% is smaller than I would like to. Neuman pro doesn't fit even on 110%. Neither vertically nor horizontally. Doesn't have my other wide screen near right now, for which I bought the pro skin, but suspect it won't fit vertically.

4. Disregardable point (my fault for not paying attention to the screenshot), but I hope my logic makes sense. Is it possible to move back synthesis lane back to the center? It's just the most "look at" point and to me it's just physically inconvenient to turn my head each time.

Can something be done/adviced? I am a user of other Plugmon's skins, so was really hoping to be satisfied with the purchase

[sekka]

please

[plugmon]

Just bought a Pro skin. Really disappointed by the purchase. Could not test these features just by looking at the screenshots!

1. Why there is no highlighting/autoselecting of the clicked osc/modulation/fx module??? This works on every skin I've tried (except for fxs). I could probably live with that if Zebra's "Selected on top" option would work as expected! But this just gets reset any time I reopen Zebra. I understand that this is not the skins fault. But the combination of these *** things just makes everything stupid slow squared instead of speeding up the existing process... Also when in regular Neumann, selecting a modulation knob and not being able to see the modulator itself because fx tab is opened is such a disadvantage compared to all regular skins.

2. Why moving SB and Mixer and Shaper to a separate tab instead of keeping them in one common "grid" tab? If that were to speed up the process by separating the types, why then filters doesn't have their own section? Why are Dist and Fold separated from the Shaper??? In the end I consider this to be an unlogical decission which on top just added one unnessary click (multiplied by many times) for the selection of synthesis modules.. the process that itself has the issue discribed in point 1.
......

"Selected on top" issue was reported by another and I fixed that in v1.6.5 update (April.5.2023), so now it should work as expected
Rack highlight does not work in Neumann for unknown reasons. It is probably due to the complex layout like mini icons appearing in the bar. The interaction between the module grid and rack is quite "blackbox" and I couldn't make it work

The necessity for SB/Mixer/Shaper moved to 2nd rack is written in the page 17 of the userguide---In short, they're sacrificed for D-VCFs and D-HPFs to be put in the 1st rack. (32 modules are the current limit for 1 rack.)
It was really hard to decide which modules to be sacrificed since the usage of modules is very much dependent on people. Anyway I put priority on having Dive filters in the main rack . And I vaguely hear that this limitation will be expanded on Zebra3.

Basically I cannot satisfy everyone with different environments, different workflows and different tastes.. I know I can please more people if I serve more options and variations, but it's endless and the burden for keep them all up-to-date is very heavy.
And that's why I offer demo skins, for customers to see if a skin fit to their environment. I'll accept refunding if you want to.

[srcodling]

Sorry if I'm missing something, but how do you assign midi learn for the XY pads with the Neumann Pro skin? I can't figure it out...

[plugmon]

Sorry if I'm missing something, but how do you assign midi learn for the XY pads with the Neumann Pro skin? I can't figure it out...

Wow, I thought the sliders (dashed borders and triagnles) in Perform tab were assignable, but actually they're not....
Sorry, I have to fix that or add extra knobs somewhere. Thanks.

For now, please assign using the default skin. The assignment data should carry over even if you change the skin.

[srcodling]

Thanks!