zebra2

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

Post

paradiddle wrote:I tried it a few times using just a bit of random and I didn't get any crash and got interesting results. I always turn the volume down just in case.
thanks for the warning though!
Well, you won't get crashes I hope ;)

But wonshu has managed to come up with patches where the LFOs do not work at all, without any traceable reason...

Cheers,

;) Urs

Post

Urs wrote:
CinningBao wrote:This is one beautiful machine.
any chance of Z2 having audio inserts? I'd love to use the reverb on 'live' sounds!
Yes, there's a good chance for that.

Cheers,

;) Urs
sweet. perhaps I'm asking too much, but is there the chance that these inserts could be used in the main modular area - then we could frequency modulate all kinds of acoustic nastiness! (my suspicion is that this was your originially intended implementation)

This is soooo good! :D

Post

CinningBao wrote:sweet. perhaps I'm asking too much, but is there the chance that these inserts could be used in the main modular area - then we could frequency modulate all kinds of acoustic nastiness! (my suspicion is that this was your originially intended implementation)

This is soooo good! :D
Yep! An "Input" module is intended to show up in the voice Grid as well as in the effects Grid.

But I'm afraid that it means that there'll be kinda "ZebraFX.dll" which will basically be the identical with Zebra but can be put in the insert/send effects rather than instrument slots.

Cheers,

;) Urs

Post

Urs wrote: But I'm afraid that it means that there'll be kinda "ZebraFX.dll" which will basically be the identical with Zebra but can be put in the insert/send effects rather than instrument slots.
That would be a great idea to have such a modular effect-only plug-in. Just to use it on anything. All Cubasers will love the idea to change the order of effects on the fly ... ;-)


Greetings,
Michael
Someday I'll look back on all this and laugh... until they sedate me.

Post

Urs wrote:But I'm afraid that it means that there'll be kinda "ZebraFX.dll" which will basically be the identical with Zebra but can be put in the insert/send effects rather than instrument slots.
Would it be possible to support Logic's sidechain? That way you can use the normal AU audio instrument, and use the sidechain feature to route in external audio to the input object (I do this with the ES1 for instance).

Post

beej wrote:
Urs wrote:But I'm afraid that it means that there'll be kinda "ZebraFX.dll" which will basically be the identical with Zebra but can be put in the insert/send effects rather than instrument slots.
Would it be possible to support Logic's sidechain? That way you can use the normal AU audio instrument, and use the sidechain feature to route in external audio to the input object (I do this with the ES1 for instance).
Yes, the AU will come as one single plugin, just like Z1.5. The hosts that don't allow for side chains don't allow for Midi->effects anyway.

Cheers,

;) Urs

Post

I just have to say \........

Damn!

Well worth the wait!

Congrats so far Urs...this thing sounds like a million.

Post

I know I keep asking for stuff, but that's the point of feedback :)

More envelope generators would be cool - there's four main EG's, and when you could maybe have the amplitude, filter and pitch of an oscillator requiring three, and you could have 4 oscillators, 4 FM oscillators and a couple of combs in there, the EG count starts looking small - and that's before you using EG's to control other parameters as well.

Same is true for the multis, especially when doing evolving stuff - I keep having to fall back to LFO's and save the multis for other things. Speaking of LFO's, custom waveforms/arpeggios would be cool too, although in some respects that's exactly what a multistage is. I found working with the multistages to be a little hit and miss at the moment, and I'm looking forward to some of the improvements already mentioned - probably wouldn't need custom LFO waveforms then.

A question about the popup to select a new module for the grid - I'm wondering why all objects are listed initially (ie FM1, FM2, FM3, FM4 etc)

Would it be simpler to list the objects by type, something like:
Osc
FM Osc
Comb
Shaper

For instance, if I want to add an FM oscillator to the grid I don't really care whether it's 1, 2, 3 or 4, I just want a new FM oscillator. Shouldn't Zebra just add an FM Oscillator and it becomes the correctly numbered one on insertion? And if I've used up all FM oscillators, then remove the "FM Osc" from the popup showing I can't add any more to the current grid. This would simplfy the grid selection popup and help sped up the workflow a snadge.

