Zebra 2.9 released

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Urs wrote: Fri Nov 22, 2019 11:20 am Hmmm, could you elaborate a bit more? We're pretty sure that drawing on Windows is now almost twice as fast as it was in the previous version. On macOS X (10.12 and up) we brought back hardware acceleration for most of it, and the things that don't have hardware acceleration are not in Zebra.

We also brought back extra smooth knob/fader moves during mouse interaction.

Hence, I'm not sure what's sluggish now - we wouldn't know what to fix... :oops:
Hm, if it was GPU accelerated, it would surely be painted in smooth 60fps, but it is not. I use Bitwig 3.03, 10.13.14 and a decent GPU. Bitwig tends to display VST GUIs with maximum FPS. If I scroll the OSCs and filter modules, for example, I see a lot of lagging, it feels sluggish. Also the knobs itself do not "feel" snappy that's why. Seems to me it is a pretty low FPS, which even is fluctuating, depending on how much is refreshed. Sounds to me like purely CPU drawn then. I don't know how I can explain it better... I think the goal should be a constant 60fps, shouldn't it? Since 60fps seems to be the common standard for computers. Even it was constant 30fps, it would be ok. That said, I can still use Zebra quite nicely, as long as I do not record GUI controls directly or so.

If I compare it with the Falcon GUI (JUCE based), the Falcon gui feels similar sluggish in cpu mode. But if I switch it to "OpenGL"/GPU, it is pretty snappy.

Post

/* whitenoise */
Last edited by noiseresearch on Mon Nov 30, 2020 2:38 pm, edited 1 time in total.
It refuses description, allowing only the vague approach of adjectives: dark, light, raw, angelic. Who or what is making these noises? Where are they coming from and what do they point to? What kind of entity can leave such a troubling sonic remnant?

Post

Just want to say thanks for getting tagging in this release. I wasn't sure if you guys were going to go back and re-tag the Z2 library, or add the tagged browser without any tagged presets, or even just leave out the tagging entirely. Having it in, with at least the factory library tagged, is a godsend. Thanks!

Post

Hanz Meyzer wrote: Fri Nov 22, 2019 10:13 am ZebraHZ has ... per-voice-compressor...
Actually a polyphonic compressor per lane of the main grid.

Post

#rob wrote: Thu Nov 21, 2019 4:16 pm So no fun stuff, you know how we Germans roll.
Yeah, I do. :wink:



Post

resistent wrote: Fri Nov 22, 2019 2:27 pm Damn!
:borg:
Zebra HZ for 70€?
:borg:
The calculation in my head goes like 40€ for ZebraHZ 30€ for Zebra³
:borg:
I'm hard on money and save up for a new laptop but this is very tempting...
:borg:
Zebra² is since years in 85% of my work my main synth and slowly become my only synth this offer is a mean move...
:borg:
I feel helpless!
:borg:
Why Urs? Why!?
Don't be resistent!

Post

Hanz Meyzer wrote: Fri Nov 22, 2019 11:37 am
Urs wrote: Fri Nov 22, 2019 11:20 am Hmmm, could you elaborate a bit more? We're pretty sure that drawing on Windows is now almost twice as fast as it was in the previous version. On macOS X (10.12 and up) we brought back hardware acceleration for most of it, and the things that don't have hardware acceleration are not in Zebra.

We also brought back extra smooth knob/fader moves during mouse interaction.

Hence, I'm not sure what's sluggish now - we wouldn't know what to fix... :oops:
Hm, if it was GPU accelerated, it would surely be painted in smooth 60fps, but it is not. I use Bitwig 3.03, 10.13.14 and a decent GPU. Bitwig tends to display VST GUIs with maximum FPS. If I scroll the OSCs and filter modules, for example, I see a lot of lagging, it feels sluggish. Also the knobs itself do not "feel" snappy that's why. Seems to me it is a pretty low FPS, which even is fluctuating, depending on how much is refreshed. Sounds to me like purely CPU drawn then. I don't know how I can explain it better... I think the goal should be a constant 60fps, shouldn't it? Since 60fps seems to be the common standard for computers. Even it was constant 30fps, it would be ok. That said, I can still use Zebra quite nicely, as long as I do not record GUI controls directly or so.

If I compare it with the Falcon GUI (JUCE based), the Falcon gui feels similar sluggish in cpu mode. But if I switch it to "OpenGL"/GPU, it is pretty snappy.
hmmm...over here it is running at a smooth 60fps all the time now..
FL Studio, windows10, x64

Post

I forgot to mention, that I am on 4K/Retina.
Howard wrote: Fri Nov 22, 2019 4:32 pm Actually a polyphonic compressor per lane of the main grid.
Ah, I think I meant the same :)

Post

Hanz Meyzer wrote: Fri Nov 22, 2019 6:12 pm I forgot to mention, that I am on 4K/Retina.
Howard wrote: Fri Nov 22, 2019 4:32 pm Actually a polyphonic compressor per lane of the main grid.
Ah, I think I meant the same :)
Hm, me too. which computer?
I'm running Mini on ultrafine 4K, 10.14.6.
Can you do a video capture see if its the same here or am i just less sensitive about that?
Image

Post

I've mentioned this once or twice in the past, but now may be a good time to ask again. Would it be possible to reduce the output volume on the factory presets? I'm hoping it would be possible to develop a quick script that goes in, looks at the current output level, and reduces it by a fixed amount. Maybe just subtract a third from the current level so like: New X=(X-(X/3)).

I generally find that some of these factory sounds go well above 0db and most seem to shoot for too close to 0dbfs for comfort. Adjusting the output to a low volume and locking it helps with most patches, but some patches are still very hot even with a low global output so it's not the best solution. Hence why I'm hoping some kind of internal script could be written to add just a bit more headroom.

Post

Funkybot's Evil Twin wrote: Fri Nov 22, 2019 9:23 pm Would it be possible to reduce the output volume on the factory presets?
Hi Evil Twin,
that already happened for this 2.9 release. Off the top of my head I'd estimate that roughly half of the factory library was edited to reduce the output volume so that the sound wouldn't exceed the 0dB line with regular playing. It's still possible that full XY-abuse or triggering 20 notes in your DAW might still do that, of course.
Did you go through the edited factory library yet?

Viktor

Post

Got it. My first commercial aquired U-HE synth. Sounds amazing. Thanks for the sale.

Post

Fantastic update!
Especially the effort to assign the XY parameters.
They work soo beautiful together with the Axyz Gems extension in Bitwig (as does Hive).
It allow you to touch the sound!
For anyone interested: https://github.com/jorisroling/axyz-gems

Post

Ploki wrote: Fri Nov 22, 2019 7:29 pm Hm, me too. which computer?
I'm running Mini on ultrafine 4K, 10.14.6.
Can you do a video capture see if its the same here or am i just less sensitive about that?
Hm, no, can you please prove by screen capture that scrolling is running smoothly with your Mac? Since I have multiple Macs, and it is the same on all, so I do not need a proof that my statement is true. Since you are questioning it, please prove it.

Post

Hanz Meyzer wrote: Sat Nov 23, 2019 12:33 pm Since I have multiple Macs, and it is the same on all, so I do not need a proof that my statement is true. Since you are questioning it, please prove it.
Nobody is questioning that you mean what you say, but since it also always runs the same as ever on our u-he machines, it would indeed be helpful to be able to see what you're seeing.
This might best be directed to the u-he Support though.
You'll find us under support[at]u-he.com

Viktor

Post Reply

Return to “u-he”