u-he - The Performance Update (M1 support & more)

[Max Antsiferov]

Can't seem to be able to download anything? Safari just loads 459b "zip" file, managed to download Diva update but everything else just won't download properly(or downloads like at 5kb/s speed)

[tasmaniandevil]

Yep, our content delivery network seems to be overwhelmed atm: viewtopic.php?f=31&t=569128

[Max Antsiferov]

Yep, our content delivery network seems to be overwhelmed atm: viewtopic.php?f=31&t=569128

Oh okay,cheers!

[Erisian]

Slightly off topic but I didn't want to create a whole new thread just for one question. Triple Cheese seems to produce some remarkably natural sounding plucks - better than some of the physical modelling synths I have tried. Are the comb oscillators partly responsible for this or is it just very good preset design that could be done in any synth?

[benedettodue]

....and new iPAD Pro CPU is M1 🥴🥴

[Double Tap]

Great work, excellent news.

[THE INTRANCER]

Modules ? At what level are you talking about...

If an LFO isn't used in a preset, it will be put into bypass automatically. If you drag that LFO onto the scope, it'll show a flat line and the Label will show, e.g. "LFO 1 (inactive)". The same goes for oscillators, sub oscillators, filters, envelopes, anything.

This happens completely automatically, there's no interaction required on the user's side.

Thanks for the clarification and time you spent in doing this... For me and it's perhaps because of the way in which I've used Hive in my music, I've always found it to be pretty CPU efficient when compared to other synths. If I'm working on a big 100+ track I optimise by bouncing down in any case. Hive I usually use for bass, pads and arps.

--

My main issue with Hive is that the script file isn't documented between updates to indicate what has been changed, added to or illustrated to show how content of the script is linked ( vie notes or numbered sections for instance ). That would help hugely for anyone wanting to change the skin design beyond the default skins provided, neither of which I really like. I mentioned this in a previous post in regard to the new filter options, but you couldn't help. With the updates being vastly shorter between versions of Hive, those who have or want to update skins significantly beyond colours are left with a frustrating task to do so or perhaps even learn from the outset. If it's practical, then I'm, sure many would appreciate it.

Here's some GUI designs I created a few months back and can easily switch to by simply changing the background element. Almost everything has been moved and changed from the original design. Hive 2 Designs

[kmonkey]

I really like ongoing development. A little bit offtopic: I in my mind secretly hope that by the end of this year there will be another deal between U-he and NI

I wanna buy all their plugins for my new build. That NI deal was really something special (to me anyway).

[Urs]

Thanks for the clarification and time you spent in doing this... For me and it's perhaps because of the way in which I've used Hive in my music, I've always found it to be pretty CPU efficient when compared to other synths.

It always depended on the way one compared Hive to other synths. Real world patches weren't always very good, but if one compared one oscillator here with one oscillator there, Hive would always be 4 oscillators, two filters, everything. So in these comparisons Hive looked bad, and people who did these comparisons would always sow doubts. We're confident that these kinds of tests would offer some surprises now.

My main issue with Hive is that the script file isn't documented between updates to indicate what has been changed...

I totally get your frustration. But imagine you were a graphics designer and you had to document every mouse move you do in Photoshop. That's just not anything that inspires creativity. And then you'd have to got back and branch off wherever you'd build variants. I doubt we'd be any more equipped to create a change log for the script file than anyone else, and I doubt there's a way to document changes in a way that's utterly helpful.

With few exceptions it should however always be possible to make screenshots of the UI and its tabs before and after and blend them with a difference layer mode. This will give you all visual differences.

If you need to find sections that are new or that changed in the script, you have two options:

- use a text compare tool that developers use ("Diff"), but these might produce overwhelming results. They would be our choice to do this though.

- look at the names of the parameters attached to controls in the changed areas, and search for them. The names are written in small print on the left side of the edit display when it shows the current value.

Anyhow, I'll keep that in mind and maybe I can come up with something in the future. I can't promise anything though.

[GaryG]

Triple Cheese seems to produce some remarkably natural sounding plucks - better than some of the physical modelling synths I have tried. Are the comb oscillators partly responsible for this or is it just very good preset design that could be done in any synth?

You could argue triple cheese is a physical modelling synth due to its comb filter oscillators, I think they're the secret to it's sound, especially the overblown sounds etc. Not a regular va obviously.

[Enkerli]

Congrats on that update! Quite an achievement. Hope adding native support for Apple Silicon wasn’t too difficult. (Few plugin devs have done it so it might prove to be a challenge, depending on their development practice.)

Didn’t notice Zebralette in posts about this massive update. So it was a nice surprise, upon downloading a trial of Zebra2, to find out that it’s indeed fully native.

Partly because Zebralette wasn’t mentioned, I undertook all the steps to get ZebraCM. It’s probably the most convoluted “plugin acquisition process” I’ve ever encountered!

Not your fault at all, of course. And one might argue that having dozens of (mostly ancient) plugins is beneficial. Then again, only a few of them work on my #MBAM1 (mostly because of Big Sur, I guess).

