Zebra 3.0 released

[Eluwei]

...

[SteveElbows]

I am on a hunt for a good midi control solution for Z3. Is there anyone using Roto Control with it? Do the controls of it detect and differentiate the devices inside of Zebra3 (i.e. have 8 controls for FMO2, then add Filter1 and Roto Control updates to the new "device")? Would this behaviour also apply to say Oxi E16? Thank you very much!

Generally speaking, Roto-Control has two different ways of operating with plugins inside DAWs:

1) Original method involves a lot of manual learning to connect each knob etc to a specific plugin parameter. These are then saved automatically inside the Roto-Control, although there are limits as to how many of these configurations can be saved within the device. Personally I prefer to use these with simpler plugins, but you do get the most configurability with this mode. But only one of these setups can be configured per plugin, and there are limits as to how many pages (and thus knobs) these configurations can include! 8 pages if I remember correctly, so 8 x 8 knobs and 8 x 8 buttons per plugin. The learning process consists of pressing a button on Roto-Control, then touching a knob or button, then moving the desired control in the plugin/DAW. For setting additional config options per knob/button their own app can be open on the computer at the same time if desired, although it doesnt need to be running to make Roto-Control work, just when doing certain learning config tweaks.

2) Additional alternative method they added shifts the 'learning' burden totally away from the Roto-Control itself, and onto macro / remote /smart controls within the DAW. Roto-Control automatically reflects whatever is setup in this feature of the DAW for the currently selected plugin instance, and doesnt need to save any config inside itself so there is no limit as to how many of these you can use - its up to you to have these macros/remote pages/smart controls edited, saved etc inside the DAW in the normal way. But you do get less configurability of each parameter on Roto-Control, and other limitations depend on your DAW. eg Ableton only supports a couple of pages of macro knobs per macro device instance I think, but Bitwig supports loads of pages so is much better in this mode. Logic Pro smart controls seem to be quite limited, but I am not very familiar with that Logic feature. In all the DAWs I tried, it was not obvious that the 8 parameter buttons on the Roto-Control can even be used at all in this mode, just the knobs.

2 is a better fit for Zebra I think for many uses, but you will still have to do some quick manual mapping of macro/remote knobs inside DAW to the parameters on Zebra modules that you want to control. But once you get used to the workflow its actually pretty rapid, and I dont think its really slower than how it would be if all the gazillions of parameters were already there, because you would just end up spending time trying to find the ones you wanted from huge lists/way too many pages on the Roto-Control. So long as your DAW doesnt suck when it comes to macro/remote control config per plugin instance, this stuff fits fairly well with Zebra 3s modular nature, unlike original learning method 1.

There is an option 3) to not use Roto-Control in DAW mode at all, and have it behave like a normal MIDI controller. But you'll still be reliant on some other pieces of the puzzle to be used to map stuff intelligently, so unless you have special workflow and solutions that work for you in the broader and more generic MIDI controller world, I doubt this option will be better or save time.

Although Roto-Control does do a few things in its own wacky way, ultimately most of the issues are still things that would exist in some form if you choose a different controller instead. And its necessary to understand which controllers are well supported by your DAW of choice, and other details about how your DAW handles plugins with lots of parameters that can change, and how these things all fit together.

[HAJIME KOURIKI]

The current scope already allows for a very comprehensive understanding and observation of what’s happening. At the same time, I agree that flashy visual feedback isn't strictly necessary. The idea of a scope-type overlay is wonderful, but to reiterate, my main desire is simply a way to know the current values—specifically the modulation values.
For instance, when using Zebra, I can't always tell exactly how far the value has reached or dropped within the -1 to +1 range. While it’s not impossible to guess, it leaves me feeling a bit uncertain. Having numerical values and a history of those movements would provide much-needed reassurance and immediate clarity during the sound design process.

[pdxindy]

I understand u-he's reasoning for not having extensive visual feedback but since this is a totally new kind of synthesis I think anything to make it simpler to understand will go a long way towards helping users use it. I noticed that there is already a lot more visual feedback in the final release than the beta's already and i think it is very helpful

