We love the idea of CLAP and plan to support this exciting format in a future version of Unify. It is painful trying to support all plug-ins even of the same VST format because the documentation is not complete. This reworked standard is so desperately needed and these guys are doing this 100% Right. This is AS BIG as the introduction of MIDI in 1982.
I wholeheartedly hope this takes off. It's great. We don't need a gazillion proprietary standards, we need one open-source standard to rule them all. I also love the fact that the companies standing behind this project are small companies that are still passionate about what they do, unlike big companies that don't seem to care about their customers. Specifically U-He and Bitwig, which are two of my favorite companies music software companies.
Let me explain the reasoning they aren't. Bitwig's future timeline has online collaboration support in real-time. They need a unified plugin format so that all controls align with everyone that is live collaborating on a project no matter what OS they are using. This is where CLAP comes in and expands on this idea. Now all plugins will be able to share all information with all instances across the internet. This is the future Bitwig is setting up for and why they decided this needs to be public and widely adopted. They know very well what they are doing and I am excited to see how the future major versions of Bitwig will surprise us all!
As a Bitwig user, I already LOVE polyphonic modulation. Being able to do simple things like pitch-bending individual notes in a chord, to complex things like randomly modulating EVERY parameter of a synth FOR EACH VOICE SEPARATELY. I can already do this with bitwig devices, but being able to do it with 3rd-party CLAP plugins is going to be awesome.
@@bassc Absolutely. But check out the list of companies already looking into. Regarding JUCE, this is worked on as well (but not yet from the JUCE people).
I heard about this in passing, but this is the first time I watch any explanation of how it works, and it sounds like it was both long overdue and a complete gamechanger that will make life a lot easier for plugin manufacturers and end users alike, which hopefully leads to the very quick adoption of this as the new de facto standard.
The best thing about this effort is that it's a bug industry middle finger to Steinberg. Nobody likes their standards and sdks, not even to speak about their business practices. So, this at least got some heads turning! (Although personally I still feel that all the reasons mentioned for having CLAP where already well considered for LV2, just too bad of all the FUD around it. I'm sure there is an alternate universe where Alexandre actually enjoyed implementing LV2 and that's the format that "won" ;) )
Let me explain the reasoning they aren't. Bitwig's future timeline has online collaboration support in real-time. They need a unified plugin format so that all controls align with everyone that is live collaborating on a project no matter what OS they are using. This is where CLAP comes in and expands on this idea. Now all plugins will be able to share all information with all instances across the internet. This is the future Bitwig is setting up for and why they decided this needs to be public and widely adopted. They know very well what they are doing and I am excited to see how the future major versions of Bitwig will surprise us all!
This is great, please let's get CLAP plugins to run on the GPU and CPU multi-core with the ability to choose one or the other or both like the GPU audio reverb plug. Thank you for this format keep pushing don't let CLAP turn into CRAP plug-in.
Does CLAP open the door to developers of both DAWs and hardware midi controllers to make it easier for them to automatically work out of the box? Not just some of the functions, but all of them and easily configurable. There seems to be a big hole in the market for plugins that could use something like CLAP to further the control and functionality of midi controllers.
Plugin standards are really about making the relationship between plugins and their host applications better. Initiatives to improve controller integration with daws with daws and plugins are certainly something that I think bitwig does well, because of its controller scripting engine. If you aren't familiar with bitwig, it is already light years ahead on making controllers work well with plugins. Additionally, I hope CLAP will empower users to really use their multi-core CPUs to build up their DSP performance. If it also solves the shitstorm of 80 plugin vendors with 80 separate preset browsers, that would be wonderful.
@@EannaButler I wonder if they have any future plans of implementing audio over ethernet, like audiogridder, also open source, which would allow CLAP to utilize DSP servers over the network.
Will we ger the possibility for a plugin to read shared resources off the daw? I.e samples and even more importantly midi clips. This could be used as a generic arp format for example, or midi "glitching" of patterns.
Really exciting development. I wonder if the 32 bit/64 bit format will remain an issue with the CLAP format? It would be cool too if it was platform independent.
@@Artek604 v3 maybe? VCV isn't known for having an open roadmap and regular updates. People have been waiting (and complaining) for AU support since the v2 launch, which could still be many months away. I would keep my expectations low here.
CLAP needs to focus first and foremost on utilizing the power of you GPU for audio and visual processing in its core. This will open up incredible innovation in the plugin industry. Bitwig if you're reading this PLEASE allow us to undo plugin tweaking states. Now if I undo the plugin disappears.
good outcome of the discussion re. CLAP's name is, we all know now there's a creme for that other one. (and I guess we all know now who's had it - great to see so many people speaking out about it openly!)
Is there a near-zero-compute wrapper for VST 2? And for VST3? I.e. host VST2 and VST3 plugins in a CLAP wrapper? I.e. standardise the VST/AU/AAX interface behind a standardised CLAP format? That would make it irresistible! Reason as a plugin as a CLAP plugin, and M1/M2 native wrapper outside of the M1/Rosetta state of the DAW, would be a dealbreaker......... I.e. CLAP for the win!
Yes, wrappers to and from any common platform have been spotted in the open source community. People working on some projects think they'll be ready for prime time in a month or two.
@@UrsHeckmannBerlin My original comment was at best misleading.. Apologies! I guess under the mess of my comment was a question... Does CLAP operate as per Bitwig's ability to host plugins as a separate process from the DAW? Where communication between DAW and plugin is over inter-process channels (RPC, Sockets,..)? If yes, then putting a CLAP wrapper over VST plugin in some standardised way, would be a way for a DAW that supported CLAP to implement Bitwig's off-process instantiation of plugins. Which would allow say a vst plugin not built for M1 to be wrapped by CLAP and run separately from the M1-native DAW.
@@EannaButler Hehehe, I'm not sure I totally understand the question. But yeah, CLAP plug-ins of course run in a separate process in Bitwig Studio, and that would be the same if they wrapped any other format.
@@UrsHeckmannBerlin Ha, what is wrong with me? 🤔😊 I guess the question is whether a DAW that implements CLAP receives off-process instantiation of plugins 'for free'? Or off-process instantiation is nothing to do with the CLAP standard, and is solely for the DAW to implement? Appreciate your patience here! 😊
sweet - it is pretty tiring to see tons of cool open source projects that must be compiled by yourself to VST - which removes a huge number of users. Hopefully this brings in more freedom to share plugins!
Haha, seriously though, they maybe should have thought twice about that for a name, you shouldn't underestimate the immaturity or nerdy musicians (I'm guilty)
@@davetbassbos jokes aside it's seriously a ball-drop (ayo, there's another one.) Both Bitwig and u-He's Heckmann Audio are based in Germany and I think it's safe to say they didn't run the name idea past a single native English speaker from the UK, the USA, or etc. to make sure they weren't going to send thousands of people running around the world proclaiming that CLAP is the best thing they've ever gotten. It's a huge face-palm and it's proactively unkind of them to establish a standard that evokes laughter, snickers, and people losing their concentration because of an unfortunate double-meaning for chlamydia that's lost in the subtext of English language. Seriously, who names something and doesn't take the time to google "what are other meanings for 'the word I am naming my product' in the languages that will likely be talking about my product in the years to come?"
I will say u-He makes awesome plugins and maybe they deserve a little bit of a pass being German, you know focused on the engineering and all, with no time to worry about what some less than mature English speakers might snicker about? but still, lol!
@@UrsHeckmannBerlin good news. Why is that? Because of different methods of each plugin to organise their presets, i.e. folders and sub-sub folders and user folders?
@@smuram no, because MIDI arrives in a plug-in on a time critical thread. This means, the plug-in must not access files or allocate memory upon a MIDI message - all of which it needs to do to load a preset. Instead the plug-in needs to store the MIDI in a pre-allocated queue, which it reads from an internal timer. So, preset loading will be delayed. Now, there's an exception. And that is when you're offline rendering (mixdown). Then it needs to be instant. There are a few issues with that, too. So you see, there are a lot of technicalities involved for something that seems so simple.
These guys are doing great work, but they’re so down in the weeds they can’t explain the concept or the benefits very well. They need someone who gets it and can explain it to musicians in a compelling way. I thought one of the guests on the last sonic state talk actually summed it up very well.
whoever that person is is going to have a very hard time getting past the eye-rolls when announcing this "hot new thing that they totally gotta get" called THE CLAP
It will be interesting to see how Steinberg responds, if at all, to CLAP. The respectable response would be to compete with CLAP by coming out with VST4... The likely response however, will be absolute silence and continuing to let VST3 rest on its laurels.
@@superactivitylad given STAINberg's attitude with consumers and developers alike with vst2 and forced migration to vst3, I seriously doubt there would be much in the way of confidence to continue sticking with steinberg's standard in the foreseeable future, should adoption of CLAP become more widespread.
I’m not sure. I think the DAW landscape is also changing quite a bit and the older ones that are maintaining quite large and possibly a bit antiquated code bases are probably also feeling a bit of heat there. The fact that AVID (aax!) and Reaper have already joined that club is interesting to say the least. And then there’s Epic Games!!!… I think the audio industry might start moving a bit faster than it used to in the years to come and you might not want to miss that train!
Well as soon at the absence of #Clap support in #Cubase and #nuendo will be a strong enough argument to walkaway, #Steinberg will have to adress it to stay in the game.
@@urssounds Epic games taking up this tech makes perfect sense. A lot of more recent game releases have already been incorporating in-game audio DSP as part of the game experience (not just fancy graphics/shaders, see!). Using a standardised plugin API architecture for such effects would allow for having even more modular control with the types of sound effects processing to be made available ingame, instead of having to build it from the ground up as part of the engine. Or even potentially reducing audio asset sizes to be procedurally generated instead of 'pre-rendered' playback streams, and making in-house CLAP modules reusable across their own different projects. I wonder if FMOD are already joining in on this too.
The CLAP standard seriously needs some marketing effort behind it. The first selling point to ALL parties, from DAW and plug-in manufacturers to consumers is being able to double the amount of plug-ins a system can run. The next couple of years will involve people stretching the service life of existing computer hardware. There is a shirtage of price and a recession is almost inevitable. Being able to double the effectiveness of plug-ins is worthy of a modest update fee for DAWs or a paid update of a plug-in. The existing customer base will open their wallets. The names and email addresses are pretty much on hand. Not bad for a day's work per plug-in. So again, the take away, double the amount of plug-ins with no upgrades to hardware. Finally ( I only made it to 22 minutes), but if the standard ALSO streamlined the usage of GPU processors as DSP farms, you'd have an irresistible nee standard that eould generate a lot of additional revenue for all vendors in a tighter market. Sidenote... I'm old enough to remember when developing clap meant a trip to the doctor and some penicillin pills. It just made me giggle.
Wonderful initiative and great concept... The name HAS to change... you cannot possibly hope to get adoption for something with the slang name for an STD
Yes, let's talk CLAP, I'm here to learn about safe reproduction methods so as to avoid the terrible thing that people on the street call Cl-... oh, sorry, wrong room
Bitwig: Has the time to develop new plugin format, but not enough time to make the gridlines visible behind the clips.. I want to switch to Bitwig so much, Lives PDC is unacceptable.. But its just unusable software when I cant see the grid while arranging. Please please please please fix this, and then continue with CLAP.
Hey it's Pie here :) This isn't a Bitwig project, it's a joint effort between multiple companies/individuals including u-he and Surge (Urs mentions 20 or so people involved about 20 minutes into the video). I know you're frustrated because, but you are asking Bitwig to put your needs and maybe the needs of a few others who are similarly affected, above the industry as a whole. Also you need to get inline behind everyone who has been begging for months, years even for MSEG modulators :D
We love the idea of CLAP and plan to support this exciting format in a future version of Unify. It is painful trying to support all plug-ins even of the same VST format because the documentation is not complete. This reworked standard is so desperately needed and these guys are doing this 100% Right. This is AS BIG as the introduction of MIDI in 1982.
Fabulous! That's great to hear! I was gonna contact you, but man, so much feedback...
I wholeheartedly hope this takes off. It's great. We don't need a gazillion proprietary standards, we need one open-source standard to rule them all. I also love the fact that the companies standing behind this project are small companies that are still passionate about what they do, unlike big companies that don't seem to care about their customers. Specifically U-He and Bitwig, which are two of my favorite companies music software companies.
Let me explain the reasoning they aren't. Bitwig's future timeline has online collaboration support in real-time. They need a unified plugin format so that all controls align with everyone that is live collaborating on a project no matter what OS they are using. This is where CLAP comes in and expands on this idea. Now all plugins will be able to share all information with all instances across the internet. This is the future Bitwig is setting up for and why they decided this needs to be public and widely adopted. They know very well what they are doing and I am excited to see how the future major versions of Bitwig will surprise us all!
then they're doomed there were many attempts on online collaboration and nobody succeded
As a Bitwig user, I already LOVE polyphonic modulation. Being able to do simple things like pitch-bending individual notes in a chord, to complex things like randomly modulating EVERY parameter of a synth FOR EACH VOICE SEPARATELY. I can already do this with bitwig devices, but being able to do it with 3rd-party CLAP plugins is going to be awesome.
For real. The utility of being able to just add a polyphonic envelope or LFO to a 3rd party synth or effect if you need one is huge.
u-he with full MPE support? BRING IT ON! :)
Yep... will start this once the dust settles...
I would start use it immediately. I think producers and mixers are going to love this.
@@bassc Absolutely. But check out the list of companies already looking into. Regarding JUCE, this is worked on as well (but not yet from the JUCE people).
Great chat. What a pleasure to see this level of collaboration
Great stuff, really nice to see the legendary Urs too
I heard about this in passing, but this is the first time I watch any explanation of how it works, and it sounds like it was both long overdue and a complete gamechanger that will make life a lot easier for plugin manufacturers and end users alike, which hopefully leads to the very quick adoption of this as the new de facto standard.
Very excited about CLAP!
Placidus Schelbert is an awesome name.
A round of applause for CLAP :)
Need this for Reason soooooo badly! We don't even have VST3 support!
Yes! I was already reading up on CLAP and this interview comes at a perfect time^^
support for MIDI 2.0? what about support for using GPU as that is also a major development in plugins?
The best thing about this effort is that it's a bug industry middle finger to Steinberg.
Nobody likes their standards and sdks, not even to speak about their business practices.
So, this at least got some heads turning!
(Although personally I still feel that all the reasons mentioned for having CLAP where already well considered for LV2, just too bad of all the FUD around it. I'm sure there is an alternate universe where Alexandre actually enjoyed implementing LV2 and that's the format that "won" ;) )
A huge industry AND consumer middle finger to STAINberg can only be a good thing after decades of stifling innovation in computer music.
Let me explain the reasoning they aren't. Bitwig's future timeline has online collaboration support in real-time. They need a unified plugin format so that all controls align with everyone that is live collaborating on a project no matter what OS they are using. This is where CLAP comes in and expands on this idea. Now all plugins will be able to share all information with all instances across the internet. This is the future Bitwig is setting up for and why they decided this needs to be public and widely adopted. They know very well what they are doing and I am excited to see how the future major versions of Bitwig will surprise us all!
The possibilities with Synth Memers are endless here, as Nick Batt discusses the clap
The future is bright for the STD Synth meme integration.
This is great, please let's get CLAP plugins to run on the GPU and CPU multi-core with the ability to choose one or the other or both like the GPU audio reverb plug. Thank you for this format keep pushing don't let CLAP turn into CRAP plug-in.
I wish I could see presets for each CLAP plugin in the Bitwig preset browser window. Like Vital presets for example.
Very good description about this powerful Standard
Will this standard allow for plugin Patch Names to be queried, browsed, selected, switched and saved from within the DAW?
Placidus, amazibg how you did not change !
Does CLAP open the door to developers of both DAWs and hardware midi controllers to make it easier for them to automatically work out of the box? Not just some of the functions, but all of them and easily configurable. There seems to be a big hole in the market for plugins that could use something like CLAP to further the control and functionality of midi controllers.
Plugin standards are really about making the relationship between plugins and their host applications better. Initiatives to improve controller integration with daws with daws and plugins are certainly something that I think bitwig does well, because of its controller scripting engine. If you aren't familiar with bitwig, it is already light years ahead on making controllers work well with plugins.
Additionally, I hope CLAP will empower users to really use their multi-core CPUs to build up their DSP performance. If it also solves the shitstorm of 80 plugin vendors with 80 separate preset browsers, that would be wonderful.
Agree. I expect midi 2.0 spec implementation in CLAP will assist with midi controller integration.
@@EannaButler I wonder if they have any future plans of implementing audio over ethernet, like audiogridder, also open source, which would allow CLAP to utilize DSP servers over the network.
Does this mean a CLAP plugin version is exactly the same no matter which OS we use??
One version fits all kinda thing??
Cheers
great job, nick. very informative and clear.
Great stuff. Congrats guys.
Why aren't u-he plugins available in Clap format yet if he is one of the founders?
Will we ger the possibility for a plugin to read shared resources off the daw?
I.e samples and even more importantly midi clips. This could be used as a generic arp format for example, or midi "glitching" of patterns.
Or maybe even write into those resources: e.g. an audio/midi looper plugin that can automatically fill a clip with its looped content.
Really exciting development. I wonder if the 32 bit/64 bit format will remain an issue with the CLAP format? It would be cool too if it was platform independent.
Hoping that it will be implemented into reaper eventually as well since it's ooen
I wont be getting the CLAP because I'm in a steady relationship with my hardware.
VCV rack has polyphonic modulation hope see that in CLAP plugins.
They're on the list of developers looking into it, so I'm pretty certain we'll see CLAP version soon(ish).
@@Artek604 v3 maybe? VCV isn't known for having an open roadmap and regular updates. People have been waiting (and complaining) for AU support since the v2 launch, which could still be many months away. I would keep my expectations low here.
These two folks on the bottom would really benefit from some acoustic panels, a closer mic or a different streaming room.
CLAP needs to focus first and foremost on utilizing the power of you GPU for audio and visual processing in its core. This will open up incredible innovation in the plugin industry. Bitwig if you're reading this PLEASE allow us to undo plugin tweaking states. Now if I undo the plugin disappears.
This is so exciting and needed, great work
I’ve had the clap for years
good outcome of the discussion re. CLAP's name is, we all know now there's a creme for that other one. (and I guess we all know now who's had it - great to see so many people speaking out about it openly!)
Just beautiful 🙏♥️
Heads up, the Image Line affiliate link is broken and needs to be updated.
Is there a near-zero-compute wrapper for VST 2? And for VST3? I.e. host VST2 and VST3 plugins in a CLAP wrapper? I.e. standardise the VST/AU/AAX interface behind a standardised CLAP format? That would make it irresistible! Reason as a plugin as a CLAP plugin, and M1/M2 native wrapper outside of the M1/Rosetta state of the DAW, would be a dealbreaker......... I.e. CLAP for the win!
Not sure CLAP's purpose is anything about re-wrapping other plugins, there is no benefit to adding layers for the sake of layers.
Yes, wrappers to and from any common platform have been spotted in the open source community. People working on some projects think they'll be ready for prime time in a month or two.
@@UrsHeckmannBerlin My original comment was at best misleading.. Apologies!
I guess under the mess of my comment was a question... Does CLAP operate as per Bitwig's ability to host plugins as a separate process from the DAW? Where communication between DAW and plugin is over inter-process channels (RPC, Sockets,..)?
If yes, then putting a CLAP wrapper over VST plugin in some standardised way, would be a way for a DAW that supported CLAP to implement Bitwig's off-process instantiation of plugins.
Which would allow say a vst plugin not built for M1 to be wrapped by CLAP and run separately from the M1-native DAW.
@@EannaButler Hehehe, I'm not sure I totally understand the question. But yeah, CLAP plug-ins of course run in a separate process in Bitwig Studio, and that would be the same if they wrapped any other format.
@@UrsHeckmannBerlin Ha, what is wrong with me? 🤔😊
I guess the question is whether a DAW that implements CLAP receives off-process instantiation of plugins 'for free'? Or off-process instantiation is nothing to do with the CLAP standard, and is solely for the DAW to implement?
Appreciate your patience here! 😊
Still watching this but waiting to see if this is platform agnostic. Update: seemingly it is.
Yeah but I reckon Apple won't support it. They used to embrace standards but they hate them now.
sweet - it is pretty tiring to see tons of cool open source projects that must be compiled by yourself to VST - which removes a huge number of users. Hopefully this brings in more freedom to share plugins!
Everyone should get CLAP
Someone had to say it.
already had it in the 70's. Dr. gave me some cream and pills fixed it right up
Haha, seriously though, they maybe should have thought twice about that for a name, you shouldn't underestimate the immaturity or nerdy musicians (I'm guilty)
@@davetbassbos jokes aside it's seriously a ball-drop (ayo, there's another one.) Both Bitwig and u-He's Heckmann Audio are based in Germany and I think it's safe to say they didn't run the name idea past a single native English speaker from the UK, the USA, or etc. to make sure they weren't going to send thousands of people running around the world proclaiming that CLAP is the best thing they've ever gotten. It's a huge face-palm and it's proactively unkind of them to establish a standard that evokes laughter, snickers, and people losing their concentration because of an unfortunate double-meaning for chlamydia that's lost in the subtext of English language. Seriously, who names something and doesn't take the time to google "what are other meanings for 'the word I am naming my product' in the languages that will likely be talking about my product in the years to come?"
I will say u-He makes awesome plugins and maybe they deserve a little bit of a pass being German, you know focused on the engineering and all, with no time to worry about what some less than mature English speakers might snicker about? but still, lol!
So, does Pro Tools use CLAP?
I hope it has a new standard for MIDI controllers, make all Devs use the same CC for things like ADSR and filters
Would be nice to see "synth" layout midi controller. Wouldnt mind the usual 8x knob&fader in it too
Because Clap will communicate the Metadata of the plugin, your daw should automatically map these features to controls in your Daw.
Will it finally get a patch/preset up or down possibility through assigning a knob? Wonder why it still not exist.
it is less trivial than it sounds, But yeah it's on our radar.
@@UrsHeckmannBerlin good news. Why is that? Because of different methods of each plugin to organise their presets, i.e. folders and sub-sub folders and user folders?
@@smuram no, because MIDI arrives in a plug-in on a time critical thread. This means, the plug-in must not access files or allocate memory upon a MIDI message - all of which it needs to do to load a preset. Instead the plug-in needs to store the MIDI in a pre-allocated queue, which it reads from an internal timer. So, preset loading will be delayed.
Now, there's an exception. And that is when you're offline rendering (mixdown). Then it needs to be instant. There are a few issues with that, too.
So you see, there are a lot of technicalities involved for something that seems so simple.
@@UrsHeckmannBerlin thanks a lot for this explanation
Ableton will start supporting CLAP in 20 years after the whole industry will shift to CLAP 2.
These guys are doing great work, but they’re so down in the weeds they can’t explain the concept or the benefits very well. They need someone who gets it and can explain it to musicians in a compelling way. I thought one of the guests on the last sonic state talk actually summed it up very well.
whoever that person is is going to have a very hard time getting past the eye-rolls when announcing this "hot new thing that they totally gotta get" called THE CLAP
They have an excellent pedagogue at Bitwig in the person of Dave Linnenbank. I am confident we will get more content about CLAP soon.
Will Steinberg play game?
It will be interesting to see how Steinberg responds, if at all, to CLAP. The respectable response would be to compete with CLAP by coming out with VST4... The likely response however, will be absolute silence and continuing to let VST3 rest on its laurels.
@@superactivitylad given STAINberg's attitude with consumers and developers alike with vst2 and forced migration to vst3, I seriously doubt there would be much in the way of confidence to continue sticking with steinberg's standard in the foreseeable future, should adoption of CLAP become more widespread.
I’m not sure. I think the DAW landscape is also changing quite a bit and the older ones that are maintaining quite large and possibly a bit antiquated code bases are probably also feeling a bit of heat there. The fact that AVID (aax!) and Reaper have already joined that club is interesting to say the least. And then there’s Epic Games!!!… I think the audio industry might start moving a bit faster than it used to in the years to come and you might not want to miss that train!
Well as soon at the absence of #Clap support in #Cubase and #nuendo will be a strong enough argument to walkaway, #Steinberg will have to adress it to stay in the game.
@@urssounds Epic games taking up this tech makes perfect sense. A lot of more recent game releases have already been incorporating in-game audio DSP as part of the game experience (not just fancy graphics/shaders, see!). Using a standardised plugin API architecture for such effects would allow for having even more modular control with the types of sound effects processing to be made available ingame, instead of having to build it from the ground up as part of the engine. Or even potentially reducing audio asset sizes to be procedurally generated instead of 'pre-rendered' playback streams, and making in-house CLAP modules reusable across their own different projects.
I wonder if FMOD are already joining in on this too.
👏
Kannst gleich ein Video darüber machen 🤪😳
@@chris5375 hab ich doch schon 👏
@@PolarityMusic ok, hab’s gesehen,sehr geil 👌
I’m still waiting for many plugins to become VST3…..
👏👏👏
Says it all...
Clever Unique Name This
"What a silly bunt."
😁
Is there an AAX version 🤣
Avid is looking into CLAP format, so they might actually add it to ProTools next to AAX
yeah make the music industry more attractive, does the MIT license actually allow forking this project?
comnts on these kinds of videos and I know for a fact that guys like Nice tutorialm have gotten strikes from TH-cam for having crack info in their
The CLAP standard seriously needs some marketing effort behind it.
The first selling point to ALL parties, from DAW and plug-in manufacturers to consumers is being able to double the amount of plug-ins a system can run.
The next couple of years will involve people stretching the service life of existing computer hardware. There is a shirtage of price and a recession is almost inevitable. Being able to double the effectiveness of plug-ins is worthy of a modest update fee for DAWs or a paid update of a plug-in. The existing customer base will open their wallets. The names and email addresses are pretty much on hand. Not bad for a day's work per plug-in.
So again, the take away, double the amount of plug-ins with no upgrades to hardware.
Finally ( I only made it to 22 minutes), but if the standard ALSO streamlined the usage of GPU processors as DSP farms, you'd have an irresistible nee standard that eould generate a lot of additional revenue for all vendors in a tighter market.
Sidenote... I'm old enough to remember when developing clap meant a trip to the doctor and some penicillin pills. It just made me giggle.
Wow👑💣Monster😈
Wonderful initiative and great concept... The name HAS to change... you cannot possibly hope to get adoption for something with the slang name for an STD
Hmmmmmm ..... 🤔
Yes, let's talk CLAP, I'm here to learn about safe reproduction methods so as to avoid the terrible thing that people on the street call Cl-... oh, sorry, wrong room
OK Boomer
It will fade away in time…Mark my words…
Not many devs will jump onboard.
Way too many plugins standards already-Protools anyone…?
I can't help but think of Gonorrhea now with this name lol, a bit unfortunate.
Anyone else want to get the Clap with me?
sa
CLAP real need to change the name
But millions of people bought Digital VD players :)
No. CLever Audio Plugins works very well. And not everyone's in UK...
@@Artek604 Yes. CLAP doesn't work very well. And this reference doesn't only apply to people that live in the UK.
agree, stupid name
There's something to be said about those who hear the word "clap," and their first thought is an STD as opposed to the action or the sound.
tNice tutorials really helped
Bitwig: Has the time to develop new plugin format, but not enough time to make the gridlines visible behind the clips.. I want to switch to Bitwig so much, Lives PDC is unacceptable.. But its just unusable software when I cant see the grid while arranging. Please please please please fix this, and then continue with CLAP.
Hey it's Pie here :) This isn't a Bitwig project, it's a joint effort between multiple companies/individuals including u-he and Surge (Urs mentions 20 or so people involved about 20 minutes into the video). I know you're frustrated because, but you are asking Bitwig to put your needs and maybe the needs of a few others who are similarly affected, above the industry as a whole. Also you need to get inline behind everyone who has been begging for months, years even for MSEG modulators :D
Great technical ideas, terrible name. They’ve really got to change the name!