I am going to join the "hip" kids and start some CLAP implementation too. As the famous quote goes, "you gotta do what you gotta do", but why not have some fun while at it too.
I am considering doing live-streams for such implementation. Again following the cool kids 😎
Want to ask though if anyone is even interested.
So Yay or Nay..?
@falktx cool to see the progress you're making with it! your opinions largely match mine.
the UI -> DSP sync/queue for parameter editing gestures was weird at first but it wasn't too hard to deal with in the end.
the lack of UI idle is a good thing imo. kind of wondering how you're dealing with that in VST3? host doesn't provide idle there either
@wrl there is a timer extension to have an idle loop, similar to how vst3 does it. the main difference is that, at least in bitwig, this timer extension is not linux/X11 specific.
for both clap and vst3 I use the idle loop from the system (which on my case comes from pugl) whenever possible, which is macos and windows. then the host idle loop extension thingy makes the linux side of things work.
@wrl just to be clear, I am not using fd stuff, but the timer extension.
Tested to work fine (plugins work as usual) in both Bitwig and Reaper.
and btw, funny to see Bitwig being the pusher for the standard, while not implementing it fully. I already found a few things where bitwig doesnt follow the spec.
@falktx to be fair, cubase is the worst vst host i've come across, so at least there's precedent for this ;)
@falktx yeah true! not sure how the fd signalling extension would work on windows at least, i reckon nobody's going to implement that there. macos, sure, but probably better to just use the NSRunLoop methods
regardless, happy to see more CLAP adoption :D