lol let’s hope so or Nick won’t give it his blessing.
I don’t want to mess around with beta versions so I’m eagerly awaiting Bitwig 4.3 full to drop so I can try CLAP versions of these u-he plugins out. I have hit stability issues before with Repro and CPU so hoping this improves things.
btw if anyone has been thinking about making the jump to Bitwig, there’s currently a full version for sale on Knobcloud for $185 with upgrades through to Feb 23. A pretty good deal.
I’ve noticed an issue with the CLAP version of VCV2.0 Pro version 2.2: Seems to work fine, except, the plugin does NOT get MIDI clock . I opened the VST3 Plugin for comparison and found that This DOES get MIDI clock. Is that an issue with CLAP? or Bitwig? I’m using Bitwig 4.4
Same here, Windows 10, from both 4.4.3 (& 4.4.4 Early Access), VCV Rack 2 (v2.2.0) CLAP plugin isn’t in list (perhaps it’s discarded by Bitwig, in case of plugin failure).
Yes, I am using Beta version 4.4.3 … It does appear … and have 4… count 'em FOUR VCV icons.in the browser… . and didn’t pay enough attention when I clicked on the first one (which happened to be the CLAP version of VCV2.). I later discovered that if I chose the VST3 version… everything worked - including MIDI in clock.
Somone finally let me know the CLAP version is buggy.
I couldn’t find anything about this on google search… hence my confusion. I like the CLAP format… I have great hope for its future… (i.e. not being dictated by Steinberg and some of the promised performance benefits)… though I can see that it’s not quite ready for prime time.
I downloaded the latest version last night, and the first thing I did was see if the clock worked in CLAP. It doesn’t.
I’m looking through this forum specifically for this reason, to see what I can learn before I report anything.
Have issue (CLAP) if I use MIDI-CV module as clock generator (either CLK/N output port, and CLK port).
Only once clock pulse when I start DAW’s transport!