CLAP public preview revision 13510 (ACE, Bazille, Diva, Hive)

[tasmaniandevil]

Happens on various plugin formats (tried Clap and VST2) and using the latest Reaper but note: trying in Studio One results in smooth movements. Not sure if this is a U-he thing or a Reaper thing.

Hmm, the update rate is automatically set to the display's refresh rate in the latest beta, so it should always be smooth.

One idea, what's your buffer size in Reaper, is it really high?
If so, can you try a lower buffer size?

Another idea, I've once noticed some GUI issue on my Intel MBP (could not reproduce on my M1 MBP though).
There was a problem with period stuttering, i.e. once every second the plugin UI update stopped for just a short moment. After lots and lots of testing I found out it happens only if the plugin's UI is covering the Reaper arrangement section completely. If moved just a tiny bit to keep some of Reaper's arangement visible, the issue stopped. Since we could not find a reason for this, we suspect it might be something to do with the graphics rendering of Reaper.
But not sure what kind of issue you experience exactly, so this might be unrelated.

[Funkybot's Evil Twin]

Another idea, I've once noticed some GUI issue on my Intel MBP (could not reproduce on my M1 MBP though).
There was a problem with period stuttering, i.e. once every second the plugin UI update stopped for just a short moment. After lots and lots of testing I found out it happens only if the plugin's UI is covering the Reaper arrangement section completely. If moved just a tiny bit to keep some of Reaper's arangement visible, the issue stopped. Since we could not find a reason for this, we suspect it might be something to do with the graphics rendering of Reaper.
But not sure what kind of issue you experience exactly, so this might be unrelated.

This seems to be the issue. If I have a certain amount of the arrange view visible, the stuttering goes away. If the arrangement view is entirely covered, or almost entirely covered (e.g. maybe 1 measure is visible on the far right), then the stuttering happens. Move the U-he GUI far enough to the left to keep more of the arrangement view visible, and all of a sudden the issue goes away. Interesting. Would never have found that. Thanks!

[Cepheus]

Reaper 6.71: add support for CLAP plugins. It's official now

[Scotty]

Congratulations. Bitwig and Reaper are innovators. Let's hope for more DAWs to come on line. We need the options. It isn't ideal to have Steinberg holding all the marbles.

[glokraw]

Marbles well worn, and oblong as they may be...

[glokraw]

I installed the linux Hive 2 CLAP public preview alongside my registered vsti and vst3i versions, and loaded them all together in a linux Reaper project, each seems to be working fine, without conflicts, as I would expect.

I replaced the CLAP version Presets folder and database with those from the registered version, and that recognized my many freeware soundsets.

I then installed my commercial soundsets, so the linux CLAP Hive is ready for action.

[petedako]

…Buddy Miles!

Congratulations. Bitwig and Reaper are innovators. Let's hope for more DAWs to come on line. We need the options. It isn't ideal to have Steinberg holding all the marbles.

[spnc]

Is Repro coming with an update soon? 1 time out of 5 when I close the Repro 1/5 window on Mac (latest Ableton/Repro) on M1 Macbook, it crashes Ableton.

Been going on for the past 6+ months. So annoying, ruins the workflow.

Only using VST3 after I read some comments about .AU/.VST Repro instability but still same issue, crashes 1 time out of 5 when pressing the close window of the plugin.

HELP

[spnc]

Okay I found the issue. I no longer press (x) close window and instead use the Ableton tool button to hide/unhide Repro 1/5.



Problem seems to be gone (I pressed 50 times in a row to double check, so far no crash).

Will report if the problem is back.

Can't believe u-he didn't fix this simple issue in such a long time, crazy imagine the number of people whose life has been annoyed by this lol

[tasmaniandevil]

Can't believe u-he didn't fix this simple issue in such a long time, crazy imagine the number of people whose life has been annoyed by this lol

Do you want to know the number of people who have reported such a problem to our support in the past six months?

Zero. And Ableton Live is pretty much the most used host amongst our users.

If you experience an issue, why are you not sending us a mail to our support system, so we can help you find the cause, and instead complain about it in our community forum half a year later?

[pdxindy]

Damn you did everything wrong in your reply from A to Z, smth lol

Actually, it was a great reply!

You just don't like that it happens to show that you have no interest in solving the problem (if there even is one).

[tasmaniandevil]

Damn you did everything wrong in your reply from A to Z, smth lol

Here's an idea.
Why not try to act and communicate like a responsible, grown-up human being?
People might suddenly be interested in talking to you.
People might even want to help you.
It could be amazing.
It could change your life.
Might be worth a try.

[Hanz Meyzer]

Is the CLAP version of Diva MPE compatible? Is it possible to individually pitch midi notes? Thx

[pdxindy]

Is the CLAP version of Diva MPE compatible? Is it possible to individually pitch midi notes? Thx

No pitch slides yet on any of the CLAP synths... it's coming, but who knows when

[Hanz Meyzer]

I tested the clap versions a bit in Bitwig. Some problems:

1. The parameter automation still seems to be clunky: the automation lane does not show the unit and scale of the parameter, only percent always. Then does not seem to be possible to set a point with the exact current value, if the unit is not percent. Not sure if this is a problem on plug-in or host side.

2. The initial value, e.g. cutoff, starts with an obvious fade-in. So there also seems to be inertia applied on exact song start. But it should read out the pautomation value without any inertia at start. Not sure again if a Bitwig problem or U-He side. Reporting to Bitwig is cumbersome though (lack of proper communication).