Zebra 3.0 - out now

[pdxindy]

really..whatever..

Best to put them on ignore since they quickly turn to personal attacks, taking any fun out of discussing features and improvements.

[pdxindy]

Macro's can be very handy. And them being saved is what i use often with other synths..you know, making a patch, change the macro's to hit a sweetspot and save that for later use. Instead of saving that state in a project (host level) every time is just a waste of space and 100% unnecessary

Control A-D are still a work in progress. Here is from the Z3 page:
Ctrl A-D macro feature is experimental, the parameter values are currently not saved.

I would also like some way to recall (in Z3) the state of tweaked A-D knobs. Maybe a way to save and recall snapshots which would give preset variations within a single preset.

[Urs]

You can always "bake" them.

[RobGee]

I haven’t had much of a chance to sit down with Z3 yet, glad I’m now aware of these A-D controls not saving. That would’ve pissed me off had I assigned them and recalled a project only for everything to sound totally different. Seems like a strange design choice, I won’t be using them…

[Held]

But they look like macros and are in the same location where other synths put their macros. So I hope you can understand why I am confused (and probably other people too).

I guess we should not have labelled them or kept the original labels. We also should have called them "MIDI A/B/C/D" instead of "Control A/B/C/D". Maybe we'll rethink that in the next version, to avoid any confusion as to what they are.

Even without the labels, I would have expected them to behave like macros. Maybe those are more familiar to people who are used to orchestral libraries, where you have a lot of parameters that are controlled via CC. But those are usually not visible in the UI.

I'd either hide those controls or replace them with normal macros that are assigned to CC via MIDI learn.

But if you hide them, people are most certainly going to ask for macros. Those are a basic feature in modern synths.

Pigments has a timbre parameter that is a normal macro, but when you enable MPE, it gets assigned to CC74 and can't be changed from the UI anymore. Maybe you can do something similar?

[Urs]

Hmmm, so if we did it like Pigments, if I understand correctly, we could add a switch for each of A, B, C & D as to whether it is a MIDI Control Change or a Macro. If it's in the Macro setting, it'll recall with preset/project. If it's in the MIDI setting, it'll reset.

[Held]

Hmmm, so if we did it like Pigments, if I understand correctly, we could add a switch for each of A, B, C & D as to whether it is a MIDI Control Change or a Macro. If it's in the Macro setting, it'll recall with preset/project. If it's in the MIDI setting, it'll reset.

In Pigments, it's tied to the MPE switch, but that's because it's hardwired to CC74.

Maybe a global setting for all controls. So you either have macros or MIDI Control Change.

[Urs]

I have set up a thread where we can discuss all of this in one place:

viewtopic.php?t=629796

[exmatproton]

really..whatever..

Best to put them on ignore since they quickly turn to personal attacks, taking any fun out of discussing features and improvements.

Yeah..he is on that list tiresome

[Dr.Gunjah]

Hmmm, so if we did it like Pigments, if I understand correctly, we could add a switch for each of A, B, C & D as to whether it is a MIDI Control Change or a Macro. If it's in the Macro setting, it'll recall with preset/project. If it's in the MIDI setting, it'll reset.

Makes sense to me. I definitely expected them to be recalled.

I've also never quite understood why the modwheel is not exposed as an automatable parameter in u-he synths. I mean historically it's midi, but pretty much any other synth I've ever used exposes it anyway and it works much smoother there with "drawn" automation.
edit: Zebra3 actually exposes it!

[IvyBirds]

[pdxindy]

You can always "bake" them.

Thanks... didn't realize that was a feature!

[bmanic]

You can always "bake" them.

Thanks... didn't realize that was a feature!

This is such an amazing feature that I've been trying to get the FabFilter dudes to implement since forever! Perhaps this is finally the leverage I can use to say "See??? THIS is how it's done!". I want Modwheel and all complex "static" routings to be able to be baked and connections deleted so that they can be easily reused.

Thank you for implementing this Urs! It's amazing to see somebody finally doing this!

[cb8rwh]

Can someone explaoin this 'baking' please?

[IvyBirds]

Can someone explaoin this 'baking' please?

Basically you take whatever you are doing with the synth and turn it into a Wavetable

That Wavetable will capture everything that the current Modulations and controls are doing

Then you can play it back and free up all those modulation slots for other things