So, at any rate, I got really excited about the new ZebraCM after that announcement was reported in several spots…

ZebraCM: (available from Computer Music soon)

* Fresh, modern GUI
* Factory preset library sorted and polished

Ha! That explains why the 2.38GB from FileSilo for the “CM Plugin Suite Mac Instruments” only included a 2019 version of ZebraCM.

So, it’s really good to know that I should eventually get the native version. That’s so generous of you!

If all goes according to plan, it might succeed as a gateway plugin to the rest of the u-he lineup, for me. (I’m mostly interested in the synths which support MPE: Bazille, Ace, Diva, Hive & Repro-5 according to Roger Linn.)

[pdxindy]

If all goes according to plan, it might succeed as a gateway plugin to the rest of the u-he lineup, for me. (I’m mostly interested in the synths which support MPE: Bazille, Ace, Diva, Hive & Repro-5 according to Roger Linn.)

Every one of them is fantastic!

Bitwig plus the u-he synths is MPE heaven!

[THE INTRANCER]

Thanks for the clarification and time you spent in doing this... For me and it's perhaps because of the way in which I've used Hive in my music, I've always found it to be pretty CPU efficient when compared to other synths.

It always depended on the way one compared Hive to other synths. Real world patches weren't always very good, but if one compared one oscillator here with one oscillator there, Hive would always be 4 oscillators, two filters, everything. So in these comparisons Hive looked bad, and people who did these comparisons would always sow doubts. We're confident that these kinds of tests would offer some surprises now.

My main issue with Hive is that the script file isn't documented between updates to indicate what has been changed...

I totally get your frustration. But imagine you were a graphics designer and you had to document every mouse move you do in Photoshop. That's just not anything that inspires creativity. And then you'd have to got back and branch off wherever you'd build variants. I doubt we'd be any more equipped to create a change log for the script file than anyone else, and I doubt there's a way to document changes in a way that's utterly helpful.

With few exceptions it should however always be possible to make screenshots of the UI and its tabs before and after and blend them with a difference layer mode. This will give you all visual differences.

If you need to find sections that are new or that changed in the script, you have two options:

- use a text compare tool that developers use ("Diff"), but these might produce overwhelming results. They would be our choice to do this though.

- look at the names of the parameters attached to controls in the changed areas, and search for them. The names are written in small print on the left side of the edit display when it shows the current value.

Anyhow, I'll keep that in mind and maybe I can come up with something in the future. I can't promise anything though.

Thanks, Urs...I've actually been updating Hive's GUI since 2015 so I've tried many things to make it easier. Trying to make comparison differences with online tools I've tried is just futile, it's easier to do that in a text editor manually. I do have some reference of the changes I've made in which I can re-adapt things like knobs labels and buttons ect... but it's a lot of extra work and jiggery-pokery to bring things together when new functionality is added. I've managed to bring the newest version of Hive together with my design so I can now utilise the extra filter feature which is great but at the moment it is more like a hybrid with a lot of things not sitting where they are meant to, matching the abbreviated text besides a few graphical issues. It's still like doing everything again each time on each new script for a revision.

My previous attempt in trying to get the new filters to display ended up with just the names and Bypass showing only and no functionality, and that was when I did find the control section for this. I can only figure that the property section at the foot of the page had something to do with this in not displaying things as it should. I had trouble trying to adapt the new into the old script which is preferential because I don't need to move everything by hand again and implement additional controls as I have created such as right side ( dual ) XY Pad for instance.

Having some structural reference, dividing up the script and naming each section is what I have to do each time on a new script. Having just one script to update rather than needing a complete transformation of a new script would save a ton of time for users into GUI design. Dune 3 for example is far less code heavy than Hive but is more informative about what is what. I can figure out how things are referenced with Hive but it is much more work than it could be otherwise to work out. Property to Control references being the more difficult aspect.

Here's a screenshot of where I am now with updating Hive's skin which as I mentioned still has some work to do to have everything displayed properly and in the right place. The colours of the main display do look rather fetching on the black screen I think. I'm half way there I think...
......
Scott

[fese]

I think I found a minor bug in Presswerk 1.1.5 that if I remember correctly wasn't present in the previous version.
If I toggle bypass, there is a rather long (maybe 0.5s?) audio dropout. No difference whether I use the internal bypass or that of the hosts. This does not happen in HQ mode, bypass is completely smooth.
This is on Cubase 10.5/Win with VST3.
Is this a known issue or shall I file a support request? While it is not a major issue, it is rather annoying when trying to compare with the unprocessed audio.

[tasmaniandevil]

It's a necessary side effect of our improved latency reporting.
In non-HQ mode, there is an additional sample of latency that needs to be compensated for when you activate or deactivate bypass. This now gets reported to the host instantly. Previously this might have only been reported when the host playback was started or stopped. This could have led to phasing issues during playback.
The moment of silence is the host adjusting the plugin delay compensation.