Zebra 3 Beta Bug Reports

[JustusSteinfeldt]

Bug Report: Roli Seaboard M Glide doesn't work for me
Version: Zebra 3, Rev 20977 (CLAP)
Operating System: Windows 11 Home 25H2, x64
DAW: Occurs in Reaper 7.65 and REAPER v7.61
Issue: I'm using the newest Roli Seaboard M connected via USB. Using Seaboard's Gliding feature it only pitchbends the note to approx. +/- 1 semitone, even though I glide over the whole 2 octaves of the Seaboard M. At the Perform section I've set the Zebra mode to MPE and the Pitch Bend ranges both to MPE. Sliding and AT works well but can't make Glide working yet. Had the problem both with the FMO and the Osc module. Also tested the Roli Studio Player VST on the same track and there Gliding works well.
Stunning Zebra 3 release. Looking forward to using it.

[tasmaniandevil]

Bug Report: Keyboard Shortcut for Deleting Curves Fails

If Backspace responds depends on the host forwarding it to the plugin. This is problematic on Windows.
In Reaper, it works when using CLAP, but not with the VST3.
In Bitwig, neither the VST3 nor CLAP react to it.
In Live, the VST3 works fine.
In Cubase, the VST3 doesn’t respond to it.
We’ll have another look to check if we can get the hosts to forward it, but it might not be possible.

[tasmaniandevil]

Bug Report: Roli Seaboard M Glide doesn't work for me

Oh yup, confirmed. It works okay in Bitwig, but not in Reaper and Live. We'll look into it. Thanks for reporting this.

[charlee8t]

Zebra 3 Public Beta 3 Revision 20977
Known Issues:

* Crash when deleting a mod slot right after opening the GUI (VST3 only)

Just reporting that I've been experiencing crashes also when trying to unassign modulation by right-clicking in the parameter, and with the GUI opened for a while.
Windows 10 - Nuendo 14

[SteveElbows]

Beta 20977, Mac Sequoia, various hosts.

MPE Pitch Bend is only using a very small range in hosts such as Logic Pro (AU) and Ableton Live 12 (VST3).

In Bitwig 6 the situation is more complicated with both the CLAP and VST3 versions. When Zebra 3 bend range settings are set to MPE, the bend range works properly, but as soon as main MPE button in Zebra 3 perform UI is switched on with the VST3 version, the bending is slightly less than it should be, causing unwanted tuning issues. In the CLAP version in Bitwig this issue happens whether the main Zebra 3 MPE button is on or not......

I decided to create a test project in Bitwig 6 to explore this issue more formally. Rather than using a MPE controller for this test, I drew the pitch bends into scene data in Bitwig:

Two C notes are played simultaneously, one octave apart. First I have the lower C quickly bend upwards until its an octave higher, matching the 2nd note. Later, I bend both down an octave.....

In a VST3 instance of Zebra 3, if main Zebra 3 MPE button is off, but pitch bend range in Zebra is set to MPE, the notes correctly match in pitch as expected. Then when I switch the Zebra 3 MPE button on, the problem can immediately be heard, the bends dont quite go far enough and so the two notes are not matching.

In a CLAP instance of Zebra 3, the faulty behaviour seems to occur regardless of whether the MPE button inside Zebra 3 is on or not.

In the following project, track 1 is the CLAP instance and track 2 is the VST3 instance. I wouldnt want to confuse the issue further by having both tracks making sound at the same time, so I was soloing tracks during testing.

http://pixelromp.com/Bitwig6Zebra3MPEPi ... roject.zip

If my explanation is unclear, solo track 2 and play the clip and then toggle the MPE button in Zebra 3 Perform UI on and off to hear what I am on about.

[tasmaniandevil]

Thanks, I can confirm the issue.
A one octave slide is off by one semitone in Bitwig.
In other hosts, it generally slides just one semitone.
We’ll look into it asap.

[JoeLowery215]

Seems like turning the ratio knob in FMO glitches out in the display. Anyone else?

[jasperdunn]

Is this huge amount of narrow band high frequency energy expected when adjusting the Feedback on an FMO? Aliasing artefact?
It just seems like a lot, I've never used any vintage FM gear, so maybe this is how they behave too?

[Urs]

Is this huge amount of narrow band high frequency energy expected when adjusting the Feedback on an FMO? Aliasing artefact?

Yes, just look at the waveform in a scope. First strong ripples appear, then chaos. This is how noise is made with FM.

[Urs]

Seems like turning the ratio knob in FMO glitches out in the display. Anyone else?

I'd need a screenshot...

[JoeLowery215]

Seems like turning the ratio knob in FMO glitches out in the display. Anyone else?

I'd need a screenshot...

Sorry but it has to be a video to see:

https://www.dropbox.com/scl/fi/dvo7y4je ... n0uqp&dl=0

[Urs]

I see... weird!

Thank you for sharing, we'll check it out!

[tasmaniandevil]

Sorry but it has to be a video to see:

Hi Joe, could you contact our support about this, please?

So far, we haven’t been able to reproduce the glitch. Would be great if we could gather some more details.

[JoeLowery215]

Sorry but it has to be a video to see:

Hi Joe, could you contact our support about this, please?

So far, we haven’t been able to reproduce the glitch. Would be great if we could gather some more details.

Thanks but it actually stopped!

[NAD]

Zebra 3 Rev 20977, Windows 11 24H2, Reaper 7.53

Preset demonstrating the bug:

bug.zip

Steps to reproduce:

• Put an 8-Tap delay in Lane 2 (i.e. bus 1) in the FX grid
• Set it to receive input from Lane 1
• Set the Dry/Wet to fully wet
• Turn up the volume for Bus 1
• Play some notes

I'm not hearing the delay at all. When I try the same with the regular Delay module it works as expected. I'm quite certain this was working properly in the previous betas. For example, the preset I shared in this post has the exact same problem. Turning up Ctrl B is meant to introduce some delay, which it most certainly did when I created the preset in a previous beta but not in the current one.