Zebra 3 Beta Bug Reports

[pdxindy]

As an end result, I'd expect being able to move the MW and for Bitwig Studio to see the last touched parameter so I can easily automate it (in my experience, pretty standard for MWs and macros on softsynths). If it's not a Bitwig Studio shortcoming (also tried Studio One 7), it seems unfortunate that these main controls that typically have the most influence over a preset's sound would need some special MIDI handling compared to all of the others which just work with ease. Hope you find a good solution to this.

For automation, create an automation lane for CC1 (Modwheel) and automate to your hearts content.
For Bitwig modulation, use a Midi CC device and modulate the CC1 knob.
Otherwise, use a mod wheel or knob on a midi controller t draw in automation.

It's all easy to do in Bitwig.

[Super Piano Hater 64]

Didn't work... Tried with VST3 and CLAP, no dice. Searched every setting in the Reaper preferences with "reset" or "flush", none of 'em helped. Oh well, I can live with it I guess...

It's a Zebra3 setting, not a host setting. Click the gear icon, click the wrench icon, and look under the section titled "AUDIO & MIDI." It's the first entry.

[magickalmutagen]

For automation, create an automation lane for CC1 (Modwheel) and automate to your hearts content.
For Bitwig modulation, use a Midi CC device and modulate the CC1 knob.
Otherwise, use a mod wheel or knob on a midi controller t draw in automation.

It's all easy to do in Bitwig.

My question is just why would I need to do any of that when using a softsynth? I don't think I've come across another softsynth where one must look up MIDI CC values to be able to control a common part of it. But yes, it's doable, but to be required to do so just comes across as antiquated in this context.

[pdxindy]

My question is just why would I need to do any of that when using a softsynth?

Because it's a beta and u-he already said it would be addressed. In the meantime, it is easy to work around in Bitwig.

[Urs]

I don't think I've come across another softsynth where one must look up MIDI CC values to be able to control a common part of it.

I found this very hard it believe, so I asked an AI to figure this out for me.

So literally every synth offers MIDI Learn, just like we do, and some popular synth have pre-defined mappings that you'd need to look up.

However, in regard of the modulations system or ModMatrix, the AI thinks that your statement is true for synth developments post Serum, such as Vital and Pigments. But for instance Omnisphere has a User CC that works just like our Ctrl A/B in Diva, Zebra and Repro. But then for ModWheel and Pitchbend, things are still pretty split: Serum (via Macros), Vital, Sylenth1 offer parameter automation, while Omnisphere and Pigments do not.

The AI furthermore thinks that it is very likely that the Macro approach (where the MIDI CC can be MIDI learned instead of used in the ModMatrix directly) is evaluated at buffer size. Hence it would not be possible to send any near-sample accurate modulation.

Mind you, this beta phase is literally the first time it came up for Ctrl A/B, which we had for 25 years, when it started as support for MIDI CC 2 (Breath Controller) and 11 (Expression). We however quite often have requests to automate Pitchbend or Modwheel as parameters.

I'll get one of our devs to focus on this before the release and evaluate how to mimic the parameter automation support of recent synth while maintaining the 800+ Hz granularity on larger host buffer sizes for classic MIDI messages (or you use CLAP, where we support 64 sample granularity for host automation as well).

[NAD]

Didn't work... Tried with VST3 and CLAP, no dice. Searched every setting in the Reaper preferences with "reset" or "flush", none of 'em helped. Oh well, I can live with it I guess...

It's a Zebra3 setting, not a host setting. Click the gear icon, click the wrench icon, and look under the section titled "AUDIO & MIDI." It's the first entry.

Yeah I could have made myself more clear... I meant that I tried the suggestion Urs made ("Automatic Reset on Playback") and then went fishing for DAW settings after that didn't work.

[exmatproton]

didn't find this one in the 'known issues list'

When modulating a parameter (knob) the modulation indicator will still show when the modulation has been removed.

indicator mods.jpg

[tasmaniandevil]

When modulating a parameter (knob) the modulation indicator will still show when the modulation has been removed.

Yep, we are on it. This was working fine just a week ago, but somehow broke in the new beta.

[tasmaniandevil]

Have attached zip with files and details for you

Thanks for the presets.
The one preset you didn't update yet, and which still causes issues, is a Zebralette 3 preset, not a Zebra 3 preset. I assume the others had originally also been Zebralette 3 presets, right?

The preset converter that allows the loading of Zebralette 3 presets in Zebra 3 is still work in progress. This might explain your issue.

[psychedelicspaniel]

Have attached zip with files and details for you

Thanks for the presets.
The one preset you didn't update yet, and which still causes issues, is a Zebralette 3 preset, not a Zebra 3 preset. I assume the others had originally also been Zebralette 3 presets, right?

The preset converter that allows the loading of Zebralette 3 presets in Zebra 3 is still work in progress. This might explain your issue.

Thanks for taking a look! Yes, the non-updated preset was a Zebralette 3 creation (sorry, my error) but the other 2 were created in the 1st Z3 beta and didn't appear to have any issues, until beta 2

[exmatproton]

something weird is happening since this beta;

i opened the MAPPER1 tab, selected LFO1 as a modulation source (under INCREMENT), but the LFO won't show in the modsection on the right. After connecting MAPPER1 to a parameter, LFO isn't showing, but MSEG1 ís, while MSEG1 isn't controlling anything. So something is broken

edit: While LFO1 is visible as a modulator underneath INCREMENT, it is indeed the MSEG1 that is modulating it. So that is a bug

Yeah no..all is good.

[jooster]

1. drag and drop preset into z3 kills plugin and takes LP down with it as well.
2. presets created by zl3, loaded into z3 behave erratic. when I load a zl3 preset, then use left/right arrows to select another zl3 preset, the sound changes but the 'coding' does not. I.e., the patch continues to show as if wired up by that first preset.

[M32]

I mentioned this elsewhere, but when you set a mapper source to gate or trig and mode to increment, i was expecting the step position to advance every time a note is played, provided key reset is off.
Sometimes it does advance, but it seem rare and almost random.

Btw, when you use a trig source in the osc FX, how does the the actual triggered pattern/rythm relate to the source, like an lfo shape or mseg, isn't very clear to me. is it a rising edge like in eurorack, the max point,etc...?

Sometimes when you use both the local slots on a sound element module and a matrix modulation slot to assign sources, the matrix ones don't have any effect. And in general i rarely use the local slots cause they don't have a modifier.

[Urs]

I mentioned this elsewhere, but when you set a mapper source to gate or trig and mode to increment, i was expecting the step position to advance every time a note is played, provided key reset is off.
Sometimes it does advance, but it seem rare and almost random.

It advances per voice, so each voice goes through the first step, then the next and so on, proceeding every 16 notes.

That's admittedly not very intuitive. Maybe we should indeed handle trigger and gate like when nothing is attached, so it advances with each new note.

[tasmaniandevil]

1. drag and drop preset into z3 kills plugin and takes LP down with it as well.

What is LP? Logic Pro?

2. presets created by zl3, loaded into z3 behave erratic. when I load a zl3 preset, then use left/right arrows to select another zl3 preset, the sound changes but the 'coding' does not. I.e., the patch continues to show as if wired up by that first preset.

As noted in the known issues section, the import of Zebralette presets hasn't been fully implemented yet.