Zebra 2.3 Released!

[mcnoone]

is there a way to change the default sound? I prefer a basic saw or sine to start from usually..

I'm pretty sure it was dropping some notes at the start of loops, and half way through strangely, on my 10.5 OSX Live 7.0.10 setup.

Yes, you can just create the starting preset, then save it as "init" It will overwrite the original one though.

[aMUSEd]

OK installed the new version. So far the KORE 2 template seems to be matching. Tomorrow I will test further and make pages for the new sideband modules. Anything else I should add pages for while I'm at it?

[mcnoone]

I'm pretty sure it was dropping some notes at the start of loops, and half way through strangely, on my 10.5 OSX Live 7.0.10 setup.

First quit out of Live, then you can try throwing out the Ableton Live preference file, under:
user(name)/library/preferences/com.Ableton.live.plist
After throwing out those, you might have to change some preferences back to as you had them before in Live.
Then repair permissions.
Sometimes those type of problems happen because of the midi cintroller your using too. I have a cheap midi keyboard controller that hangs notes alot. Buy a better one, and it would not have that problem.

[CinningBao]

I'm pretty sure it was dropping some notes at the start of loops, and half way through strangely, on my 10.5 OSX Live 7.0.10 setup.

Sometimes those type of problems happen because of the midi cintroller your using too. I have a cheap midi keyboard controller that hangs notes alot. Buy a better one, and it would not have that problem.

I'm using the squeltchy micron keyboard at the moment, but despite it's foibles that isn't the problem - the notes are being triggered from a quantized clip in the arrange window.

and thanks for the init preset tip

[Urs]

Hmmm. This version shouldn't drop first notes in Live. It was a bug in Live (also affected some other complex synths), I worked around it.

[rbet]

Thanks. Another question: why do some OSCFX (Turbulence, Ripples, Formanzilla, etc.) affect the sound even when the 'Value' knob is dead center? How do I control the wet-dry mix of those effects?

I'm pretty sure the dry mix is to have them turned off. Just turning any OSCfx on has an effect. By turned off, I mean no OSCfx selected, is the dry mix.

Thank you for the answer. Hey Urs, until now I thought the Value knob was a kind of dry-wet mix knob. Is there no way of controlling the OSCFX in the traditional sense?

[ZenPunkHippy]

I'm pretty sure the dry mix is to have them turned off. Just turning any OSCfx on has an effect. By turned off, I mean no OSCfx selected, is the dry mix.

<...> until now I thought the Value knob was a kind of dry-wet mix knob. Is there no way of controlling the OSCFX in the traditional sense?

Heh heh, I guess because they aren't traditional effects, they don't have traditional controls

For example the "Odd for Even" OSC FX controls the ratio of even / odd harmonics in the overall waveform. Increase the value and you get more odd harmonics, decrease for more even harmonics. In the middle there is an even split between the number of odd and even harmonics, which is why it starts modifying the waveform as soon as you turn the effect on, but that depends on the harmonic content of the basic waveform being modified of course.

It would not make sense to have a wet / dry to control the amount of the amount of this effect if you see what I mean?

With OSC FX you are controlling the harmonic content and / or the amplitude of the harmonic content of the fundamental wave form i.e. it's overall "shape". For example you might create a sine wave and use OSC FX to add second peak at double the fundamental frequency, controllable via the "Value" parameter.

This does affect the sound of course - leading us to think of a wet and dry component - but wet / dry controls the ratio of FX'd signal to dry signal, and if I've explained this well enough you will understand that with OSC FX it makes no sense to think of an FX'd signal, as there is only one signal and it's always dry, that being the generated waveform.

Two simple reasons for using OSC FX would be

a) to tame a troublesome peak in a particular patch

b) for interesting and unique control over FM or additive synthesis.

There are probably more that I cannot think of right now. It's a pretty unique feature BTW.

Phew! I'm glad to get that out, it helps me understand it better. Does that help?

Peace,
Andy.

[rbet]

...Does that help?

Peace,
Andy.

Absolutely. Thanks for the reply! :tu:

[mcnoone]

...Does that help?

Peace,
Andy.

Absolutely. Thanks for the reply! :tu:

I think if you use the "filter" and, or, "symmetry". Those two on default settings, do not produce any noticable change (on middle setting). Those are the only OSC fx used in ZebraCM. They were always on...so I think they don't alter the wave until moved. Could be wrong though.
later,
Mike

[aMUSEd]

Found a problem while trying to set up new pages in the KORE 2 template for the new SB modules. In the past selecting a mod knob in "learn" mode assigned a Kore knob to amount (as it should). Now it's assigning Mod source instead so when I turn the KORE knob it's just cycling through sources rather than changing the amount for the selected source.

Just tried with knobs I'd already assigned - they play right but if I try and re-assign then I get the same problem - looks like no new mods can be assigned properly.

[Urs]

Found a problem while trying to set up new pages in the KORE 2 template for the new SB modules. In the past selecting a mod knob in "learn" mode assigned a Kore knob to amount (as it should). Now it's assigning Mod source instead so when I turn the KORE knob it's just cycling through sources rather than changing the amount for the selected source.

Just tried with knobs I'd already assigned - they play right but if I try and re-assign then I get the same problem - looks like no new mods can be assigned properly.

Very interesting. This might be a new issue that I'll quickly fix then...

(I have a hang over today, so it's a rather typical Sunday. No work, just rest...)

[aMUSEd]

I think I can see what's happening when I try and automate this sort of param in Reaper. Just moving the lfo mod creates envelopes for the source as well as the amount even though I did not change the source or touch it until briefly towards the end of this clip - clearly KORE is just learning the first one.

That suggests a possible workaround - will try and report back.

[aMUSEd]

OK - the workaround works In KORE learn mode I can set it to multi learn params and assign them all to the one knob (you can do this for dozens of params if you want to create really big effects). Selecting the mod knob in multi learn selects the mod source and amount - I can then edit the assignments to delete the source param and voila it's just assigned to amount.

This wasn't happening before though so still probably needs fixing.

[kuniklo]

Hmmm. This version shouldn't drop first notes in Live. It was a bug in Live (also affected some other complex synths), I worked around it.

It seems to be happening here still with live 7.0.12 and the Mac vst.

[phazed]

Urs, I've done a screen cast for you regarding the long-standing OSC load bug:

http://screencast.com/t/d8azWZlc

It starts from a fresh instance of Zebra with its init patch.

As you can also see, there's still something called "WaveFo" that should have 2 additional letters

Zebra 2.3 AU on OS X PPC 10.5.5