Zebra 3 3.0 RC1 Revision 21793

[surreal]

Hi Urs and Victor, May I ask when will multicore support be implemented... this is literally the only one feature that i am waiting for... my cpu can run 7 instances of repro 5 so I wonder how it will cope with this final Rc version.

We had feature freeze some time ago... we'll give multicore a try once we figure out how to do it on modern asymmetric CPU structures.

Thank you for your reply Urs, how would this compare CPU wize to Repro 5 on a single core cpu performance?

[Eluwei]

...

[tasmaniandevil]

Does it mean that preset loading is flawed completely? I don't understand why it's only the init preset? Do you mean Bitwig's init preset mechanism? Do you know if this will be fixed in Bitwig 5, too?

No, preset loading is not flawed. This only affects our internal "init preset" function (right-click the data display to find it) when using the CLAP version in Bitwig.

With Bitwig 5.3, Bitwig introduced a new Undo/Redo system. And this somehow interferes with our init preset function when using CLAP. The moment our plugin loads the init preset, Bitwig tries to undo this, leading to an init preset that still contains remnants of the previously loaded preset.

We still hope they will fix this.

[Eluwei]

...

[cb8rwh]

It's in the settings

SCR-20260416-rpht.png

Have been reading through the manual and wanted to ask how to de/activate preset Auto Versioning. The default is that it's active.

The manual indicates:

"PRESETS
Auto Versioning
If switched on, an index is appended to the preset name and automatically incremented each time
you save it. For instance, saving ‘Space’ three times in a row would give you three files: ‘Space’,
‘Space 2’ and ‘Space 3’."

... But there appears to be no information about how to toggle preset auto versioning on/off.

[Eluwei]

...

[orbitfold]

Expanding the FMO parameters with the down facing arrow button at the bottom scrolls to the top to the top of the generator rack automatically? Making the expanded parameters invisible until scroll back down again. For this to happen the FMO has to be low in the list so that you need to scroll down to see it in the first place. I don't see that in the known issue list.

[Urs]

Expanding the FMO parameters with the down facing arrow button at the bottom scrolls to the top to the top of the generator rack automatically? Making the expanded parameters invisible until scroll back down again. For this to happen the FMO has to be low in the list so that you need to scroll down to see it in the first place. I don't see that in the known issue list.

I can't reproduce that here. But if you have the Rack preferences on "selected on top" and you also click the FMO panel background, then the FMO gets selected and pops to the top of the rack. Is that maybe what is happening?

[karrikuh]

Bug: In the MSEG editor, if I create a new break point with Alt+Click and move the mouse while button still pressed, the new breakpoint disappears and selection is created instead.

Expected: The new breakpoint should move until mouse button is released just like in a normal click+drag operation.

[tasmaniandevil]

Bug: In the MSEG editor, if I create a new break point with Alt+Click and move the mouse while button still pressed, the new breakpoint disappears and selection is created instead.

Hmm, might not be easy to solve. Alt + drag is used to append to the current selection.

[orbitfold]

Expanding the FMO parameters with the down facing arrow button at the bottom scrolls to the top to the top of the generator rack automatically? Making the expanded parameters invisible until scroll back down again. For this to happen the FMO has to be low in the list so that you need to scroll down to see it in the first place. I don't see that in the known issue list.

I can't reproduce that here. But if you have the Rack preferences on "selected on top" and you also click the FMO panel background, then the FMO gets selected and pops to the top of the rack. Is that maybe what is happening?

https://www.icloud.com/iclouddrive/0f5i ... 7_09-41-34

[DrWashington]

+1 for multicore support. I hope the figuring it out for modern CPUs turns out to be easier than expected. If only you could throw Claude Mythos Preview at it, no? Seems to be able to figure damn near anything out, frighteningly enough...

[tasmaniandevil]

https://www.icloud.com/iclouddrive/0f5i ... 7_09-41-34

I can’t reproduce it either. Neither Mac, Win nor Linux, in Bitwig.
Which operating system are you using? And VST3 or CLAP?
Is this happening only with one particular preset, or with any?

[neverbeeninariot]

Hi,

I think I've found a bug in the Matrix (apologies if already reported/known)

Init patch.
Assign MW to ENV1 Decay and Release, add some modulation values.
Close Z3 UI then open again.
The mod slots are there, but the slot numbers, source and dest labels, and modulation amounts are invisible.

The issue is repeatable in a fresh project with Bitwig or Reaper.
Win10 (latest ESU), Bitwig 6.0.3, Reaper (7.69), clap version of Z3 RC1 21793.
AMD Ryzen 9900, AMD Radeon 9070

EDIT:
It is repeatable only if the UI scale is not at 100% (I'm typically at 110%).
Resetting the UI scale to 100% and closing and re-opening the UI restores the missing information although it is lost again if you scale to any other size.
.

[zvenx]

Not happening on Mac 26.4.1, Cubendo 15, M1 Max.

And I am at 110% too.. but Tas seems to be able to replicate it, I think?
rsp