News for hackers. Stuff that matters.
Re:Clap: New MIT license audio plug-in format from Bitwig by tialaramex on Sunday June 26, 2022 @06:29AM (#31882626)
> EDIT: ah! it looks like CLAP has delivered something i've been after in an audio API for some time: it appears to allow for dynamic parameters. i'm surprised it took this long!

What does this mean? I can imagine it being reasonable to have, for example, a wet/dry pot for a thing that's "not present" if you didn't enable the thing, since that pot is useless. Whether you want to reflect that as the pot magically "not existing" or just "disable" it or something so that user knows it isn't important is a small matter.

I'm way more dubious about genuinely dynamic parameters. If I can't look at your plug-in and decide it has 24 parameters, but must instead reason that it could have any number of parameters and those might change (every sample? every bar? On reload? Once per week?) then automation becomes unmanageable. If you say, but some of the parameters are not automatable - too bad, somebody will want to automate those parameters too anyway and they will fight you to do it.

Re:Clap: New MIT license audio plug-in format from Bitwig by foxhill on Sunday June 26, 2022 @09:19AM (#31883653)
> What does this mean?

so the particular use-case was for a sampler. we had a bunch of different samples that had their own domain parameters, which needed to be automatable. hell, even multi-sample sample selection (the process of choosing which samples of a multisampled sample-set to use) was automatable. it was hell.. aha.

that said, i envisenged a few other scenarios although they mostly revolve around variable IO (e.g. variable numbers of sidechained inputs, etc.)

> I'm way more dubious about genuinely dynamic parameters.

you're right to be. the approach i came up with was a conceptually a mess - although i guess it worked - the dynamic portions of automation could be mapped basically the same way that one routes audio in the daw. you have, say, 10 automatable gain parameters visible to the host, then in the plugin you'd route that to your chosen parameter.

no joke, there was the question of making the parameter mapping itself automatable. i told them it was impossible and i would die on that hill, which is technically not a lie.

Re:Clap: New MIT license audio plug-in format from Bitwig by olivejun on Sunday June 26, 2022 @07:46AM (#31883089)
I think they were referring to the audio API itself when mentioning wanting dynamic parameters to implement when writing plugins. I may be wrong though!

Also, I just want to say in general, devs in music tech need a lot more love :( Fighting a dev over a design decision in a plugin is really commonplace online for some reason and its unfortunate being that most complaints can be easily solved with a solid foundation in sound and digital audio.

Re:Clap: New MIT license audio plug-in format from Bitwig by tialaramex on Sunday June 26, 2022 @12:42PM (#31885474)
In this context by "fight you" I meant things like you find that even though you surface an automation API as expected, since they can't automate the things they want through your API they cause your GUI to run, inside a virtual environment in which the "pointer" is controlled by their software so as to click on gadgets at the appropriate time and then they whine that your plug-in (which is rendering a GUI) is too bloated and slow compared to the plug-ins that they're doing conventional automation for.