Zebra 3 Public Beta 2 Revision 20552

[Urs]

Hello
I also want to report that something with the reverb FX is broken. I created a simple patch (1x OSC, 1x 18db linear LP filter and comp1 & Rev 1 on master fx and delay 1 on bus1) and everything was working until i added a new FMO where the synth didn't output any audio(or just really short snippet and then muted). deactivated and removed the FMO but still no sound. Deactivated rev 1 - sound was working again. Had to reload the plugin (reloading rev 1 didn't help) and now the patch with Rev 1 fx activated is working again.
Cheers Martin

That sound like left over bug in the FMO rather, maybe a division by zero. Once that happens, a weird mathematical thing called "not a number", short "NaN" can happen, and once it enters a delay based effect, that effects keeps emitting NaNs, which goes silent.

Usually it is not the fault of the Reverb, Delay, Filter or Chorus whatsoever, but some other module beforehand emitting a single faulty sample.

The reason we quickly updated Zebra 3 today a second time was a NaN being emitted from the Modal Resonator in a specific patch.

[NAD]

It was quite overwhelming at times (and time consuming).

Yeah some of that's on me, sorry! I've just been way too excited about this synth for so long, it's hard to keep it together

Anyway, loving the new modulation features, very comprehensive and very useful. The Laser target finder is a lot of fun. No notes, 10/10 (at least for now lol...)

Edit: Are the any new (global) presets by the way?

[Urs]

Edit: Are the any new (global) presets by the way?

Our content team has just started picking up from where they left off before Christmas. I was on workation myself until yesterday, I hope I get a briefing tomorrow.

[rmbles]

Just to say that the '808 designer' preset still crashes Reaper on Linux as soon as you play a note. Other presets are fine. This was the same in the first beta too.

[ThoughtExperiment]

Sorry, should have made it more clear. I don't mean the ABCD controls, they're OK. I mean eg if a modulation source in the Matrix is set to Pressure, I want to be able to change it to Breath. Because now you can have AT plus ABCD, so since I don't have an AT enabled controller, I need to change it to something else.
Hope I've explained myself better this time.

That's what the Control A-D parameters are for. Set one of them to Breath (CC 2)

I'm afraid I'm still not making myself clear.
For example, I'm trying out one of the included presets. It uses 6 modulation controllers: mod wheel, aftertouch and all 4 ABCD. I've mapped ABCD to cc 23 to 26, I have a mod wheel, but I don't have an aftertouch-capable keyboard so I need to reassign AT to another CC (I have a nanokontrol so plenty of sliders).

I hope that's clear, believe it or not English is my first language but sometimes I'm the only one who knows what I'm talking about. It's my useless super power

[pdxindy]

Sorry, should have made it more clear. I don't mean the ABCD controls, they're OK. I mean eg if a modulation source in the Matrix is set to Pressure, I want to be able to change it to Breath. Because now you can have AT plus ABCD, so since I don't have an AT enabled controller, I need to change it to something else.
Hope I've explained myself better this time.

That's what the Control A-D parameters are for. Set one of them to Breath (CC 2)

I'm afraid I'm still not making myself clear.
For example, I'm trying out one of the included presets. It uses 6 modulation controllers: mod wheel, aftertouch and all 4 ABCD. I've mapped ABCD to cc 23 to 26, I have a mod wheel, but I don't have an aftertouch-capable keyboard so I need to reassign AT to another CC (I have a nanokontrol so plenty of sliders).

I hope that's clear, believe it or not English is my first language but sometimes I'm the only one who knows what I'm talking about. It's my useless super power

In that case, I would remap breath to AT in the DAW so that Zebra receives the AT data.

[ThoughtExperiment]

--deleted, made a mistake, nothing to see--

[JoeLowery215]

Thanks Urs! I may have missed it but....the BURN module. Doesn't do anything for me other than glitch out and bring my CPU up to like 800%....anyone else? I don't really know what it does

[ere2learn]

Thats what it does, working as intended

[VitaminD]

Thanks Urs! I may have missed it but....the BURN module. Doesn't do anything for me other than glitch out and bring my CPU up to like 800%....anyone else? I don't really know what it does

I think that was designed to test newer Intel CPUs or trick them really into using the performance cores over the weaker, efficient cores. It does nothing sonically for you and can otherwise be ignored.

[Milkman]

I dont want to bother Urs with this -- I should keep using my beta key for the beta zebra even if I just bought a pre-release key? Or can I install the retail key now? I didnt see this posted anywhere, but I probably missed it.

[JoeLowery215]

Thanks Urs! I may have missed it but....the BURN module. Doesn't do anything for me other than glitch out and bring my CPU up to like 800%....anyone else? I don't really know what it does

I think that was designed to test newer Intel CPUs or trick them really into using the performance cores over the weaker, efficient cores. It does nothing sonically for you and can otherwise be ignored.

lol oh, well it's doing its job then!

[Funkybot's Evil Twin]

I dont want to bother Urs with this -- I should keep using my beta key for the beta zebra even if I just bought a pre-release key? Or can I install the retail key now? I didnt see this posted anywhere, but I probably missed it.

From the first post:

Known Issues:

* Beta Tester license card takes precedence over user license (workaround: delete the beta card)

[Milkman]

I dont want to bother Urs with this -- I should keep using my beta key for the beta zebra even if I just bought a pre-release key? Or can I install the retail key now? I didnt see this posted anywhere, but I probably missed it.

From the first post:

Known Issues:

* Beta Tester license card takes precedence over user license (workaround: delete the beta card)

lol I must be blind. Did not see this.

Cool! So I will delete the beta card, aim zebra3 at the retail card, and away I go. Thanks for the reply!

[ThoughtExperiment]

Sorry, should have made it more clear. I don't mean the ABCD controls, they're OK. I mean eg if a modulation source in the Matrix is set to Pressure, I want to be able to change it to Breath. Because now you can have AT plus ABCD, so since I don't have an AT enabled controller, I need to change it to something else.
Hope I've explained myself better this time.

That's what the Control A-D parameters are for. Set one of them to Breath (CC 2)

I'm afraid I'm still not making myself clear.
For example, I'm trying out one of the included presets. It uses 6 modulation controllers: mod wheel, aftertouch and all 4 ABCD. I've mapped ABCD to cc 23 to 26, I have a mod wheel, but I don't have an aftertouch-capable keyboard so I need to reassign AT to another CC (I have a nanokontrol so plenty of sliders).

I hope that's clear, believe it or not English is my first language but sometimes I'm the only one who knows what I'm talking about. It's my useless super power

In that case, I would remap breath to AT in the DAW so that Zebra receives the AT data.

Aftertouch doesn't have a CC number, so I can't remap it like that.
And it doesn't account for somebody wanting to use for example CC2 in ADDITION to whatever they've mapped to A,B,C and D. Hate to say this, but I can do this in Zebra2, Hive, Ace, and Repro...
I'm sorry but it still looks to me like the list of midi control numbers for automation isn't complete, so my question still stands: why is CC2 (Breath) missing?