Zebra 3.0 - out now

[exmatproton]

Can someone explaoin this 'baking' please?

from the manual;

Baking
Knob values can be 'baked' into all modulation targets: If you are particularly happy with the sound
at a certain position of Control A, for instance, and would like that to become your new zero point,
right-click on the knob and select 'Bake Modulation'. You can then remove the assignment(s)...

Note: This feature is work in progress. You will need to left-click once on the knob before trying to
bake its position—baking is disabled if the most recently received value was via MIDI CC.
These sources appear at the far right of the Modulation Assigner Bar as ●A, ●B, ●C and ●D.
See the Audio & MIDI preferences and Per Instance Control.

[Grizzellda]

Baking is a term used in 3-Dimensional software modelling IIRC!

Prolly to maximize the computing power available to calculate those images. For those of you that don't know, it is the lighting and shadows, the "3D sense of depth" is what requires CPU power.

[cryophonik]

I'm fresh off the plane from an amazing trip to Switzerland and a little late to the Z3 party, but I installed it this morning, have just started checking it out, and may have found a very minor bug that I'm hoping someone can confirm (or may have already been discovered). In the MSEGs, the Loop Mode window toggles between Normal and Infinite when I left-click, but right-clicking shows 0 and 1 (plus the Lock option), rather than the actual values like the other MSEG dropdown menus do. I assume this is not the intended behavior, correct? I'm on a Mac with the latest AU build downloaded today FWIW.

[Touch The Universe]

Anyway to turn off the incremental saving that adds a bigger number after the patch automatically, from 2 to 3 to 4, etc? sometimes, usually, i just want to update the patch. Am i missing somethin?

[pdxindy]

Anyway to turn off the incremental saving that adds a bigger number after the patch automatically, from 2 to 3 to 4, etc? sometimes, usually, i just want to update the patch. Am i missing somethin?

It's an option in preferences

[Touch The Universe]

thanks

[tasmaniandevil]

In the MSEGs, the Loop Mode window toggles between Normal and Infinite when I left-click, but right-clicking shows 0 and 1 (plus the Lock option)

Well spotted. Thanks.

[Krakatau]

bump

[frag]

why did you abandon multithreading from Diva & Repro?

Because more and more computers today and tomorrow have asymmetric CPU cores, and we need to figure out how to compute our threads only on performance cores. Otherwise the performance gets a lot worse, like Diva and Repro on Apple silicon (but also e.g. on my Thinkpad).

That is an excellent, straightforward explanation.
All I was getting before are insults, even from Korg representatives!

With symmetrical cores, all we have to do is disable core parking. I do not like P+E configurations at all. I hope some solution will be found, because I feel new CPUs are underutilized when it comes to real-time audio processing. And then old CPUs are underutilized as well, if you run new plugins.

[SamDi]

But, e.g. I wanna make a sound, which when releasing the key has a certain pitch-down behaviour in the release phase. Today I couldn't do it with the MSEG, I would need to mess around with the ENV and hope, that I get the pitch-down-curve to near as I want to have it, instead of beeing able to draw it directly as I want.

Hold on... how does that curve which you want actually end? Does it eventually end at 0? Because then you can do this with MSEG in Z3 just fine, I think, since you CAN select MSEGs as amp modulation sources for each column of the grid.

Draw the pitch down curve you want in the release section of an MSEG. Set the MSEG Release Mode to Immediate. Done.

Yes, you are both right. That works - at least for my given example.

Why should it be a MF?

The point is about the recursiveness of triggering and also being triggered. MSEG 1 triggers MSEG 2, MSEG 2 triggers MSEG 3, MSEG 3 triggers MSEG 1. At the same time, MSEG 2 is used as VCA source and thus responsible for the life cycle of the voice.

In any case, MSEGs are a great source for exactly timed triggers. Exactly timed triggers are commonly rhythmic, happening across quarters/eighths etc. or across bars, and then regularly. Thus, if MSEGs are triggered in such commonly short intervals (rhythmic) or bar-length intervals (regular distance), why trigger an MSEG for that? The question is, what needs to happen "on trigger" that warrants wasting an MSEG for some short event, and why trigger it regularly if it could just loop anyway.

If it really is just about the free running part, there's the single trigger option.

We'll happily discuss an "endless looping global LFO mode" for the MSEGs, I just don't think it is really that useful.

You might be right, that it might be not so uncomplicated.On the other side, you might overthink it and just could prevent some of the MF cases by prohibiting circular calls or exclude a MSEG from retriggering, when it's used as AMP-ENV.

Anyway I've got the impression, you consider MSEGs primarily as more sophisticated ENVs and they seem to be implemented in Z3 like that. You consider MSEGs not so much as the more sophisticated brothers to LFOs as it seems and this leads to that they can not be used in Z3 as an alternative to them. At least you would need similar to LFO the time base and trigger options. This would solve the endless looping topic.

What's more imortant is to really make the MSEGs able to run long over eg. 1-8 bars and then not to be reset with every note to have this long evolving modulations not only for one played note.

Put the MSEG in Single mode, and then they don't reset with each note. After the first poster brought this up yesterday, I spent some time exploring this and I had no trouble doing just what you are describing.

Are you sure? I can not confirm this. When set to Single mode the MSEG retriggers also with each note on my side.

[EvilDragon]

Yeah, Single mode doesn't work if you have long release on amp envelope and you play staccato. Then MSEG retriggers on every played note. If you play connected, it works as you'd expect. Definitely a bit iffy behavior here, I have to agree.

There would have to be a mode which doesn't retrigger the MSEG as long as there are any active voices.

[pdxindy]

Are you sure? I can not confirm this. When set to Single mode the MSEG retriggers also with each note on my side.

If all notes stop, then it will retrigger. However if there is always a note held, then new notes do not retrigger.

[EvilDragon]

Yeah, it should also work if you don't hold any notes but voices are active IMO. That's how it would work on a single trigger monosynth.

[SamDi]

If all notes stop, then it will retrigger. However if there is always a note held, then new notes do not retrigger.

That's right, but this isn't exactly the same as a free running LFO or beeing able to be synchronized to DAW's tempo. Still think it's missing for MSEG. Hope they will deliver something for that during next releases.

[Urs]

Yeah, it should also work if you don't hold any notes but voices are active IMO. That's how it would work on a single trigger monosynth.

But it's a single trigger polysynth. You can't just wait with retriggering until the initial MSEG has played out fully. It would seem buggy.

(The solution is to not re trigger the MSEG on new notes while another note is still held. But as soon as no note is held, a new note must receive a single trigger for the MSEG... it doesn't work any other way)