If the host honors the "CLAP_PARAM_IS_READONLY" flag, Apricot will not be able to automate filter mode, which in my opinion, is a shame. If the host ignores "CLAP_PARAM_IS_READONLY", the host can at least automate the filter mode from the interface. The synth would be better if it told the truth and let the host automate those values. Changing the filter mode (and other parameters now marked read only) sounds really cool.
sagantech
2
Posts
1
Topics
A member registered Sep 19, 2022
Recent community posts
Thank you for making this wonderful synthesizer. I have recently added CLAP support to my DAW (www.saganech.biz) and have been doing tests with all CLAP plug-ins I can find. Anyway Apricot works very well. I did have a bug whereby I was setting the .time field to a negative number and this was causing Apricot to write over random memory. It is fixed now so that is not my concern. I was doing some automation recording with Apricot and I noticed, for example, 'Filter Mode' has a range of 0 to 1 and the supplied labels go from 0% to 100%. The values for LP, HP ad BP are some very very small numbers near 0. Imagine how this looks on a graph. The difference between the values are imperceptible. To make matters worse, if the values are edited and sent back to Apricot, Apricot deselects all of the filters if it not a known value. It would certainly make more sense to have the labels be correct.. "LP", "HP", "BP", for the CLAP_PARAM_IS_STEPPED flag to be set and if you need room for future filter types have a few reserved. If you would like to discuss this more please contact me at info_AT_sagantech.biz. Jeremy