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

[SaganTech]

I only tried with hive so far. While Hive supports CLAP_NOTE_DIALECT_CLAP it does not respond to CLAP_NOTE_EXPRESSION_TUNING.

Hi Jeremy, I've asked the developers, will let you know asap (might take until Monday, though).

That's funny, I thought you were the developer.

Also Hive does not respond to CLAP_NOTE_EXPRESSION_VIBRATO, useful for modulation wheel mapping me thinks.

[tasmaniandevil]

That's funny, I thought you were the developer.

Hahaha, I'm merely the guy who's searching for bugs all day.

[tasmaniandevil]

I'm not sure what this new modulation system is, I only know how to assign modulation in Bitwig to the automatable parameter list.

Short explanation:
https://cleveraudio.org/1-feature-overview/_modulation/

[Sound Author]

Selecting one of the Category/Features/Character options makes the Tag Menu disappear on my M1 Mac Mini.

[tasmaniandevil]

Selecting one of the Category/Features/Character options makes the Tag Menu disappear on my M1 Mac Mini.

Hmm, works fine over here on an M1 MacBook.
Which plugin and which host?
And where exactly do you select the Category/Features/Character options?
In the Tag menu on the left side, in the inspector on the right side, in the Tag this Patch menu, or in the smart folders section in the directory tree on the left side?

[Sound Author]

Selecting one of the Category/Features/Character options makes the Tag Menu disappear on my M1 Mac Mini.

Hmm, works fine over here on an M1 MacBook.
Which plugin and which host?
And where exactly do you select the Category/Features/Character options?
In the Tag menu on the left side, in the inspector on the right side, in the Tag this Patch menu, or in the smart folders section in the directory tree on the left side?

Using Diva CLAP beta Rev13510 in Bitwig v4.4
The "Tag This Patch" menu will disappear when I select any of the Category/Features/Character options. It does assign that tag though. You just have to keep opening the Tag This Patch menu over and over to finish tagging.

[tasmaniandevil]

Using Diva CLAP beta Rev13510 in Bitwig v4.4
The "Tag This Patch" menu will disappear when I select any of the Category/Features/Character options. It does assign that tag though. You just have to keep opening the Tag This Patch menu over and over to finish tagging.

Ah perfect, that helped, can reproduce this now in Diva.
It's not even a CLAP issue, happens in the VST3 as well.
We'll check that out. Thx a lot for reporting.

[Echoes in the Attic]

I'm not sure what this new modulation system is, I only know how to assign modulation in Bitwig to the automatable parameter list.

Short explanation:
https://cleveraudio.org/1-feature-overview/_modulation/

Yeah but we already knew that from the previous betas. We could assign modulation per voice through Bitwig's modulators and a CLAP plugins parameter in the plugin list. The description seemed to indicate there was a new way to assign this modulation as opposed to "the old way of Bitwig modulation via host automation."

[tasmaniandevil]

Yeah but we already knew that from the previous betas. We could assign modulation per voice through Bitwig's modulators and a CLAP plugins parameter in the plugin list. The description seemed to indicate there was a new way to assign this modulation as opposed to "the old way of Bitwig modulation via host automation."

Sorry for the misunderstanding.
In the first beta, quite a few of parameters didn't work with the new modulation system yet, and some of those that did work had quirks. This has been resolved now, and that was what was meant.

[Echoes in the Attic]

Yeah but we already knew that from the previous betas. We could assign modulation per voice through Bitwig's modulators and a CLAP plugins parameter in the plugin list. The description seemed to indicate there was a new way to assign this modulation as opposed to "the old way of Bitwig modulation via host automation."

Sorry for the misunderstanding.
In the first beta, quite a few of parameters didn't work with the new modulation system yet, and some of those that did work had quirks. This has been resolved now, and that was what was meant.

Oh ok so there's no new method of assigning modulation, just more parameters work now? Got it thanks. Yeah it was written in a strange way. It seems we still assign by bitwig modulation via automatable parameters, which is fine.

[Buckster]

fantastic - firstly thankyou very much - in particular for Bazille as the one I've been patiently waiting for

I might have found a bug though - just happened to be the first patch/attempt at poly modulation I tried but maybe one for someone else to try

I loaded up "Mellow Monster" one of my favourite patches, then modulated a step sequence against amount of Fractalize - and literally on first note press on my keyboard I had a loud micro burst (high pitched) - and instant cut off of audio from the plugin in Bitwig. Bitwig showed a momentary all red bar in the audio output level then nothing from the VST.

I retried same patch, same modulation (this time with speakers lower) and had same issue

<EDIT> could be using the Step sequencer as modulation as I just tried it with same patch against Frequency Cutoff and had same result - interestingly I momentary saw like waveform unlike I've seen on the analyser built into Bazille a sort of half a square wave but like it was completely clipped (square wave wasn't complete - didn't have the down part of the wave - and wasn't stable and was nearly at top of graph)

<EDIT 2> tried LFO on Frequency Cutoff and had same problem
I'm running 4.4 I haven't updated to 4.4.2 yet - I will try tomorrow

<EDIT 3> downloaded 4.4.2 - same problem. Even after Bitwig has cutoff the audio you can see something odd going on in the display on Bazille as suddenly it will recover and waveforms will look like you'd expect then a few seconds later you get the odd pulsating faint cut-off square sometimes disappearing completely, then will recover, then back to the odd waveforms

[tasmaniandevil]

I might have found a bug though - just happened to be the first patch/attempt at poly modulation I tried but maybe one for someone else to try

Thank you very much for that report.
I can reproduce it over here on an M1 MacBook using Bitwig 4.4.2.
It seems to only happen if you activate Bazille's multicore button in the CLAP version.
No problems as long as MC is switched off. No problems in the VST2 and VST3 version.
Not sure if it's a problem in the plugin or in Bitwig's thread pool multicore support, we'll investigate.

For the time being maybe best to avoid using the MC button in Bazille.

[tasmaniandevil]

nvm

[Buckster]

I might have found a bug though - just happened to be the first patch/attempt at poly modulation I tried but maybe one for someone else to try

Thank you very much for that report.
I can reproduce it over here on an M1 MacBook using Bitwig 4.4.2.
It seems to only happen if you activate Bazille's multicore button in the CLAP version.
No problems as long as MC is switched off. No problems in the VST2 and VST3 version.
Not sure if it's a problem in the plugin or in Bitwig's thread pool multicore support, we'll investigate.

For the time being maybe best to avoid using the MC button in Bazille.

No problems at all and thanks very much for the reply (and I'm glad was repeatable as thought it might be me doing something wrong).

All these updates to these already great VSTs are very much appreciated.

[Buckster]

just as a follow-up I had same issue without Multicore turned on - same patch - Mellow Monster - still leads to no audio output

<edit> the 2nd part I wrote and then deleted was incorrect - it was my user error. The bit I've left in still seems to be correct though.