Zebra 3 Public Beta 3 Revision 20977

[Urs]

Also, is there a reason the Ctrl A, B, C, D knobs aren't MIDI-learnable? Is this something that's still being worked out pursuant to the "special note" in the changelog?

They are not just MIDI Learnable, they can be set to any MIDI CC per instance. The default CC is set in the preferences section, the per-instance setting is on the MIDI table page. The "Control" of their name refers to "MIDI Control Change".

But as we now have them on the UI, maybe we can indeed add the assignment of the MIDI Control Change into them as well...

(They are actually evaluated at control rate, which is near sample accurate, with adaptive de-zippering - much more accurate and responsive than MIDI-learned parameters, or automated ones. They also know their MIDI Channel, so if you send notes on channel, you can send them different A/B/C/D than those notes you play on another... a pre-requisite of MPE btw)

[Urs]

We do this in Surge XT, it's consistent UX according to the name of the option. If you hide the cursor when dragging, it happens everywhere, in step sequencer table as well as sliders and when editing MSEG nodes. ^_^;

Well, you use a replacement cursor by highlighting something else that appears to follow the mouse...

... and you're highlighting steps in the mapper. So realistically this could also work in Z3 much in the same way, I'd say

Sure...

However, in a control with horizontal and vertical movement, it would be a mistake to "freeze" the position of the mouse cursor. Like, when you drag a point in an envelope and you lift the mouse button, you definitely want the mouse pointer to appear where that point was dragged. So by my account, in this case hiding the mouse pointer is YAGNI.

In fact, the only reason the mouse pointer is hidden is because of the freezing. The freezing is the main reason to do this, to be able to drag a control value beyond the screen estate. But if the mouse pointer is visible and frozen, it looks like a bug. Hence, hiding it.

So in my view, there is no need to hide the mouse pointer when the control boundaries never need to be exceeded. (which doesn't mean we won't improve things further... apparently the planned 1-2 weeks for implementing this have already become twice or thrice as much due to platform specific quirks and all that)

[EvilDragon]

That's fair. But with Shift pressed, you do exceed the boundaries of the mapper widget many times over, that's the issue here. Looking forward to improvements!

[david.beholder]

Btw Urs returning with question about Z3 interface

As person with bad vision I use larger fonts. The way it works on mac is by reducing resolution of the display. My resolution is 1344 x 840 and z3 only works with 80% of size in it and fonts are just too small.

[Urs]

Btw Urs returning with question about Z3 interface

As person with bad vision I use larger fonts. The way it works on mac is by reducing resolution of the display. My resolution is 1344 x 840 and z3 only works with 80% of size in it and fonts are just too small.

The final UI will be much more readable, more visually consistent and tidy. The font contrast and size in particular will be increased.

[tasmaniandevil]

Do i have to backup these module presets first,....is a new install overwriting the whole folder ?
where can i find the Folder ? ( Mac in my case)

The installer will only touch factory presets. If you added any presets or module presets, the installer will not touch these.

If you want to back them up first, just in case, you can find the module presets here on Mac:

/Library/Application Support/u-he/Zebra3/Modules

You can also easily reach that location from within the plugin.
If you click the little arrow to display the module preset menu, you'll find a "Show in Finder" option.

[david.beholder]

The final UI will be much more readable, more visually consistent and tidy. The font contrast and size in particular will be increased.

That's great news.
I'm ready to be any kind of guinea pig if needed.

Btw is there any update on light theme?

[tasmaniandevil]

Only had 5 mins with the new firmware yet, but the ringmod is now displaying its frequency in Hz. kinda cool but before i knew that values like 24, 48 for example had a 1_1 ratio when tracking pitch. I kind of miss that. You can ofcourse do it by ear, but before, values & multiples of like 5, 7, 12 like in pitches allowed you to know the kind of stable centres quickly.

There's a "Show Raw Parameter Values" option in the preferences.
You can choose to display just one or both values.

[tasmaniandevil]

Right-clicking an empty slot in the grid (doesn't matter which one), has a disabled entry on top that says "Add &_Paste". Not sure if that's intentional or not, if it is intentional, then the underline should be a whitespace. If it's not intentional, it should not be there period.

It's intentional. Once you copied a module in the grid, you can add and paste it.

I have no idea where that underscore comes from.
I checked VST3 and CLAP on Mac and Win, it looks totally fine everywhere, there is no underscore.

[Urs]

same here

[PieBerger]

Btw is there any update on light theme?

Blasphemy!

[Urs]

hehehe, the UI team is pretty heavy at work, but still mostly working on a dark theme. Which I guess they'll turn light as well, eventually.

[eclipse_soundlab]

anyone has a problem with silent presets?

[EvilDragon]

I have no idea where that underscore comes from.
I checked VST3 and CLAP on Mac and Win, it looks totally fine everywhere, there is no underscore.

The underscore comes from the & character, I reckon. In Win32 API using & in a context menu entry specifies the letter that triggers that menu entry when you're Alt-walking context menus. So then you need to use "&&" instead of "&" if you want to show the & character. Then that character gets underlined. So in this case it could be that this was an overzealous & compensation so instead of "&&", "&&& " was typed, which would result in an "&_" situation.

This would never show up on Mac. But it definitely shows here, regardless of DAW (but that part is unsurprising since it's using OS-based menus after all).




And just to be sure: this is indeed happening with rev 20977.

[tasmaniandevil]

Actually a bug: if you Shift+mousewheel on mapper steps, there's no UI refresh happening. You can see the value changing in the display atop, but the matchstick doesn't change its size.

It does move, but since Shift + mouse wheel is so slow, it moves very slowly. That works way better on Mac. Will create a ticket for improving this on Windows.