Zebra 3 Teething Troubles

[exmatproton]

i got one; my displays run @ 144Hz. When i modulate a parameter thru the modmatrix with a MSEG, the UI of Z3 runs at ~40 to 70 FPS. When i modulate that same parameter but via the mod slot beneath the parameter, Z3 runs @ 144 FPS. Tried other mod sources, but so far only the MSEG gives that result and only when attached to a parameter (tried the Spectral Decay parameter) via the modmatrix

[carrieres]

-Windows11 can kiss my entire %$#%$#!

Which version of Windows11 works and wich one does not work ?
I mean 23H2, 24H2, 25H2 ...

I can no longer say, as there have been too many win updates in the last 2 months to really unroll it all without doing a lot of research. The issues Im having on numerous DAWs on Win11 began about 2 months ago, right after I built it, and then became worse over time, resulting in performance problems, audio distortion, etc. Probably a dozen win updates have gone in over the time Ive been dealing with this. Sorry!! I wish I could point at a version and say "it started here" or something, but I cant. : /

what is your current Windows version ?
It will help me a lot

[Milkman]

-Windows11 can kiss my entire %$#%$#!

Which version of Windows11 works and wich one does not work ?
I mean 23H2, 24H2, 25H2 ...

I can no longer say, as there have been too many win updates in the last 2 months to really unroll it all without doing a lot of research. The issues Im having on numerous DAWs on Win11 began about 2 months ago, right after I built it, and then became worse over time, resulting in performance problems, audio distortion, etc. Probably a dozen win updates have gone in over the time Ive been dealing with this. Sorry!! I wish I could point at a version and say "it started here" or something, but I cant. : /

what is your current Windows version ?
It will help me a lot

Its Windows 11 pro 25H2, with preview build 26200

Sorry for putting all this here(move it if needed), but I thought it could also help everyone troubleshooting any Zebra3 issues they have:

Bitwig 6 and Cubase 15 have both bluescreened at least 2 times each during various operations inside the DAWs. When indexing the file system. When loading a synth. When authorizing a plugin.
Ive been able to recover from these bugchecks and restore projects, and it appears that once the initial authorizations and first-run setups calm down, the bluescreens seem to calm down... but I dont appreciate windows 11 much at all. Its a horrible step down from windows 10, its noticeably slower on startup and on numerous other file system tasks than 10, and I have of course done my due diligence to ensure my hardware is clean.

But right now, as long as I dont authorize anything new or trigger large file indexing operations inside those DAWs, things are smooth, audio is very clean in both DAWs, MIDI devices are attaching reliably and their scripts are good, and I can make music. Zebra3 is perfect, and I am happy with that. Maybe Ill sneeze later and win11 will puke all over again. Who knows. Im migrating to open source as we speak, but its slow...

[SteveElbows]

They tried to get MIDI right with the major update to that side of Windows, but in the end they failed to avoid major issues for some users initially. I suppose I'm not surprised really because the mistakes made were really down to a very very long period of neglect of the Windows MIDI subsystems. So when they finally got round to updating it to support MIDI 2.0 etc, it ended up being a major rewrite that was bound to introduce issues to start with. Especially as they were trying to ensure compatibility with old hardware and software, and its hard to get that right. When they iron out any remaining issues its actually a pretty good system now, and the pain points people lived with for decades are gone. Just have to deal with the new pain points till everything settles down.

[joradn]

The description for mod noise seems to be

[Matty686]

That release knob on that mseg of yours is begging for release velocity as a modulation option lol (I hope it comes soon) sorry I know I've kinda said this a lot

[pdxindy]

That release knob on that mseg of yours is begging for release velocity as a modulation option lol (I hope it comes soon) sorry I know I've kinda said this a lot

Fortunately for me, Release Velocity works in Z3 CLAP in Bitwig!

[Matty686]

That release knob on that mseg of yours is begging for release velocity as a modulation option lol (I hope it comes soon) sorry I know I've kinda said this a lot

Fortunately for me, Release Velocity works in Z3 CLAP in Bitwig!

quoting the manual

"release: maximum after a note is released (practically the opposite of GAT) "

I believe what your using is called release witch is a note off gate signal.

but if I'm wrong and you have actually found release velocity do let me know were you found it.
urs said it wouldn't be hear until version 1.2 maybe he was not quite sure