The Scope is useful for understanding complex modulations. Plus it's already there, so no need to hope for a future feature.

[aMUSEd]

I am on a hunt for a good midi control solution for Z3. Is there anyone using Roto Control with it? Do the controls of it detect and differentiate the devices inside of Zebra3 (i.e. have 8 controls for FMO2, then add Filter1 and Roto Control updates to the new "device")? Would this behaviour also apply to say Oxi E16? Thank you very much!

Generally speaking, Roto-Control has two different ways of operating with plugins inside DAWs:

1) Original method involves a lot of manual learning to connect each knob etc to a specific plugin parameter. These are then saved automatically inside the Roto-Control, although there are limits as to how many of these configurations can be saved within the device. Personally I prefer to use these with simpler plugins, but you do get the most configurability with this mode. But only one of these setups can be configured per plugin, and there are limits as to how many pages (and thus knobs) these configurations can include! 8 pages if I remember correctly, so 8 x 8 knobs and 8 x 8 buttons per plugin. The learning process consists of pressing a button on Roto-Control, then touching a knob or button, then moving the desired control in the plugin/DAW. For setting additional config options per knob/button their own app can be open on the computer at the same time if desired, although it doesnt need to be running to make Roto-Control work, just when doing certain learning config tweaks.

2) Additional alternative method they added shifts the 'learning' burden totally away from the Roto-Control itself, and onto macro / remote /smart controls within the DAW. Roto-Control automatically reflects whatever is setup in this feature of the DAW for the currently selected plugin instance, and doesnt need to save any config inside itself so there is no limit as to how many of these you can use - its up to you to have these macros/remote pages/smart controls edited, saved etc inside the DAW in the normal way. But you do get less configurability of each parameter on Roto-Control, and other limitations depend on your DAW. eg Ableton only supports a couple of pages of macro knobs per macro device instance I think, but Bitwig supports loads of pages so is much better in this mode. Logic Pro smart controls seem to be quite limited, but I am not very familiar with that Logic feature. In all the DAWs I tried, it was not obvious that the 8 parameter buttons on the Roto-Control can even be used at all in this mode, just the knobs.

2 is a better fit for Zebra I think for many uses, but you will still have to do some quick manual mapping of macro/remote knobs inside DAW to the parameters on Zebra modules that you want to control. But once you get used to the workflow its actually pretty rapid, and I dont think its really slower than how it would be if all the gazillions of parameters were already there, because you would just end up spending time trying to find the ones you wanted from huge lists/way too many pages on the Roto-Control. So long as your DAW doesnt suck when it comes to macro/remote control config per plugin instance, this stuff fits fairly well with Zebra 3s modular nature, unlike original learning method 1.

There is an option 3) to not use Roto-Control in DAW mode at all, and have it behave like a normal MIDI controller. But you'll still be reliant on some other pieces of the puzzle to be used to map stuff intelligently, so unless you have special workflow and solutions that work for you in the broader and more generic MIDI controller world, I doubt this option will be better or save time.

Although Roto-Control does do a few things in its own wacky way, ultimately most of the issues are still things that would exist in some form if you choose a different controller instead. And its necessary to understand which controllers are well supported by your DAW of choice, and other details about how your DAW handles plugins with lots of parameters that can change, and how these things all fit together.

Bitwig is by far the best DAW for setting up option 2 (although I use it with NI Kontrol MkIII keyboard the principle is the same). An alternative option 1 type solution is the Kontrol MkIII (NKS) - in practice again you have to create the mapping yourself or use/adapt a mapping created by a fellow user (for Zebra 3 I have already created template remote controls for Bitwig and NKS). The challenge with Zebra is it potentially has hundreds of mappable params, the trick is to put the ones that are adaptive like the CTRL's at the front, then things that are most useful when performing/playing live and when you don't want to menu dive too much (for me this means things like the OSC and MSEG morphers, filters and OSC FX). Leave the rest open so people can create additional controls if they have a patch they want more control over.

