Zebra 3 Public Beta Revision 20399

[exmatproton]

However, as far as visual feedback, what I would like is this: parameter controllers moving (eg knobs turning, faders shifting) as they are being modulated.

No. That would not work. Since a knob should still be usable after 1 (or more) modulator(s) is 'linked' to the knob.

I'm also noticing that unipolar controls aren't working as they did in Z2 - and can't for the life of me work out how to get it right. For instance, I just want to assign a CC knob to pan something L-R and it's absolutely flooring me. The "unipolarize" option doesn't help. User error? Glitch?

unipolarize is working as expected here. However, if you want, let's say, CTRL-A to do a full pan (-100 to 100), you cannot do that with one 'link'. You can make 2 links though (so CTRL-A is modulating panning twice). Then turn the panning to one side completely and now CTRL-A is doing a full -100 to 100 sweep if you turn the knob

[WalterH]

Can I reset only one module ? for example I experimented with COMB but I didn't like results and I want to reset only COMB, how ?
now I have to either double click on all parameters to reset them one by one, or add new another COMB (as previous COMB stores previous values) or reset with preset which is even more bad.

[tasmaniandevil]

Can I reset only one module ?

That's where module presets come in handy. Just set the comb module up the way you want it, then click the triangle in the upper left corner to save it as a module preset.
We want to include init presets for all modules, but so far didn't have time to create those.

[WalterH]

Oh great, I can create init, didn't know that, thanks!
yes that would be good devs to include inits for modules by default.

P.S.
COMB module's "tone" knob by default isn't in its default state by the way, it stays middle, double clicking on it resets it to left.
but middle is default if you ask me, in other words it stays correctly but that correct state for some reason isn't default.

[MeanGreen7]

What a time to be alive indeed! I'm seriously impressed by just how good everything sounds, especially the exciter/modal/comb modules. They are on par or better than any physical modeling specific plugin I own. Are you planning on keeping the "Arp Mode" label for the partials, or switching it to "Flux - Sweep/Random" like it is in the manual? I think the latter makes more sense in context.

[WalterH]

As a sidenote, why not have excitr module to infinitely beep, it's limited to 100.. I tried many ways and it stops anyway.

[MeanGreen7]

As a sidenote, why not have excitr module to infinitely beep, it's limited to 100.. I tried many ways and it stops anyway.

I would imagine that would cause runaway feedback/overload problems with how the other modules process the impulses. You can use the noise module for constant impulses.

[beely]

What a time to be alive indeed! I'm seriously impressed by just how good everything sounds...

Zebra's never sounded so good indeed!

[whassup]

What a time to be alive indeed! I'm seriously impressed by just how good everything sounds...

Zebra's never sounded so good indeed!

This!

[Matty686]

OK, so I really like to make wind instruments.
Wind instruments often need to start detuned and come into tune as pressure is applied.
That’s why you can't just preview them on their default pressure instead of max pressure.

Aha! I misunderstood then, I thought you were referring to factory library presets (i.e. non-MPE presets), where "pressure to pitch" can be irritating in many cases.
What do you mean by "preview" though? This line in particular I can't grasp: "some way to preview pressure in preform view is necessary". Can you spell it out for me, please? It's been a demanding week, brain slightly tired.

Viktor
u-he team

By “preview,” I mean having a way to send a pressure signal along with the note, other than relying on an MPE keyboard or in my case looping a note with a pressure envelope in Bitwig (which is currently how I audition my custom instruments that use pressure). Having a way to simulate pressure on the included keyboard during the performance section would significantly save me time when selecting an instrument for a song. If pressure were integrated into the performance window as an adjustable parameter or even better directly on the performance window keyboard keys, I could Audition my own instruments much faster, as many of them use pressure and remain silent without a pressure signal. This could actually be a huge selling point as no other synth has this

[Matty686]

OK, so I really like to make wind instruments.
Wind instruments often need to start detuned and come into tune as pressure is applied.
That’s why you can't just preview them on their default pressure instead of max pressure.

Aha! I misunderstood then, I thought you were referring to factory library presets (i.e. non-MPE presets), where "pressure to pitch" can be irritating in many cases.
What do you mean by "preview" though? This line in particular I can't grasp: "some way to preview pressure in preform view is necessary". Can you spell it out for me, please? It's been a demanding week, brain slightly tired.

Viktor
u-he team

By “preview,” I mean having a way to send a pressure signal along with the note, other than relying on an MPE keyboard or in my case looping a note with a pressure envelope in Bitwig (which is currently how I audition my custom instruments that use pressure). Having a way to simulate pressure on the included keyboard during the performance section would significantly save me time when selecting an instrument for a song. If pressure were integrated into the performance window as an adjustable parameter or even better directly on the performance window keyboard keys, I could Audition my own instruments much faster, as many of them use pressure and remain silent without a pressure signal. This could actually be a huge selling point as no other synth has this it is nice to be able to hear all your instruments the way they are ment to sound with just the mouse it in some ways I feel the MPE protocol can be a bit of a broken or at least missapplied idea because using it in songs the way you wish you could often involves destroying the ability to audition your own patches. I actually think making The performance window keyboard have MPE features is something that will eventually become normal once one person in the industry actually tries it you guys could be the first ones honestly it could be revolutionary. at the very lest you could give a switch to change the velocity property of the virtual keyboard (witch already exists in the form of were you click on the key) to pressure so I can hear my patches.

[exmatproton]

As a sidenote, why not have excitr module to infinitely beep, it's limited to 100.. I tried many ways and it stops anyway.

You can use the noise generator. Set it to 'single hit' and set the trigger source to whatever (lfo, saw down works pretty good). The lfo rate can be modulated to mimic the bounce effect.

[don_sook]

I've been having so much fun using Zebra 3 since it was released. The oscillators and filters sounds very, very nice. The yellow filter with the resonance cranked up with some subtle frequency modulation sounds incredible.

My only gripe so far is how Zebra 3 doesn't meld well with the aspect ratio of 16:9. I have a feeling like 4:3 would help Zebra 3 fill the screen more than 16:9. Hopefully there will be future skins available that would make Zebra 3's GUI more wider.

[jtsterays]

There's definitely should be a way to save curve shapes in a built in library or something.

[exmatproton]

There's definitely should be a way to save curve shapes in a built in library or something.

you can (edit; sort of)

youcan.jpg