Hmm, does it sound like I'm ungrateful? I hope not! This week is adopt a Zebra week... :)

Post

Valid point, beej!

Will see what I can do about them. There's always been the plan to add 4 more envelopes and maybe custom LFO shapes...

The add-modules menu will be tidied up to look less cluttered, but I think having the distinct modules isn't such a bad idea, especially for the normal oscillators. It's hard to explain now, but there's some stuff on its way that will make things easier when it's done the way it is...

;) Urs

Post

Thanks Urs - I know that much of what people suggest you will already be on top of, but it doesn't hurt to mention it ;)

I have total confidence in the end result! Great stuff!

Post

WTF!!

Naaaa, your taking the piss! :o

just downloaded Zebra2 demo & all i can say is

f**k,,,, hang on let me pick another random preset,.........................................................................................................

SHIT!

H H H How? i dont get it?

My sound card never made a noise like this before? (well except maby the 2 minit Virus demo on my POCO

Bravo!!!!!!

Post

I've just been adding the X-Y stuff to my patches, and another thought occurs:

I usually program my patches so the intended patch plays when all the X/Y controls are centered. However, as we all know there can be useful patches at other positions, as well as just using the X/Y controls for motion, so, it would be cool if there were snapshot memories of the X/Y positions, a bit like how the waveform selectors work.

By clicking on the various snapshots, you could instantly audition some patch variations of the X/Y controls setup by the patch designer. And if there was a morph time slider, then the transitions could be instant or could morph over time, in a similar way to the GRM Tools plugins, without the problems a generic patch morphing feature would cause.

It would probably be good UI practice to only show patch variations if there actually were any, as even now not everyone sets up the X/Y controls with meaningful parameters, let alone enough to do patch variations.

Ooh, and there's an idea - recordable motion paths of the X/Y's in a patch might be useful, although that implementation clashes a little with the idea that the X/Y's are more intended as real time controls. I suppose LFO's are the way to go on that for now...

Post

I'm floored by Zebra. Congratulations on such a major accomplishment. Do you plan on implementing some sort of microtuning capacity. There are a number of sounds that I've been playing with that would work well with such a feature...I know you are barraged with requests for features and hope that you don't mind one more being thrown on the pile. Anyhow...wonderful...friggin' wonderful!!

Post

beej wrote:I've just been adding the X-Y stuff to my patches, and another thought occurs:

I usually program my patches so the intended patch plays when all the X/Y controls are centered. However, as we all know there can be useful patches at other positions, as well as just using the X/Y controls for motion, so, it would be cool if there were snapshot memories of the X/Y positions, a bit like how the waveform selectors work.

By clicking on the various snapshots, you could instantly audition some patch variations of the X/Y controls setup by the patch designer. And if there was a morph time slider, then the transitions could be instant or could morph over time, in a similar way to the GRM Tools plugins, without the problems a generic patch morphing feature would cause.

It would probably be good UI practice to only show patch variations if there actually were any, as even now not everyone sets up the X/Y controls with meaningful parameters, let alone enough to do patch variations.
This is indeed planned, maybe for version 2.5 or something... 8)
beej wrote:Ooh, and there's an idea - recordable motion paths of the X/Y's in a patch might be useful, although that implementation clashes a little with the idea that the X/Y's are more intended as real time controls. I suppose LFO's are the way to go on that for now...
Modulation is not planned for several reasons... :cry:

Cheers,

;) Urs

Post

mayan wrote:I'm floored by Zebra. Congratulations on such a major accomplishment. Do you plan on implementing some sort of microtuning capacity. There are a number of sounds that I've been playing with that would work well with such a feature...I know you are barraged with requests for features and hope that you don't mind one more being thrown on the pile. Anyhow...wonderful...friggin' wonderful!!
Heh, thanks! :oops:

Microtuning is one of the next things on the todo list.

But it's indeed a lot of stuff left to do. I'll publish another preview version shortly that will be quite identical to the current stuff and expires end of January... damn...

Cheers,

;) Urs

Post Reply

Return to “u-he”