A Few More Zebra Questions

[Suntower]

1. Is there a way to change the 'range' of the knobs? For a lot of parameters it seems like the difference between '1' and '2' and '3' is -huge- but it only shows up as a -sliver- visually. Is there a way to make the knobs 'travel' a bit more 'logarithmically'? I dunno if that makes sense, but the visual amount often doesn't map well to the change in -sound-.

2. Is there a way to apply 'Glide' to only certain oscillators in a patch?

3. When I use Midi Learn for the X=Y, it 'learns' for the first control (say X1) just fine, but then when I proceed to the next control (X2) the Learn seems to keep 'learning' and then applies the new parameter to both X1 and X2.

Thanks again,

---JC

[mcnoone]

1.No-
You can hold down shift then move for smaller increments though.
2.Yes. Assign a sloping down (top to bottom)-short amount-mseg to the tune-modulation knob.
That mseg should be non-looping. The end point should only be there.
Not 2 loop points. You can delete as necessary.
3.Don't know about this.
Do you have the same kinds of parameters mapped to both XY 1&2?

[bmrzycki]

For #3, see if you can set up your controller to only transmit one axis at a time:

1. set up controller to only send the CC for the x-axis.
2. Right click on the XY and select "MidiLearn X Axis"
3. Move the controller and verify the X axis is moving in Zebra.

Repeat those steps for Y.

If your controller can't separate out the X and Y signals you can also try to use a controller like a knob or a slider with the same CC value. If this doesn't make sense I can try to explain in a follow-up post.

Good luck!

[Howard]

2. Is there a way to apply 'Glide' to only certain oscillators in a patch?

See "Glide, Glide2" on page 20 of the manual.

BTW: Here's how to apply Glide2 to an ODD-numbered module (e.g. OSC3). Zero its "key scale" and modulate Tune by KeyFol2. Similar will work for filters, of course...

[Suntower]

Thanks for the example. I read about Glide2 and it wasn't clear to me. I'll give it a go.

---JC

2. Is there a way to apply 'Glide' to only certain oscillators in a patch?

See "Glide, Glide2" on page 20 of the manual.

BTW: Here's how to apply Glide2 to an ODD-numbered module (e.g. OSC3). Zero its "key scale" and modulate Tune by KeyFol2. Similar will work for filters, of course...

[Suntower]

I don't get it---how does an MSEG act like glide? If an MSEG is an envelope, how does it 'know' how about the previous note pitch---ie. where to start the portamento -from-?

---JC

2.Yes. Assign a sloping down (top to bottom)-short amount-mseg to the tune-modulation knob.
That mseg should be non-looping. The end point should only be there.
Not 2 loop points. You can delete as necessary.

[pdxindy]

2. Is there a way to apply 'Glide' to only certain oscillators in a patch?

See "Glide, Glide2" on page 20 of the manual.

BTW: Here's how to apply Glide2 to an ODD-numbered module (e.g. OSC3). Zero its "key scale" and modulate Tune by KeyFol2. Similar will work for filters, of course...

oh... nice tip!

[mcnoone]

I don't get it---how does an MSEG act like glide? If an MSEG is an envelope, how does it 'know' how about the previous note pitch---ie. where to start the portamento -from-?

It might be easier to start by just assigning an envelope to the "Tune" modulation knob (next to tune) move it to the left, then adjust the envelope attack-decay, but turn the sustain off=0.
To start attack=0.
Experiment. Move the tune mod to the right for some hard attack tones.

edit:Try to spend some time going through some available presets, and examine what was done within them. It is a faster, better way to learn the synth.