CLAP 1.0 betas for ACE, Diva, Hive, MFM 2.5

[teilo]

So I'm experiencing some drastic performance drops with Diva Clap 1.4.5 compared to VST3 and VST2 versions of the plugin - running a single instance of the default patch in Bitwig 4.3, playing a simple loop of 2 notes;
Load avg (VST2/3): ~.65ms
Load avg(CLAP): ~1.45ms

This is with multicore off, but there are similar differences with it enabled.

Not sure if this is actually an issue, or if it's just an unoptimized (debug?) build?

0.8 milliseconds is a dramatic performance drop? That's a rather dramatic statement.

[dss32]

So I'm experiencing some drastic performance drops with Diva Clap 1.4.5 compared to VST3 and VST2 versions of the plugin - running a single instance of the default patch in Bitwig 4.3, playing a simple loop of 2 notes;
Load avg (VST2/3): ~.65ms
Load avg(CLAP): ~1.45ms

This is with multicore off, but there are similar differences with it enabled.

Not sure if this is actually an issue, or if it's just an unoptimized (debug?) build?

0.8 milliseconds is a dramatic performance drop? That's a rather dramatic statement.

The absolute difference isn't the issue here - it's taking over twice as long to generate the same output. And of course if you're trying to get latency down to a minimum, 0.8ms extra _is_ a big deal.

[tasmaniandevil]

Load avg (VST2/3): ~.65ms
Load avg(CLAP): ~1.45ms

I'm seeing identical load average performance over here (0.231ms) on a 2020 MacBook Pro M1 when I play two notes on the init patch.
What's your system, Mac, Windows, Linux? Which CPU? And what sample rate & buffer size are you using?

[Urs]

If there is any excess overhead at this point, I guess it's debug code.

Our CLAP versions should run faster than others on average because other formats require us to schedule MIDI and stuff by ourselves. That is, in other formats for each event we create our own version of it and collect that for later use.

In CLAP we don't do this extra step, we use the queued events directly without copying anything since CLAP events are already in a single queue that is easy to iterate.

[dss32]

Load avg (VST2/3): ~.65ms
Load avg(CLAP): ~1.45ms

I'm seeing identical load average performance over here (0.231ms) on a 2020 MacBook Pro M1 when I play two notes on the init patch.
What's your system, Mac, Windows, Linux? Which CPU? And what sample rate & buffer size are you using?

Windows 10, i7-4790k
256sample buffer @ 48khz (Steinberg UR22)
The performance differential seems to be the same at other buffer sizes
E.g
64 samples:

VST: 0.21ms
CLAP: 0.45ms

[dss32]

Just another note that Diva (CLAP) consistently crashes within Bitwig 4.3 when trying to modulate the Glide parameter. Apologies if this has been reported already.

[tasmaniandevil]

Just another note that Diva (CLAP) consistently crashes within Bitwig 4.3 when trying to modulate the Glide parameter. Apologies if this has been reported already.

Yes, known issue. Some parameters currently don't work with the new modulation system yet, or crash. We're on it.

Please keep reporting such issues. Better to have things reported twice than not at all.

[tulamide]

Because the first CLAP plugins now drop, please let me ask a favor of you: It would be awesome, if there was some type of "user installation guidelines" for those developers. What bugs me is that most installers just copy the ultra-bad habit of automatically installing into "C:\program files\common files\CLAP"
Please stop this while CLAP is still fresh! I (and most musicians/producers I know) have a different approach. My system drive is hosting the system and nothing else. All my instruments are on their own drive, and all my sample libraries on yet another drive. This is very important. Nothing should ever be stored on the system disk. I'm totally fine with an installer that pre-sets the install path to a system folder, but lets me install anywhere I want to. I'm not ok with installers that just install to the system folder without a chance to change that behavior.

[Tj Shredder]

Nothing should ever be stored on the system disk.

Paranoia??? Ever used a laptop? Are symbolic links unknown to Windows?
I guess 99.999999999% of all computer users do store something on the system disk... Maybe you have a lonely secret nobody else knows of?
I can only tell, that on Macs it helps a lot that plugins (not sample content or presets) are stored on a defined place. If you are literate enough to organize it differently its no problem to do so...

[mabian]

Nothing should ever be stored on the system disk.

Paranoia??? Ever used a laptop? Are symbolic links unknown to Windows?
I guess 99.999999999% of all computer users do store something on the system disk... Maybe you have a lonely secret nobody else knows of?
I can only tell, that on Macs it helps a lot that plugins (not sample content or presets) are stored on a defined place. If you are literate enough to organize it differently its no problem to do so...

Come on... the "lonely secret" is having two different partitions on the same physical disk, one for the OS only and the other for whatever needed to make music, especially samples and projects.
This way, if you ever have to reinstall the OS, most of the files are still already there, especially sample libraries and so on...and I know symbolic links exist, but why use them when plugins could store - or look for - data wherever the user decide?

- Mario

[Tj Shredder]

Its 2022 I stopped partitioning my drives maybe 15 years ago… I never had to wipe a disk to reinstall the OS… And even if I would need to, I can restore all my files from a timemachine backup, even on to a new version of the OS…
Having the plugins on definite places, eases support a lot, they belong to my system anyway…

[mabian]

Its 2022 I stopped partitioning my drives maybe 15 years ago… I never had to wipe a disk to reinstall the OS… And even if I would need to, I can restore all my files from a timemachine backup, even on to a new version of the OS…
Having the plugins on definite places, eases support a lot, they belong to my system anyway…

We're all different, but we should be given freedom of choice...

... and, even if I don't have to reinstall the OS, I could move to a whole different system (yes disks and computers break sometimes and people upgrade ), and in this case having everything clean in its own partition already would help a lot saving time.

- Mario

[ThomasHelzle]

There is a dedicated thread for installer criticism:
viewtopic.php?t=583188

Cheers,

Tom

[tulamide]

There is a dedicated thread for installer criticism:
viewtopic.php?t=583188

Cheers,

Tom

Thanks!

[shaboogen]

Sorry if this has been mentioned already (I searched the thread but couldn't find anything), but is anyone else having tuning issues with the preview version of Hive? There's certain intervals that sound pretty significantly off (for me it's most noticeable at the A3 perfect 5th).

This is happening on all versions (CLAP, VST2 and VST3) on Bitwig, and happening on the VST2 version on Reason (don't think it can load any other format).

When I revert to the version on the u-he website, doesn't seem to be happening on either the VST2 or VST3 versions.

Any info would be great. Keen to get onto the CLAP version if for no other reason than the performance uplift.

Thanks