Diva: Struggling to get Macros to Work (Big Sur, M1, Ableton 10)

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
I've been trying to get U-HE Zebra to work with macros/mapping on Ableton 10. Either I'm making a mistake, or there is a bug. I hope it's the former, but it is likely the latter.

This is a big part of my workflow with Push. Using instrument racks you can create mappings for the 8 knobs which allow you to make basic adjustments without touching the laptop. Amazing when it works!

Code: Select all (#)

Open Ableton 10
Add Diva to an empty MIDI Track
Expand plugin panel, enable 'configure' and click the knob in the VST I want to map.
See the parameter added
Disable configure and adjust the new slider.
Optional: Drag into an instrument rack and assign to a macro.
Expected: I should be able to adjust the parameter and control the VST through the DAW, and record automation.
Result: The synth breaks and I have to reload the template to get any sound out.

I've tried with Valhala Supermassive (VST Effect) which works flawlessly and Sugar Bytes Egoist (VST Instrument) and both work as expected.

I admit this might be as I am an early adapter of the M1 macbook, but I only got Diva this week. If you have any beta builds I can give them a shot and let you know if it fixes them.

Thanks and have a great Christmas. :-)
Macbook Air 2020 M1 - 8GB
Big Sur (came with the Mac)
Ableton 10 Suite

Post

You write about VST, but are you maybe actually using the AU version of Diva?

We have listed the currently known compatibility issues in this post:
viewtopic.php?p=7853092#p7853092

There are a number of issue with the AU versions, the macro automation in Live being one of them.
We are still working on compatibility updates for macOS Big Sur, and for the new M1 chips.
That QA guy from planet u-he.

Post

That is exactly what the issue was!

That's given me a workaround for now. Generally which is recommended for M1 compatibility and speed? VST or AU?

Also, if anyone else has similar troubles, you can bypass it the long way round with Komplete Kontrol.

Thanks Guys

Post

Yeah, I've been curious about that as well. I haven't (in my very casual googling of the issue) found anything that indicates that AU has a performance gain over VST3; most of what I've been able to find boils down to "AU has some midi constraints; use VST for cross-platform compatibility". I'm not sure that Apple Silicon has an impact here or not. I've got an M1 Mac Mini on the way and will be experimenting, also.

Post Reply

Return to “u-he”