Zebra3 Info

Official support for: u-he.com
Locked New Topic
RELATED
PRODUCTS
Zebra Legacy (Zebra2)

Post

Any chance of an osc free running mode (like hive's flow) in 2.8 or would that be a Zebra3 feature?

Post

SamDN wrote:Any chance of an osc free running mode (like hive's flow) in 2.8 or would that be a Zebra3 feature?
That's a Z3 one...

Post

Quick reply, thanks :) looking forward to Z3...

Post

I would love a button to save the current preset with MIDI learn. Extremely useful if you work with multiple instances and want to automate your workflow.

Post

Urs wrote:What's wrong with current Distortion module in Zebra?
I thought it would be a good time for it to fully succeed the old Shaper modules.
They sound great. But they use a lot more CPU than other modules, could that be?

Post

Please seperate the plugins on zebra 2.8 and up, I dont like waveshell kinda thing like you do in zebra2, I dont use zebrify, zrev and zebralette.

Post

It's not a plugin shell. They are separate plugins completely, you can remove those that you don't use manually.

Post

wackazong wrote:I would love a button to save the current preset with MIDI learn. Extremely useful if you work with multiple instances and want to automate your workflow.
There's the same problem as with MIDI-Learning the prev/next buttons: It's "forbidden" (for lack of a better word) to access the file system upon a MIDI message. Additional infrastructure is required, such as timer based executors, which pose great potential for bugs. It is IMHO a can of worms that should be left untouched.

Post

re23071998 wrote:Please seperate the plugins on zebra 2.8 and up, I dont like waveshell kinda thing like you do in zebra2, I dont use zebrify, zrev and zebralette.
It's not really a "waveshell kinda thing" which has (or had?) a two-step instantiation process. We use plug-in interfaces properly and expose our plug-ins clearly to the host.

It has a lot of advantanges. We might even go there with VST2 in future.
EvilDragon wrote:It's not a plugin shell. They are separate plugins completely, you can remove those that you don't use manually.
Only in VST2. In all other formats (AAX, AU, VST3) we have a combined binary for all plug-ins within a bundle (Uhbik, Filterscape, Zebra, Repro).

The VST2 versions are simply copies of the same .dll. On Windows we query the .dll name to figure out which plug-in is which.

Post

wackazong wrote:
Urs wrote:What's wrong with current Distortion module in Zebra?
I thought it would be a good time for it to fully succeed the old Shaper modules.
They sound great. But they use a lot more CPU than other modules, could that be?
True...

Post

wackazong wrote:
Urs wrote:What's wrong with current Distortion module in Zebra?
I thought it would be a good time for it to fully succeed the old Shaper modules.
They sound great. But they use a lot more CPU than other modules, could that be?
It will be always easier and cheaper for everybody to buy a new CPU, than to reverse back the made compromises of the sound quality for a developer. Especially better for an artist.

Post

Well, there might also be room for improvements. And also, there's the whole thing about setting different qualities for realtime performance and mix down. We might need to define a consistent idea about that *before* we release Zebra 3.

Post

I don´t know if someone has posted something like that before and if its possible.

Would be nice to load single cycle waveforms as wav or aif file on the osc on zebra 3.

Post

Aless909 wrote:I don´t know if someone has posted something like that before and if its possible.

Would be nice to load single cycle waveforms as wav or aif file on the osc on zebra 3.
That's on our own feature wish list. It's quite definitely going to happen!

Post

Urs wrote:
re23071998 wrote:Please seperate the plugins on zebra 2.8 and up, I dont like waveshell kinda thing like you do in zebra2, I dont use zebrify, zrev and zebralette.
It's not really a "waveshell kinda thing" which has (or had?) a two-step instantiation process. We use plug-in interfaces properly and expose our plug-ins clearly to the host.

It has a lot of advantanges. We might even go there with VST2 in future.
EvilDragon wrote:It's not a plugin shell. They are separate plugins completely, you can remove those that you don't use manually.
Only in VST2. In all other formats (AAX, AU, VST3) we have a combined binary for all plug-ins within a bundle (Uhbik, Filterscape, Zebra, Repro).

The VST2 versions are simply copies of the same .dll. On Windows we query the .dll name to figure out which plug-in is which.
Im on linux right now, and theres only Zebra.64.so , no individul plugin
http://i.imgur.com/JKY3JnI.png
but if scanned within host, it has zebra2, zebrify, zebralette, zrev and I cant remove them

Locked

Return to “u-he”