Zebra 3 Public Beta (final beta)

[Urs]

Z2 patches will not work in Z3. Did I hear that right?

That is correct. Z3 is a completely new development.

[SamDi]

Auto-detect checks if you are using a vertical mouse wheel or a mouse with a vertical and a horizontal wheel. As long as you just scroll vertically, all controls will react to vertical scrolling. Once you actually use horizontal scrolling on your mouse or trackpad, it switches the plug-in's mode, so it uses vertical scrolling for vertical scrollbars and horizontal scrolling for horizontal scrollbars.
If you switch it to "vertical only", then all scrollbars will react to vertical scrolling only.
If you then switch back to "auto-detect", it's back to vertical scrolling for vertical bars and horizontal scroll for horizontal bars.

That sounds pretty over-engineered, but not in a good way. I don't even understand, what should be the point to have these setting options or which benefit should they add?

Wouldn't be normal expectation:

-vertical wheel -> vertical scrolling
-horizontal wheel -> horizontal scrolling
-vertical wheel + modifier key (shift is more common than ctrl BTW) -> horizontal scrolling
-horizontal wheel + modifier key (nobody is using it, but it's often implemented ITO consistency) -> vertical scrolling

???

And (not so common or often implemented but useful):
-vertical wheel when only horizontal scrolling is available -> horizontal scrolling

Why these settings are needed then?

[El°HYM]

Thank you Urs for the great release & the T-Shirt!

A short Question about Zebralette 3, was MTS-ESP dropped for a reason or will it be (re)_added in a future Update?

Would be sad to see this feature (even being niche) been gone.

I didn't know MTS-ESP was dropped from Zebralette. Are you certain?

You are right, sir. Not sure what happened on my side, tested with some different MTS- ESP Master plugins and the client wasnt seen. Also searched Zebralette 3 plus MTS-ESP and didnt find anything about it. Yet, this is now all working just fine and as usual, so must have been on the user side. Sorry for the confusion and many thanks for this excellent little synth.

A short Question about Zebralette 3, was MTS-ESP dropped for a reason or will it be

i just tried it with RCv20354 of zebralette3, AU version in Logic:
showing up in MTS-ESP, working fine here...

which version are you using ?

REV 15573 Beta with Live 12. Problem got resolved though and seems to have been on my side.

What's this about a T-Shirt?

[teilo]

The "Every new synth sucks" club is out strong. Bless their hearts.

You too can join the club in three easy steps:

1. Be firm in your conviction that every new synth sucks.
2. Install the new synth and figure out where it sucks.*
3. Tell everybody this new synth sucks.

* Sometimes this part is hard, because even though you know it sucks, it can be difficult to find the suckage. But don't worry. You can always just grab one of these classic standbys:

• "It sounds cold/artificial/digital."
• "The UI has <insert a random control here> and that sucks."
• "The presets are garbage."
• "The workflow is crap."
• "I hate the copy protection."
• "The price is too high and they are just out for your money."
• "The price is too low, and they are flooding the market with crap."
• "u-He is a CLAP whore."

Good luck!

[Urs]

That sounds pretty over-engineered, but not in a good way. I don't even understand, what should be the point to have these setting options or which benefit should they add?

Accessibility for people with different kinds of devices, such as trackpads, mouses with built in trackpads, mouses with two wheels and so on.

[SamDi]

That sounds pretty over-engineered, but not in a good way. I don't even understand, what should be the point to have these setting options or which benefit should they add?

Accessibility for people with different kinds of devices, such as trackpads, mouses with built in trackpads, mouses with two wheels and so on.

Hm don't know. I have a mouse with 2 wheels and have never encountered problems to need specific settings for that. Also I have used trackpads and trackballs. I am not aware of any other SW having such setting options. Most just implement the standard behaviour instead.

Really sure Zebra needs this?

[Urs]

Really sure Zebra needs this?

Pretty sure. Otherwise I can't shift-scroll for fine tuning at all with my ordinary single wheel mouse.

[Funky40]

• "It sounds cold/artificial/digital."

- i like those ! ymmv

[*]"The presets are garbage."

- they usually have been.

- U-HE got Howard Scarr on board. That was a clever move

- while SW has "now" widespread some great preset makers around.

- But don´t ask me vs. my opinion on HW.....

[SamDi]

Really sure Zebra needs this?

Pretty sure. Otherwise I can't shift-scroll for fine tuning at all with my ordinary single wheel mouse.

Of course. As long as your pointer is over a knob, fader or other widget, the wheel focus is there and when it's not on a wheel-sensitive widget then it scrolls. Not a topic about vertical vs. horizontal and modifier keys, but where the wheel focus is.

[wagtunes]

Z2 patches will not work in Z3. Did I hear that right?

That is correct. Z3 is a completely new development.

So then we need to keep Zebra 2?

[Benjamin923]

Yes, if you want to use Zebra 2 sounds you will have to keep it around. It will continue to get product support.

[Urs]

Really sure Zebra needs this?

Pretty sure. Otherwise I can't shift-scroll for fine tuning at all with my ordinary single wheel mouse.

Of course. As long as your pointer is over a knob, fader or other widget, the wheel focus is there and when it's not on a wheel-sensitive widget then it scrolls. Not a topic about vertical vs. horizontal and modifier keys, but where the wheel focus is.

It's just that if we support horizontal scrolling, which we want, and the user has a single wheel mouse, the operating system (macOS in this case), interprets shift+scroll as horizontal scroll. In that case, our controls don't see this as shift-scroll, they see it as horizontal scroll.

With a trackpad etc. shift-scroll arrives as shift-scroll. With a normal mouse, vertical scroll.

So by having a preference, we can enable shift-scroll on an ordinary mouse.

I don't know atm how to put it easier. I hope it's clear, and if not, I'll get our writers to clarify it in the user guide.

[kraster]

The "Every new synth sucks" club is out strong. Bless their hearts.

You too can join the club in three easy steps:

1. Be firm in your conviction that every new synth sucks.
2. Install the new synth and figure out where it sucks.*
3. Tell everybody this new synth sucks.

* Sometimes this part is hard, because even though you know it sucks, it can be difficult to find the suckage. But don't worry. You can always just grab one of these classic standbys:

• "It sounds cold/artificial/digital."
• "The UI has <insert a random control here> and that sucks."
• "The presets are garbage."
• "The workflow is crap."
• "I hate the copy protection."
• "The price is too high and they are just out for your money."
• "The price is too low, and they are flooding the market with crap."
• "u-He is a CLAP whore."

Good luck!

Just to add:

[*] This synth isn't exactly like X synth therefore it sucks (X synth also sucked when it was new but let's not talk about that now)

[El°HYM]

I like Aliasing, it makes my dog fall asleep.

[Surgo]

Auto-detect checks if you are using a vertical mouse wheel or a mouse with a vertical and a horizontal wheel. As long as you just scroll vertically, all controls will react to vertical scrolling. Once you actually use horizontal scrolling on your mouse or trackpad, it switches the plug-in's mode, so it uses vertical scrolling for vertical scrollbars and horizontal scrolling for horizontal scrollbars.
If you switch it to "vertical only", then all scrollbars will react to vertical scrolling only.
If you then switch back to "auto-detect", it's back to vertical scrolling for vertical bars and horizontal scroll for horizontal bars.

That sounds pretty over-engineered, but not in a good way. I don't even understand, what should be the point to have these setting options or which benefit should they add?

If you see a UI feature that seems complex and you don't quite understand it, a good exercise is to imagine yourself as blind and using input devices for the blind. I don't know if it explains this particular one or not (I'm not in this particular beta) but it's a reason a great deal of stuff that a lot of people find pointless exists, with a very important point.