Latest Builds: Zebra 2.8 *beta*

[manuriga1]

First of all congrats to make the best synth even beter!
i wonder one thing , would it ever be possible to add the record function of hive in Zebra sequencer. it would make using the sequencer far better

That's something we'll hopefully achieve for Zebra 3. But we can't invest double time to rework Zebra2 into the same thing as Zebra3 - where we could as well merge the two. It would take a lot longer and I don't think it would in the end make for a better synth.

the synthesizer on its own doesn't get better this way , but a recordable step sequencer makes you come up with nice surprises . anyway its just a suggestion. Top work from you and your team. you are all responsible for many hits out there

[Theturbinman]

Like how you guys left the old unempty dark horse skin!! Like the old light background on it tho instead of the BLACK background . I also like the Dark Skin better then the New dot one In my opinion. I am also not getting CPU spikes anymore on (mostly pad patches) !! So far great update the only thing i dont like is that once u select from the preset browser a category i dont like how the presets are showing sideways like HIVE (see image below). Is there a way to set that back to default? Thanks Much!!!!!!

[Russell Grand]

Wow wow wow! That DarkEight skin is sexy! This is awesome!

[Elektronisch]

I also noticed that Zebra 2 needs some time to update its preset database and i am using SSD.

Might be anti-virus stuff, like the problems people experienced with Repro?

The database update is normally really kinda instant...

Also just a small tip wich i think can help visualy: in Dark8 skin use same color scheme for Preset browser as you have in OSC browswer. It feels so much more cohesive with the Synthesis and Performance section.

Good point!

Nice we agree on same thing

No i dont think its antivirus issue since i use the default Windows security. It just slow and it updates it every time i open zebra 2.

[zvenx]

I also noticed that Zebra 2 needs some time to update its preset database and i am using SSD.

Might be anti-virus stuff, like the problems people experienced with Repro?

The database update is normally really kinda instant...

Also just a small tip wich i think can help visualy: in Dark8 skin use same color scheme for Preset browser as you have in OSC browswer. It feels so much more cohesive with the Synthesis and Performance section.

Good point!

Nice we agree on same thing

No i dont think its antivirus issue since i use the default Windows security. It just slow and it updates it every time i open zebra 2.

I do believe the Windows security default (in windows 10 anyway) includes windows defender running real time.
rsp

[PietW.]

Hi Urs,
Many thanks for Zebra.
Merry Christmas and health for you, your family and of course the entire U-He team.

[tasmaniandevil]

Tried the AU version and it works great! The VST is what's crashing. I replied to my email to support with the updated info. Thanks again! Now back to the Zebra2.8 AU!!

Thanks for reporting. I have seen your support ticket. Very curious to find out what's going on there, sounds very unusual.
But good to know that at least one plugin format works for you.
I might get back to you about this after the holidays.

[tasmaniandevil]

are unwanted noise bursts a possibility with the beta?

Certainly not expected. If this continues to happen, please send us a mail to support @ u-he .com, so we can investigate this after the holidays.

[tasmaniandevil]

Reopen of GUI resets scroll position in preset browser. IE if preset is on second page it's not visible.

Good catch. I will add a ticket in our system, maybe we can improve/fix this.

[tasmaniandevil]

The first instance of zebra 2.8 with defender running takes about 38 seconds, without defender its about 28 seconds.. So yeah better.. But...
Every other run even if I close my daw and reopen it is more in the 2 second time period..
Rsp

Oy vey, sorry to hear that, Richard. Seems like your computer really doesn't like our new preset database system. Sounds like this is the same issue you had with Repro. Which is really strange, since the applied fix was a framework fix, so theoretically this should not happen in Zebra.
I might contact you after the holidays, so we can figure this out (really need a few days off now, this was an exciting but also very straining year).
Very interesting detail that Defender still has an effect, although you already excluded the u-he folders from scanning.

Note to everyone:
Since Zebra now uses the same new browser as Repro, the same notice about malware scanners applies:
Please make sure that antivirus/malware realtime scanners (such as Defender on Windows) do exclude the u-he folders from scanning, since this can drastically slow down the initial building of the preset database when you load the first instance of Zebra in a host project.

About the reopening of the GUI taking a few seconds for some people:
If you have tons and tons of presets installed (like 15000 or 26000 as already reported by a few users), this might slow down the opening of the GUI a bit.
This is one of the bigger issues on our list, and will certainly be improved next year in subsequent updates.

[experimental.crow]

win10 -
cannot seem to open w/ :
tobybear / minihost
xlutop / chainer

previous build did open in minihost

[Jax Pok]

I really like that colour scheme.

Have a good one

[zvenx]

Viktor no rush whatsoever...
maybe the gui speed up will help too..
Thanks.. Enjoy your time off .
Rsp

The first instance of zebra 2.8 with defender running takes about 38 seconds, without defender its about 28 seconds.. So yeah better.. But...
Every other run even if I close my daw and reopen it is more in the 2 second time period..
Rsp

Oy vey, sorry to hear that, Richard. Seems like your computer really doesn't like our new preset database system. Sounds like this is the same issue you had with Repro. Which is really strange, since the applied fix was a framework fix, so theoretically this should not happen in Zebra.
I might contact you after the holidays, so we can figure this out (really need a few days off now, this was an exciting but also very straining year).
Very interesting detail that Defender still has an effect, although you already excluded the u-he folders from scanning.

Note to everyone:
Since Zebra now uses the same new browser as Repro, the same notice about malware scanners applies:
Please make sure that antivirus/malware realtime scanners (such as Defender on Windows) do exclude the u-he folders from scanning, since this can drastically slow down the initial building of the preset database when you load the first instance of Zebra in a host project.

About the reopening of the GUI taking a few seconds for some people:
If you have tons and tons of presets installed (like 15000 or 26000 as already reported by a few users), this might slow down the opening of the GUI a bit.
This is one of the bigger issues on our list, and will certainly be improved next year in subsequent updates.

[Penelope]

are unwanted noise bursts a possibility with the beta?

Certainly not expected. If this continues to happen, please send us a mail to support @ u-he .com, so we can investigate this after the holidays.

FYI, this did NOT happen to me. Just curious if it might. Beta tested a plug recently where that was an issue.

[Urs]

are unwanted noise bursts a possibility with the beta?

Certainly not expected. If this continues to happen, please send us a mail to support @ u-he .com, so we can investigate this after the holidays.

FYI, this did NOT happen to me. Just curious if it might. Beta tested a plug recently where that was an issue.

Yeah, I read your question that way. If anything, we fixed a possible glitch or two, but it wasn't any of those burst type of things. I don't recall Zebra ever having any of these.

Back in the days, when one bought a synthesizer, it commonly came with a note of caution that synthesizers can create tones and frequencies which can damage hifi gear and/or ears. I guess that still applies, which is why I'd suggest to avoid overly much headroom on the digital side (turn volume up in the DAW, with as little headroom as possible before clipping). Instead, keep volume as low as possible on the analogue side (knob on power amp or external mixer). This way common glitches are limited by clipping.

I guess ^^ is the opposite advice of what mixing engineers will say, but I'd still go there while testing new stuff.