KVR Audio

koalaboy · Post by **koalaboy** » Sun Jun 19, 2022 5:28 pm

Think of WOOT as being the kontakt point for your YOLO sample that you sell (forgive my spellink)

vad.martyn · Post by **vad.martyn** » Sun Jun 19, 2022 5:28 pm

all this time I was thinking it’s a plugin for synthesizing claps.

But this looks even worse. It’s a headache sometimes because some plugins aren’t vst3 or 64bit yet, etc, and here is a new plugin format CLAP

Urs · Post by **Urs** » Sun Jun 19, 2022 5:31 pm

Well, let's take the example of WrapClap Inc.

WarpClap Inc. offers to CLAP developers to put their Clappy.clap into their WrapClap.vst3 for a one time fee of 25$, and for another 5$ renames the filename of WrapClap.vst3 to Clappy.vst3. Another 10$ for hosting on WrapClap.music. $5 rebate on the next.

So many scenarios to consider. Which one will it be?

Urs · Post by **Urs** » Sun Jun 19, 2022 5:31 pm

vad.martyn wrote: Sun Jun 19, 2022 5:28 pm all this time I was thinking it’s a plugin for synthesizing claps.

It is, among other things.

zvenx · Post by **zvenx** » Sun Jun 19, 2022 5:37 pm

trackbout wrote: Sun Jun 19, 2022 5:22 pm Haha, I feel like I just read the script for Inception.

Anyway, didn't I say the developer of YOLO would not need a license form Steinberg if it was loaded through WOOT? Not sure what you're saying differently other than also making the developer of YOLO a reseller of WOOT.

tbh, I understand what you are saying.
I, like you, am reading what urs as saying as inception, a movie I still don't fully understand.

My original question was simply does clap allow a developer to create vst3 plugins without signing SB's vst3 licensing agreement.
rsp

vad.martyn · Post by **vad.martyn** » Sun Jun 19, 2022 5:40 pm

It would be great if CLAP could wrap 32bit plugins and vst2 plugins into a 64bit format so all those obselete plugins like Steinberg-Wizoo Virtual Guitarist 2 could be used in 64bit DAW

Urs · Post by **Urs** » Sun Jun 19, 2022 5:45 pm

zvenx wrote: Sun Jun 19, 2022 5:37 pmMy original question was simply does clap allow a developer to create vst3 plugins without signing SB's vst3 licensing agreement

The answer is "yes", but the matter is more complex than questioning and answer suggest: There are a few more things to consider. Hence, depending on the perspective, the answer could as well be "no", because the place where the "creation" happens might very well be the computer of the user, not the computer of the CLAP developer.

Urs · Post by **Urs** » Sun Jun 19, 2022 5:46 pm

vad.martyn wrote: Sun Jun 19, 2022 5:40 pm It would be great if CLAP could wrap 32bit plugins and vst2 plugins into a 64bit format so all those obselete plugins like Steinberg-Wizoo Virtual Guitarist 2 could be used in 64bit DAW

Writing such a bridge is possible in any format, it's not anything that the format itself can solve.

trackbout · Post by **trackbout** » Sun Jun 19, 2022 5:47 pm

zvenx wrote: Sun Jun 19, 2022 5:37 pm
trackbout wrote: Sun Jun 19, 2022 5:22 pm Haha, I feel like I just read the script for Inception.

Anyway, didn't I say the developer of YOLO would not need a license form Steinberg if it was loaded through WOOT? Not sure what you're saying differently other than also making the developer of YOLO a reseller of WOOT.
tbh, I understand what you are saying.
I, like you, am reading what urs as saying as inception, a movie I still don't fully understand.

My original question was simply does clap allow a developer to create vst3 plugins without signing SB's vst3 licensing agreement.
rsp

I think I just got it from the Clappy.clap example.

It seems like a third scenario where the developer of YOLO would need to have a relationship with the developer of WOOT, and then ultimately it gets presented to the user as loading a single plugin, from a file called yolo.vst3, but the developer of YOLO would not need a license from Steinberg. My confidence level in the accuracy of that explanation is about 3%.

zvenx · Post by **zvenx** » Sun Jun 19, 2022 5:51 pm

Urs wrote: Sun Jun 19, 2022 5:45 pm
zvenx wrote: Sun Jun 19, 2022 5:37 pmMy original question was simply does clap allow a developer to create vst3 plugins without signing SB's vst3 licensing agreement
The answer is "yes", but the matter is more complex than questioning and answer suggest: There are a few more things to consider. Hence, depending on the perspective, the answer could as well be "no", because the place where the "creation" happens might very well be the computer of the user, not the computer of the CLAP developer.

Do you mean a developer creating a converter/adapter which a user buys and then converts their purchased clap plugins to vst3?
I think that is a theoretical/unusual situation for the average plugin user, who a developer sells their plugins too..

Most purchasers of plugins, I strongly believe buy a plugin if it is available in the format their daw can use and buy it and use it in their DAW.

rsp

Urs · Post by **Urs** » Sun Jun 19, 2022 5:53 pm

trackbout wrote: Sun Jun 19, 2022 5:47 pmMy confidence level in the accuracy of that explanation is about 3%.

Yeah, it took me a while to fully understand those concepts, but after a while they feel natural.

Urs · Post by **Urs** » Sun Jun 19, 2022 5:57 pm

zvenx wrote: Sun Jun 19, 2022 5:51 pm
Urs wrote: Sun Jun 19, 2022 5:45 pm
zvenx wrote: Sun Jun 19, 2022 5:37 pmMy original question was simply does clap allow a developer to create vst3 plugins without signing SB's vst3 licensing agreement
The answer is "yes", but the matter is more complex than questioning and answer suggest: There are a few more things to consider. Hence, depending on the perspective, the answer could as well be "no", because the place where the "creation" happens might very well be the computer of the user, not the computer of the CLAP developer.
Do you mean a developer creating a converter/adapter which a user buys and then converts their purchased clap plugins to vst3?
I think that is a hypothetical/unusual situation for the average plugin user, who a developer sells their plugins too..

Most purchasers of plugins, I strongly believe buy a plugin if it is available in the format their daw can use and buy it and use it in their DAW.

rsp

Again, the developer of YOLO.clap can simply bundle WOOT.vst with the same download, and the transformation of WOOT.vst3 to YOLO.vst3 can happen transparently on the user's computer.

Pop Up: "Would you like to install WOOT.vst3? Would you like WOOT.vst3 to be renamed to YOLO.vst3 and have YOLO appear as VST3 plug-in on your computer? [yes/no]"

Urs · Post by **Urs** » Sun Jun 19, 2022 5:58 pm

(text needs to be carefully massaged by lawyer, In think - a service that WrapClap Inc. should probably be prepared to offer)

10bd01 · Post by **10bd01** » Sun Jun 19, 2022 5:59 pm

Urs wrote: Sun Jun 19, 2022 5:45 pm The answer is "yes", but the matter is more complex than questioning and answer suggest: There are a few more things to consider. Hence, depending on the perspective, the answer could as well be "no", because the place where the "creation" happens might very well be the computer of the user, not the computer of the CLAP developer.

This nuanced answer may underwrite more confusion. I understand the complexity, but I think unless otherwise specified most people here are referring to commercially released plugins; and on that count I'm hearing "no" - if a developer wants to commercially release a VST3 plugin they need a license from Steinberg, period, regardless of what they do "behind the scenes" to develop it.

CLAP... thoughts?