Zebra 3 3.0 RC1 Revision 21793

[Urs]

Is it intended that when I load a saved OSC wavetable into an existing patch all modulations get unassigned and the OSC FX disappear? If so, that's a pity...

We currently only have presets for the whole oscillator.

From the first beta we released in December to now, we have committed 1400 changes, but most of these changes were based on feedback and criticism, not changes that we had originally planned. So we had to adjust the roadmap to come up later with some of these things, such as curve presets. Not sure when we can do it.

[Sampleconstruct]

Is it intended that when I load a saved OSC wavetable into an existing patch all modulations get unassigned and the OSC FX disappear? If so, that's a pity...

We currently only have presets for the whole oscillator.

From the first beta we released in December to now, we have committed 1400 changes, but most of these changes were based on feedback and criticism, not changes that we had originally planned. So we had to adjust the roadmap to come up later with some of these things, such as curve presets. Not sure when we can do it.

Ok, I understand, I thought it might have been a bug. No problem...

[exmatproton]

Since we can use lfo's at audio rate to mod stuff; is there a simple way to let the lfo speed follow keytracking? I mean..the lfo speed can be modulated by kt or a pitch mod, but what is the exact amount it has to be modulated with? I can't seem to get it to follow the tracking neatly..

[Urs]

Since we can use lfo's at audio rate to mod stuff; is there a simple way to let the lfo speed follow keytracking? I mean..the lfo speed can be modulated by kt or a pitch mod, but what is the exact amount it has to be modulated with? I can't seem to get it to follow the tracking neatly..

Good news: This is super easy in Zebra 3.

Drag Pitch or key follow on LFO rate and set the depth to +100, or use the Direct Modualtion at +5. That's it, the LFO tracks key.

If you play C3 (MIDI Note 60), The LFO plays in its original tempo. Play C4 and it plays at double speed, C5 at 4 x and so on.

[exmatproton]

Since we can use lfo's at audio rate to mod stuff; is there a simple way to let the lfo speed follow keytracking? I mean..the lfo speed can be modulated by kt or a pitch mod, but what is the exact amount it has to be modulated with? I can't seem to get it to follow the tracking neatly..

Good news: This is super easy in Zebra 3.

Drag Pitch or key follow on LFO rate and set the depth to +100, or use the Direct Modualtion at +5. That's it, the LFO tracks key.

If you play C3 (MIDI Note 60), The LFO plays in its original tempo. Play C4 and it plays at double speed, C5 at 4 x and so on.

+100? oh man...i tried that and...i dunno..i am not sure. Will try it again thanks!

[Urs]

use two LFOs next to each other in the Scope, set one to follow Pitch +100.00/+5.00 and set both to reset. Should be obvious. (and if not, file bug report)

[Eluwei]

...

[HAJIME KOURIKI]

Would you mind sharing that profile with me?

[exmatproton]

use two LFOs next to each other in the Scope, set one to follow Pitch +100.00/+5.00 and set both to reset. Should be obvious. (and if not, file bug report)

works like a charm...i have no idea what went wrong previously. No report needed

[jtsterays]

Might be a lil late but does Feedback in Env need to be called like that? Why not just Curvature to make it more obvious & intuitive?

[Urs]

Might be a lil late but does Feedback in Env need to be called like that? Why not just Curvature to make it more obvious & intuitive?

It's called that because it refers to a technique that people have used in some of our other synths, and which never worked in Zebra 2. So this is a bit like "look here, it works now".

We want to also add an option called "curvature" or "slope", but this requires us to rewrite large parts of the envelope code. So we postponed it for later.

[jtsterays]

It's called that because it refers to a technique that people have used in some of our other synths, and which never worked in Zebra 2. So this is a bit like "look here, it works now".

Yea, but for people who only know about Zebra, it can look a bit odd.

We want to also add an option called "curvature" or "slope", but this requires us to rewrite large parts of the envelope code. So we postponed it for later.

Wouldnt this make the above redundant?

[Urs]

It's called that because it refers to a technique that people have used in some of our other synths, and which never worked in Zebra 2. So this is a bit like "look here, it works now".

Yea, but for people who only know about Zebra, it can look a bit odd.

You mean, like almost everything in Zebra 3?

(I think if we called it "Slope" people would expect it to work exactly like "v-slope" in Zebra 2)

We want to also add an option called "curvature" or "slope", but this requires us to rewrite large parts of the envelope code. So we postponed it for later.

Wouldnt this make the above redundant?

Not quite. There are many ways to affect the curvature of an envelope. Feedback modulations is easy and popular where anything else is missing, but there are other ways that work more surgical and predictable. Feedback changes the overall timing.

[Charlie Firpo]

Urs, i'm sorry if this has been spoken of before. But in the exciter module (from the init patch), increasing the noise knob to about value 53, makes the left and right levels on the mixer move indepedantly. Eventhough "stereo" is set to off. Is this expected behaviour?

[Urs]

Urs, i'm sorry if this has been spoken of before. But in the exciter module (from the init patch), increasing the noise knob to about value 53, makes the left and right levels on the mixer move indepedantly. Eventhough "stereo" is set to off. Is this expected behaviour?

Yes, that's intended. "Stereo" is just an additional pattern for a series of multiple impulses. By default (Stereo = off) the Exciter creates the same impulse for left and right channel which is then filled with stereo noise when Noise is turned up.