Exactly right. I’m really after fine control of the detune parameter so I can record some subtle pitch change automation envelopes. Gain would be nice too.
Out of curiosity, is the gist of the implementation to change the chooser (behind the scenes M4L.chooser.js?) to point to a clip (or is it clipaudio) rather than device?

If it’s an easy hack, I’d be happy to run with a one-off that was missing a nice UI FWIW. For example, if I had a m4l device that ONLY automated clip params to complement @ithkaa’s version for devices, I’d be really happy.
EDIT: actually had a little luck changing the argument to the M4LChooser object to clipaudio @observe 1 and got clips to show up. Unfortunately, I don’t think parameter is right for the clip params as I don’t see anything when I try and list them. Looking at M4L.chooser.js I see:
parameter : { fun: iterate_parameters_for_id, name: "Parameter", container: ["parameters", "mixer_device\\s+\\S+"] },
which at a quick read feels specific to device parameters… Not sure what the right clipaudio container is though. 