[suice7]

I am on a hunt for a good midi control solution for Z3. Is there anyone using Roto Control with it? Do the controls of it detect and differentiate the devices inside of Zebra3 (i.e. have 8 controls for FMO2, then add Filter1 and Roto Control updates to the new "device")? Would this behaviour also apply to say Oxi E16? Thank you very much!

Generally speaking, Roto-Control has two different ways of operating with plugins inside DAWs...

Thanks a lot for your answer and thanks for explaining.
I do not know the correct term, but I would like to know if a Z3 module like for example FMO could be detected as a seperate device. When you switch devices in Bitwig or Ableton, Roto Control updates to the new device as well. This behaviour would be great. I know there are a lot of devices inside Zebra3, but you would have to map only 4 different oscillators (x4) once and you are done.

On the other hand, I like to make use of the option to use the mouse scroll for pots on the device you are hovering over. I might just buy Intech Studio VSN1, which can take over mouse scroll action on the big wheel. (https://www.thomann.de/de/intech_studio ... gK_I_D_BwE)
Cheers!

[Eluwei]

...

[gobe99]

Z3 is a fantastic new synthesizer! This wonderful instrument will give me joy for a long time to come. Many thanks to the entire u-he team!
I'm currently building a castle out of 30,000 building (lego) blocks, so I can imagine how you all felt during the development of the Z3.

[Sollyd]

I really like the new GUI

[ban jhankri]

Very nice work with the new Zebra. The new GUI is much better than the previous one.

[lovelights]

I’ve built Ableton Instrument Racks for all the factory presets in Zebra 3, designed especially for Ableton Push so you can browse sounds and tweak parameters without looking at your computer screen. They also work with many other MIDI controllers, as long as you’re using the latest version of Ableton Live with VST3 support.
Each rack maps MIDI parameters across all 16 banks, with CTRL A–D and volume assigned to macros for easy control. It’s completely free—all you need is Zebra 3 and Ableton live. Get them in my FB group: https://www.facebook.com/groups/AbletonPushVstRacks

[lovelights]

Here are the bank mappings for Push/ Zebra 3 ( about the post above )
MACRO Ctrl ABCD and Volume
Bank 1 Filter 1 + 2
Bank 2 Envelope 1 + 2
Bank 3 LFO 1
Bank 4 LFO 2
Bank 5 OSC 1
Bank 6 OSC 2
Bank 7 Noise 1
Bank 8 Comb 1
Bank 9 FMO 1
Bank 10 Modal 1
Bank 11 Mix 1
Bank 12 Exciter 1
Bank 13 EQ 1
Bank 14 Distortion 1, Folder 1
Bank 15 Effects Delay, Reverb Wet and Output gain

[Charlie Firpo]

I discovered something in Cubase 15 with the midi CC:
1) Init patch in Zebra 3.
2) Select Filter1 and put it under Osc1.
3) Assign midicc 3 to cutoff freq.
4) In Cubase midi editor, create a note & create a midicc lane for cc3.
5) Draw a straight line that goes from zero to the top.

Result: everytime i hit play, the cutoff doesnt start from zero. It seems to depend on the highest end point on the line. If i move the note & cc line slightly forward on the grid the cc seem to register correct. I tried this also in Renoise/Bitwig with the same result. I've checked/unchecked all the "reset on stop" options in Cubase. And also tried the various midi ctrl slew options in zebra 3.

[Urs]

This is automation. We smooth automation so that parameters don't zipper.

We also smooth MIDI Learned parameters so they don't zipper.

Instead of MIDI Learning the parameter directly, set Control A to MIDI CC#3, then modulate Cutoff with Control A.

[Charlie Firpo]

This is automation. We smooth automation so that parameters don't zipper.

We also smooth MIDI Learned parameters so they don't zipper.

Instead of MIDI Learning the parameter directly, set Control A to MIDI CC#3, then modulate Cutoff with Control A.

Indeed, that worked! Thanks Urs