Zebra 3 Public Beta Revision 20399

[Urs]

Has the download been updated to 6.0.2 in spite of the fact that it still says 6.0?

What do you mean by 6.0.2?

We have not updated the beta, yet. But we are making great progress with some of the more annoying bugs, which we hope to publish in early January.

[machinesworking]

Has the download been updated to 6.0.2 in spite of the fact that it still says 6.0?

What do you mean by 6.0.2?

We have not updated the beta, yet. But we are making great progress with some of the more annoying bugs, which we hope to publish in early January.

Since the Absynth 6.02 update came out, and Native Access still says 6.01, and the Falcon 26.03 update dropped with a similar issue the UVI Portal where it says 26. my guess is wrong thread.

[machinesworking]

I mean good taste in plugins though.

[Sascha Franck]

Here's a quick video we made about the CPU Burner, because we forgot to mention it in the preliminary user guide:

That is just incredibly wicked. Loving it.

[Matty686]

We would love to do that, but can't yet say when we do it.

The MPE specs btw. do not mention Release Velocity. But yeah, we'd love to support it.

Yeah, Release Velocity has nothing to do with MPE any more than regular velocity does. It's just the velocity value in the Note Off message. Lots of keyboards today support it without also supporting MPE.

Indeed, a (underused) aspect of the original MIDI spec rather than MPE.

I think part of the reason it got associated with MPE in the minds of some people is because ROLI used it as part of their '5 dimensions of expression' marketing that they were fond of, even though not all of those dimensions relied on MPE messages. And this ended up getting carried forwards as part of peoples general MPE awareness with subsequent MPE controllers etc.

And renewed interest in release velocity did end up overlapping with the era when MPE was on the rise, certain MPE synths becoming popular etc.

I prefer using release velocity instead of pressure primarily because hand-editing pressure curves significantly slows down my composing. For instance, a single minute-long MIDI track for any of my wind instruments can take up to two hours to program. However, if I use a combination of velocity> attack_time release velocity>release_time and Mod-wheel>breathIntensity, I can complete the same task in just 30 minutes. You can think of it as having three channel aftertouch kinda like images have red green and blue. This might seem like it would take longer, but it’s actually much easier because I can actually hear what I'm doing when I add notes. By the way I think release velocity makes articulation more accessible for those with no sense timing who can't record there keyboard. or for those who have delayed response due to disability. take me for example I have a slight motor lag due to parts of my Autism so I can't keep time in order to record with an MPE Controller. that's why I use Bitwig because it has release velocity (although I admit reaper implements it better)

[stippenstoh]

Here's a quick video we made about the CPU Burner, because we forgot to mention it in the preliminary user guide:

Whoever made that video intro, I love it.

[david.beholder]

Here's a quick video we made about the CPU Burner, because we forgot to mention it in the preliminary user guide:

Well it's time to add local memes.

[Stan Navi]

Here's a quick video we made about the CPU Burner, because we forgot to mention it in the preliminary user guide:

Well it's time to add local memes.

Urs can use this meme instead of answering two most asked questions:
1. Is Zebra 2 presets compatible with Zebra 3?
2. Will be there crossgrade sale from Zebra Legacy to Zebra 3?

[atmelcool]

OK try this preset:
Shmately Bass.zip
Go into Osc1 editor, select the blue curve, then add a point somewhere in the middle and start moving it around. If you can't hear what it's doing that may be a bug.

Yes, I tried that, and the blue curve works as a filter, but the green and red ones don't work at all. I still don't understand where that blue curve is attached to.

[david.beholder]

Urs can use this meme instead of answering two most asked questions:
1. Is Zebra 2 presets compatible with Zebra 3?
2. Will be there crossgrade sale from Zebra Legacy to Zebra 3?

Nice. Also it makes sense to add some text there I just don't know which one.

[Urs]

OK try this preset:
Shmately Bass.zip
Go into Osc1 editor, select the blue curve, then add a point somewhere in the middle and start moving it around. If you can't hear what it's doing that may be a bug.

Yes, I tried that, and the blue curve works as a filter, but the green and red ones don't work at all. I still don't understand where that blue curve is attached to.

You get the green and red ones (aka "Guide 2" and "Guide 3") by setting the knob labelled "Morph" in the middle or fully right position. The in-between values crossfade the curves accordingly. This can be modulated, so you can seamlessly crossfade between different filter curves in this example.

Usually, wherever you can use a Guide, you can also use the main Curve itself. Guides are easier on CPU, but they only crossfade. The Curve would still morph properly, as set up in the timeline.

[soundman007]

Has the download been updated to 6.0.2 in spite of the fact that it still says 6.0?

What do you mean by 6.0.2?

We have not updated the beta, yet. But we are making great progress with some of the more annoying bugs, which we hope to publish in early January.

Oops, so sorry, jumping from one thread (Zebra-Absynth) to another, this was meant for the Absynth thread.

[Urs]

[robisme]

Wonderfull.

Just a request : could you add a button to select "all favorite numbers" in the preset view (it's tedious to select them one by one when you want all and only your favorites to display).

(btw, this would be a request for all of your devices, not only Zebra, but I figured a beta is the right place to ask).

[atmelcool]

You get the green and red ones (aka "Guide 2" and "Guide 3") by setting the knob labelled "Morph" in the middle or fully right position. The in-between values crossfade the curves accordingly. This can be modulated, so you can seamlessly crossfade between different filter curves in this example.

Usually, wherever you can use a Guide, you can also use the main Curve itself. Guides are easier on CPU, but they only crossfade. The Curve would still morph properly, as set up in the timeline.

Did I understand correctly that access to these three curves (blue, green, red) is only possible from OSC FX?