Zebra + Distortion (new rev 2079)

[Breeze]

We have to rewrite the VST3 layer because all work arounds to make VST3 work for us have failed. We need to revert to "simple VST3". I'll write a blurp about that.

In the meantime we recommend using VST2 instead.

I've kept the betas from my main computer because they are works in progress, but I have used VST3 versions in projects over the last year. Will the builds using a new VST3 framework be able to load and work as before in older projects using VST3s created with the older framework?

[Urs]

This is a fantastic update to Zebra. Thank you!
Unfortunately it's crashing Live 9.1 (32bit) every time on exit.
I'm on OSX 10.8.5.

please send crash.log to support at u-he dot com

[Urs]

Will the builds using a new VST3 framework be able to load and work as before in older projects using VST3s created with the older framework?

We sure hope so. I can't see why they wouldn't (but then, I haven't seen the underlying problems coming in the first place)

[Gyu]

This is a fantastic update to Zebra. Thank you!
Unfortunately it's crashing Live 9.1 (32bit) every time on exit.
I'm on OSX 10.8.5.

please send crash.log to support at u-he dot com

Done. (I hope I sent the right thing)

[Urs]

This is a fantastic update to Zebra. Thank you!
Unfortunately it's crashing Live 9.1 (32bit) every time on exit.
I'm on OSX 10.8.5.

please send crash.log to support at u-he dot com

Done. (I hope I sent the right thing)

Eeek. It's the right thing, but I can't see anything in it - no reference to Zebra.

Did you use the AU or the VST?

Also, could you create an empty text file called "Zebra2.log" on your desktop? It would help a lot ot get this as well after such a crash.

[Gyu]

Ok, I've sent another one. I hope it helps.
As I said in my last mail, this only happens when Zebra is racked.

[3ee]

Would it be a good idea to place a feedback knob (similar to Diva) into the new Zebra dist module or maybe make it as a new dist type instead?

[Urs]

Would it be a good idea to place a feedback knob (similar to Diva) into the new Zebra dist module or maybe make it as a new dist type instead?

We actually had a feedback knob there. The system became so immensely hard to control that we decided against it for sake of usability, until Sascha can spend more time to fine tune it and maybe until we can come up with some sort of preset-scheme.

[EvilDragon]

Urs, I've just noticed that:

* Zebrify doesn't show revision number like Zebra 2 does
* Zebrify didn't get two additional modmappers
* Zebrify doesn't have 4 FMOs (intentionally?)
* Zebrify is totally missing my orange skin (not your fault though! )

[#rob]

EvilDragon: what revision number is that?
"This one" or an older build?

[EvilDragon]

Lemme try installing the beta... I have rev 1559, so that's before this beta.


EDIT: And I was just halfways through making Orange Zebrify. ;_;

[EvilDragon]

Hm, installed the beta and now custom skins don't seem to be using their images... instead they're pulling from the main images folder :/

[iamyourfather]

tried this version in reaper and the timing is crazyily bad lol, like swing on full bad. Distortion sounds amazing tho but thought I best let you know before you release it or anything. Gone back to std zebra now

[Urs]

tried this version in reaper and the timing is crazyily bad lol, like swing on full bad. Distortion sounds amazing tho but thought I best let you know before you release it or anything. Gone back to std zebra now

Fixed here, will post update shortly.

[Urs]

Hm, installed the beta and now custom skins don't seem to be using their images... instead they're pulling from the main images folder :/

I'll work on Dark Horse in a few days. Then I'll check out what's happening. It's entirely possible that the fast GUI open code has corrupted Themes loading.