I probably should have shut up about it after that but I get anxious.

I am kind got spoiled by anamoogs touchpad on my Ipad and want similar stuff in Bitwig but easily programable and per note. I figured out using phase plant how to do this by combining velocity>attack Timbre>volume and pitch and release velocity > release time

I have been studying release velocity since I started music 5 years ago it's kinda my hyper fixation. I actuly haven't built anything with zebra 3 yet because im waiting for this feature. sad I know but my entire synth organization system is built around release velocity being a huge category in my synth library so I don't want to get started making stuff until its hear.

when release velocity is available and urs told me it will be I can start setting up

I plan on sharing with everyone how to set up a on/off velocity driven woodwind synth because I think people might like it. Maybe ill do a YouTube video or somthing

[pdxindy]

I believe what your using is called release witch is a note off gate signal.

One of the Bitwig Note Expressions is Release Velocity.

You can use a keyboard that supports Release Velocity, or you can manually set the release velocity per note in the Bitwig Detail Editor.

Then using the CLAP version of Zebra 3, add the Expressions modulator to it (Velocity, Timbre, Pressure, Release Velocity are the 4 mod sources). Assign Release Velocity to whatever automatable parameter you want in Zebra 3 (Amp Env Release is a common choice).

[Matty686]

I believe what your using is called release witch is a note off gate signal.

One of the Bitwig Note Expressions is Release Velocity.

You can use a keyboard that supports Release Velocity, or you can manually set the release velocity per note in the Bitwig Detail Editor.

Then using the CLAP version of Zebra 3, add the Expressions modulator to it (Velocity, Timbre, Pressure, Release Velocity are the 4 mod sources). Assign Release Velocity to whatever automatable parameter you want in Zebra 3 (Amp Env Release is a common choice).

dud omg thanks so very very much

I did not even remember that existed

thank you thank you thank you

you made my day

[eclipse_soundlab]

i can't set mseg loop to 1.5 it's either 1.49 or 1.51

[pdxindy]

i can't set mseg loop to 1.5 it's either 1.49 or 1.51

I just tried and had no trouble setting loop speed to 1.50 (also can do 1.49 and 1.51)

Maybe double click the knob to reset it. Or you can hold shift for fine adjustment.

[Urs]

i can't set mseg loop to 1.5 it's either 1.49 or 1.51

I just tried and had no trouble setting loop speed to 1.50 (also can do 1.49 and 1.51)

Maybe double click the knob to reset it. Or you can hold shift for fine adjustment.

It depends on whether you use the raw parameter value (it's possible there, easily) or the parameter value converted to a meaningful unit. In this case, as the Loop parameter is interpreted exponentially, there's no exact match. One would have to be able to reach 0.5849625007 on the raw parameter, but it's only ever 0.58 or 0.59.

[lindwyrm]

Hi everyone!

I already reported this on the website but perhaps I should write it here as well.

When I use an MPE controller, the timbre modulation (piped to Control A) is jagged / there's significant aliasing. It does not seem to vary under different slew rates. When I automate Control A directly, it's smooth.

MPE / Note expression:


Automation / wiggling the control directly:


Depending on the modulation target, this creates audible noise (e.g. a simple noise -> modal patch with the modal position and crossfade modulated by control A).

Can anyone reproduce this? Or is this expected behavior?

(I am on Bitwig 6.0.6, MacBook Pro M1 Pro)

[jooster]

I run into 2 problems, the first one often:
1. Control ABCD goes dead i.e. any cc on the appropriate channels (in my case 16..19) stop working as control ABCD. Strangely, I see the CC signals arrive in Logic and they are recorded in logic. I can also use any of these four to use midi learn inside Z3 to directly assign to a parameter. But they stop working for the ABCD controls. Restarting Logic does not make a difference, creating a new project also not. But restarting the Mac does.

2. I have a few presets from zebralette3 I try to load - I understand the conversion is not yet working? Anyway, the preset invariably messes up any other true z3 preset I select thereafter. Perhaps not entirely weird as the zebralette preset may have left memory in an undetermined state. However, after an init it may or may not work i.e., I can load a zebralette patch, get wacky results, do init and load a z3 patch abc, then do it all over again and the second load of the same z3 abc patch may or may not work. So must I conclude 'init' is not a complete initialization?