Zebra 3 final final beta 21764 April 14

[Zakast]

[edit1]

it would be great to have a user-friendly editor for this

Urs, in the previous topic, mentioned something about a guide or tutorial after Z3's release... viewtopic.php?p=9228501#p9228501

[edit2] Also, not for the weak-spirited/hearted, there's this too...

viewtopic.php?t=607522

[pdxindy]

FYI... that is a misquote. warcat said that.

[Zakast]

FYI... that is a misquote. warcat said that.

LoL, sorry 'bout that... Just noticed it myself

[bhinton]

Maybe another by-design/not-a-bug, and almost certainly too late, though if not a bug but also not by-design maybe can be fixed in a future release?

Choosing CC64 as the source for one of the control macros - let's say Control C - then assigning Control C to a direct modulation slot in a module works as expected: the modulation reflects the continuous nature of the pedal.

But if HOLD is chosen for direct modulation, it's just 0/127. On or off (as if using a non-continuous sustain pedal).

It would be great if selecting HOLD for direct modulation could transmit the continuous range when a continuous pedal is used to transmit CC64. This frees up a Control ABCD slot that otherwise would be available for another external midi control.

Especially useful for those of us who use three-pedal all-continuous units for our main stage keyboard.

[jrgillam]

In the mod matrix, it seems like pushing the mouse wheel up should increase the value in a positive direction, and down should decrease it in a negative direction. It's inverted for me. I'm on a Mac, but I have natural scrolling turned off, so in general pushing wheel up increases values on other parameters.

Go to the Preferences. You can tweak it there.

My mouse wheel is working as I believe it should based on the settings I have, except in the mod matrix where its behavior is now inverted to how it worked in the previous beta skin.

[Lawndart78]

You can always copy your presets to a different folder, then install the new beta and if you can't find your presets (which I doubt as with me everything went okay) you can always copy those back. Have fun!

Thanks. I saved what I've been using as user presets, updated, and everything seems to be working just fine. I loved the way this thing sounded from day one. It's wild that it went from the first iteration seemingly crashing if I moved my mouse wrong, to present, where I can have 10 instances going full tilt in a song I'm working on.

[tasmaniandevil]

I'd rather just hide the MSEG modules from the modulator lane. However, I do like adjusting the Mappers there. So for the future, please add the preferences options:
Show Both
Hide Both
Hide MSEG's
Hide Mappers.

(uh... I thought we had that... apparently not...)

There is a preference for that, you can choose to show or hide Mappers & MSEGs in the grid. You just can’t set this for each one individually.

[tasmaniandevil]

When I open a project in Bitwig, the fader positions for the mod wheel and Macros A - D are set to zero. This happens with both VST3 and Clap.

As mentioned in the known issues section, the MIDI macros feature is considered experimental at this point. These settings are not saved with presets or projects right now.

[Viktor [TUC]]

But if HOLD is chosen for direct modulation, it's just 0/127. On or off (as if using a non-continuous sustain pedal).

It would be great if selecting HOLD for direct modulation could transmit the continuous range when a continuous pedal is used to transmit CC64.

Especially useful for those of us who use three-pedal all-continuous units for our main stage keyboard.

This could however pose a problem for people with more standard sustain pedals then. Those standard ones that send only on/off - they behave strangely sometimes. I've seen pedals that send only two values, a 0 and a 127. I've ones which aim for "something below 63" vs "something above 64", but the actual values differ or even jitter. Allowing a continuous range would be problematic in these cases.

Viktor
u-he team

[tasmaniandevil]

In the mod matrix, it seems like pushing the mouse wheel up should increase the value in a positive direction, and down should decrease it in a negative direction. It's inverted for me. I'm on a Mac, but I have natural scrolling turned off, so in general pushing wheel up increases values on other parameters.

Go to the Preferences. You can tweak it there.

My mouse wheel is working as I believe it should based on the settings I have, except in the mod matrix where its behavior is now inverted to how it worked in the previous beta skin.

The previous beta with the old GUI did not have horizontal sliders in the mod matrix.

Switch the “Scroll Horizontal” preference to inverted.

[jrgillam]

In the mod matrix, it seems like pushing the mouse wheel up should increase the value in a positive direction, and down should decrease it in a negative direction. It's inverted for me. I'm on a Mac, but I have natural scrolling turned off, so in general pushing wheel up increases values on other parameters.

Go to the Preferences. You can tweak it there.

My mouse wheel is working as I believe it should based on the settings I have, except in the mod matrix where its behavior is now inverted to how it worked in the previous beta skin.

The previous beta with the old GUI did not have horizontal sliders in the mod matrix.

Switch the “Scroll Horizontal” preference to inverted.

Thank you. I understand it now, philosophically .

[exmatproton]

here is a package with presets i've made so far. More IDM oriented.
Comes as is; quality is all over the place. Some are aweful, some are actually quite good.
Use a limiter. do with it what you will

[todkon]

Did CPU Burn get removed recently? Can't seem to find it, it was a cool addition to force my M2 Pro to use the performance cores haha. Love the new theme, and that the filters no longer say WIP. Stoked for the imminent official release!

[Urs]

Did CPU Burn get removed recently? Can't seem to find it, it was a cool addition to force my M2 Pro to use the performance cores haha. Love the new theme, and that the filters no longer say WIP. Stoked for the imminent official release!

We removed it because some people left it on in their presets, and there's a good chance it'll stay on accidentally.

We are probably going to move the functionality into the Module Performance Meter directly, but that will have to happen in a subsequent update.

[Urs]

It seems that the issue with poorly visible dark gray text on a dark background, which many users have pointed out, still remains unresolved.

One person's great visibility is another person's eye strain.

We're weighing contrast, readability, information structure and everything very carefully to satisfy a wide range of preferences. We have tested this design with people, some of which are visually impaired. Please note that the main design process was done in the months before this release, we are only fixing bugs right now, such as missing labels or functionality.

We will be happy to provide more skins for different needs in the future, as we have with other products. We definitely want to create a lighter scheme. Hence, there won't be a need to rely on third party skins. But, this isn't a quick process.