So developers can smoothly transition their existing codebase to CLAP and still support pretty much all other formats as if they were developing for these directly. The gist is: A CLAP plug-in can tell its wrappers and adapters what it would be like if it was that kind of plug-in. The host manufacturers can deploy these adapters themselves, the plug-in manufacturers can add them to their CLAP installers, or the users can install them. For some other formats it's possible to create open source adapters, for some it needs to be closed source. For AU we (u-he, not CLAP devs) have planned to offer a CLAP-to-AU wrapper for developers. All other formats can be abstracted from it. It's simply not important.įor any developer who starts out or wants to have a solid base, CLAP is gonna be an easy choice. "The question "so who's gonna support it?" is pretty much what has killed all prior efforts to do this. Urs from u-he lays it out in post #16 (on page 6) from that thread: until Lisa Su brought AMD back (and Apple started making their own chips). until they created the Microsoft/Intel franchise. History has a way of repeating itself - IBM was invincible. The increasingly heavy handed tactics of Microsoft and Apple will cause more people to try Linux than any plugin spec, just like the tactics of Steinberg and Apple are causing devs to try alternatives. It won't bring more *users* to Linux, but that's ok. Will this *directly* benefit Linux audio? A well supported non-proprietary plugin standard will benefit all platforms, including Linux. I'm sure the other devs - large and small - would be happy to see Steinberg have less influence on the industry. Only one dev benefits from the VST format - Steinberg. What is even more interesting question here is how other large, corporate devs will respond. Right now Windows/VST is the easiest route, Windows/CLAP would be even easier. That is already the case with some plugins being Windows/VST only. The proprietary formats won't go away, but if CLAP takes off, many smaller devs will not bother to jump through the proprietary hoops. If a few more hosts like *ehem* Reaper support it, it stands a good chance. The CLAP standard can exist alongside the proprietary ones. The good thing is that it's not an either/or situation. It sounds like people are unhappy enough to take action. Reaper supporting LV2 and now plugin devs like U-He getting behind CLAP. The audio dev community has been unhappy with the handling of the VST standard for a while now, especially since VST3 happened.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |