Zebra 3 Public Beta Revision 20399

[midi_transmission]

Small addition for the number of LFO discussion.

Just my personal opinion, but I realized my favorite solution is just more MSEGs. For soundscapes or complex pads it's doable to hit the 4 limit. But yeah, maybe I'm too used to Absynth.

And you can create also LFOs this way. And with MATH modules you can use the LFO mode to get a super simple LFO.

edit: thanks urs, didn't think about the slew mod, I will try.

[misterandy]

When using the Mapper as a trigger for an envelope it seems that to be able to retrigger the envelope you need to go to a negative value on a step to sort of "reset" it and then give it a positive value again. Is there a way to make it retrigger the envelope between successive steps? I guess what I'm looking for is a sequencer with modulation amount per step

[Urs]

When using the Mapper as a trigger for an envelope it seems that to be able to retrigger the envelope you need to go to a negative value on a step to sort of "reset" it and then give it a positive value again. Is there a way to make it retrigger the envelope between successive steps? I guess what I'm looking for is a sequencer with modulation amount per step

So the modulation system is "dumb", but therefore reliable. Mappers are bipolar, and bipolar sources trigger on positive zero crossings. Unipolar sources trigger when they cross 0.5 upwards.

If you need the Mapper to trigger on every step: Use the same source that also triggers the Mapper.

If you need a Mapper to be "this step triggers, but this one does not", still use the same trigger as the Mapper for whatever you want to trigger, but route it through a ModMath and multiply with the Mapper. This way you can switch individual steps on or off with the Mapper.

[Urs]

Just my personal opinion, but I realized my favorite solution is just more MSEGs. For soundscapes or complex pads it's doable to hit the 4 limit. But yeah, maybe I'm too used to Absynth.

Have you tried to copy & paste an MSEG into a Mapper yet? For evolving and particularly for LFO-like MSEGs this might be a quick fix.

[misterandy]

If you need a Mapper to be "this step triggers, but this one does not", still use the same trigger as the Mapper for whatever you want to trigger, but route it through a ModMath and multiply with the Mapper. This way you can switch individual steps on or off with the Mapper.

Thanks, that's a great workaround!

[stippenstoh]

Creating with Zebra can be a bit like solving math equations, unfortunately I sucked at math. For someone like me the video tutorials will be crucial, I'm hoping for a 'popular tricks / workarounds' video.

[Urs]

Creating with Zebra can be a bit like solving math equations, unfortunately I sucked at math. For someone like me the video tutorials will be crucial, I'm hoping for a 'popular tricks / workarounds' video.

I'm sure we'll do quite some!

[stippenstoh]

Creating with Zebra can be a bit like solving math equations, unfortunately I sucked at math. For someone like me the video tutorials will be crucial, I'm hoping for a 'popular tricks / workarounds' video.

I'm sure we'll do quite some!

[ehgdae]

(If running Zebra with Novation is not an option, I will not purchase it.)

[pgwalsh]

+1 for moss

(While waiting for the Launchcontrol XL3 to be recognised by Moss for Reaper...)

Zebra3 behaves strangly behaviour with Ableton Live:
- it's right with simple MIDI Learn (but value scaling in takeover mode don't work with Zebra3, values jumps)
- so, what is really surprising:
when I configure the instant mapping in the device of Live for Zebra3 (also similar problems with Zebralette2), some parameters don't works on the Novation Launchcontrol XL3. For example, if I configure Vol of OSC1 then Vol of OSC2, only Vol of OSC1 works. If I start with OSC2 and then OSC1, it is only OSC2 that works. Same with other parameters of the OSCs. Same behaviour with the envelope modules and so on. Sometimes it's more erratic than that, difficult to explain.

Maybe a bug by Novation? But only Zebra make this behaviour.

Anyway, thank you Urs

(If running Zebra with Novation is not an option, I will not purchase it.)

Now there's a reference to the original issue.

[Urs]

(If running Zebra with Novation is not an option, I will not purchase it.)

I guess then they better get it fixed, whoever is responsible for the bug or whatever it is...

[Urs]

(I think the issue might be related to a faulty/sloppy implementation of VST3, AU or CLAP on the host side where the status quo for plug-in parameter support is still on the ancient level of VST2, and where the meta data for parameters such as the module name is not respected, and then Osc1:Volume and Osc2:Volume are just "Volume", with the Osc part missing, and then the host or the environment can't comprehend the difference)

[ehgdae]

Thank you
I asked this question here because I only have this problem with Zebra. Other plugins, also in VST3, do not have this problem. But okay, I'll check with Ableton and Novation...

[Urs]

We might be the only ones whom extensively use parameter meta data as it is supposed to be used.

[ehgdae]

Yes, Urs, I recognise the quality of your work because I had Zebra 2 and Zebra 3 is awesome. I plan to switch back to Zebra with version 3. From my point of view, if others don't properly respect the metadatas but everything works correctly, that's fine with me. This metadatas are certainly important for reasons I don't know about. If my problem is insignificant, please don't worry about it, I'll manage to find a valid solution with what exists. In any case, thank you again.