Sehr interessanter Ansatz, der einen eigenen Thread verdient hat.
Eure Meinungen, bitte...
Eure Meinungen, bitte...
Quelle: https://www.bitwig.com/de/stories/201/Bitwig and u-he are excited to announce CLAP (“CLever Audio Plug-in API”), the new open standard for audio plug-ins and hosts. CLAP offers modern features, innate stability, and rapid support for plug-in and host developers. And since it's open source and liberally licensed, CLAP is a safe bet for the future.
Advantages of CLAP for MusiciansDeveloped in collaboration with experts from diverse fields in the music software industry, CLAP is a cutting-edge plug-in standard, designed for modern computers, software, and paradigms. CLAP caters to novel DAW concepts, and opens up new horizons for what a plug-in can do or be.
Here are some immediately useful advantages of CLAP:
Better Performance From Modern CPUsDeveloped with modern CPUs in mind, CLAP takes multi-thread management to a new level, with a clear and efficient allocation of roles between plug-in and host. Specifically, CLAP allows collaborative multicore support between plug-in and host through a so-called “thread-pool”, also allowing hosts to manage CPU-threading for plug-ins that provide their own multicore support. Preliminary tests show significant performance gains compared with current solutions.
Better and Faster OrganizationCLAP hosts can read plug-in metadata and help organize your plug-ins. As CLAP hosts can retrieve information from plug-ins without having to wait for them to initialize, plug-in scans can be much faster.
Furthermore, we’re currently finalizing an extension which lets plug-ins tell the host which files they need (e.g. samples or wavetables), and the host can consolidate those in the project file. That means you'll never lose a sample while transferring a project between systems!
Better ModulationThe CLAP standard promotes new ways to create music with automation, modulation, and expressions. Here are a few examples:
With this new standard we aim to inspire host developers to add exciting new features to their products. Initial implementations by Bitwig, u-he and the Surge project demonstrate just a few of the possibilities.
- CLAP supports per-note automation and modulation (in accordance with the recent MIDI 2.0 specifications).
- Going one step further, CLAP’s parameter modulation concept allows for temporary parameter offsets. Parameter modulation is non-destructive, so as soon as the modulation has finished, the target parameter will return to its original state.
- CLAP makes it possible for polyphonic plug-ins to have their per-voice parameters modulated for individual notes (“MPE on steroids”).
Information for Plug-In and Host DevelopersThe KISS (keep it simple, silly) mantra belongs to CLAP. From the C-only ABI, which allows binding to any programming language, to the transparent client-server model between host and plug-in, the robustness and clarity of the threading model, and the single event queue for all kinds of parameter changes, timing and MIDI. Despite being so comprehensive, everything in CLAP is easy to find and easy to implement.
A single cpp/hpp glue layer for C++ offers a quick start into the ABI, and its built-in “proxy layer” finds common threading bugs in an instant. Apropos C-only ABI: There are no platform specific dependencies: In theory CLAP should also run well on embedded platforms, game consoles or specialized supercomputers.
Open Source & Liberal LicenseCLAP is open source, released under the MIT license: No fees, memberships or proprietary license agreements are required before developing or distributing a CLAP capable host or plug-in, and the license never expires. In a nutshell, there are no entry hurdles for developers, and plenty of open source projects already benefit from CLAP.
MIDI Just Works!Inspired by MPE and MIDI 2.0, CLAP can adapt to any future MIDI standard. Wherever a solid standard exists, we allow developers to freely decide how to apply it. Plug-ins can receive and send any MIDI event on multiple ports.
Extensibility & GovernanceA simple system for extensions makes CLAP future-proof. Companies can offer proprietary extensions if required for specific features.
CLAP 1.0 is the result of a multi-year project initiated by u-he and Bitwig, with design and implementation contributions by a group of commercial and open source audio developers from across our industry. As we proceed beyond the initial set of extensions, we are committed to establishing a transparent process to govern the standard which allows participation from the entire audio software community. We welcome participation from the development community today, and we will share details of these processes and governing models over the second half of 2022.
An Invitation to Collaborate and ExploreCLAP does not only exist on paper; there are several ways you can try it out now. See the links below for projects from u-he, Bitwig, and others. Several other industry players are currently evaluating the CLAP standard.
Available From Bitwig, u-he and Others TodayBitwig Studio 4.3 (Latest Beta)
u-he CLAP beta versions
Surge Synth Team
Open Source Projects Using CLAPAvendish project
CLAP JUCE Extensions project
Companies and Projects to Watch Out ForFollowing companies and projects are already evaluating CLAP for their host and plug-in software:
Epic Games (Unreal Engine)
Node Audio (Entonal Studio)
For DevelopersFor latest updates, example code and information check CLAP's Github page: