# FR: Support CLAP for plugins (host & client) **URL:** \ **Category:** Feature Requests\ **Created:** [June 18, 2022, 3:03pm UTC](https://forum.juce.com/t/fr-support-clap-for-plugins-host-client/51860 "2022-06-18T15:03:48Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![kunz](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kunz](https://forum.juce.com/u/kunz)\ **Post date:** [December 14, 2022, 10:42am UTC](https://forum.juce.com/t/fr-support-clap-for-plugins-host-client/51860/11 "2022-12-14T10:42:28Z")
I would also like to see CLAP support. But adding CLAP support also means sample accurate modulation, automation, and the integration of expressions for me. I would like to see some bigger changes and simplifications in the JUCE wrappers to make this possible (sample accurate handling of parameters, expressions, and MIDI data in the same function → processing method) : > [@Sample accurate parameter automation?](https://forum.juce.com/t/sample-accurate-parameter-automation/50277/66): > > I’m not sure if we should take the VST3 standard. I also see some problems when we have to check the parameters for changes. There are also questions about how this works when you are using the ValueTreeListener to update your parameters also for the DSP code. We have a plugin with \>10000 parameters. I don’t think I can check them all when the buffer size is 32 samples and I like to have the DSP code decoupled from parameter value classes. At the moment we have to use the listeners to update … --- _[View the full topic](https://forum.juce.com/t/fr-support-clap-for-plugins-host-client/51860)._