On Tue, Mar 18, 2003 at 12:04:46 +0100, Francois Dechelle wrote: > > A better solution would be to expand the ID space to 64bits, and reserve > > the top bit's worth, which is plenty, but will break binary compatibility > > of course. > > In any case, hosts that save the ID cannot restore the plugin settings > correctly, if the ID is assigned dynamically.
Yes, but the ID number would be created from a hash of the unqiue identifier (eg. a URI), so it would be consistant between sessions. > > > Another question: is there a plan to get plugin port values that are not > > > floats? More precisely, I am thinking of transforming a patch that does > > > granular synthesis into a plugin. But this patch needs a sound file > > > name. How can I pass it to the LADSPA plugin? > > > > You can't. I think this is thought to be outside the remit of LADSPA. > > Too bad. Is there any trick to twist LADSPA plugins for that? Not cleanly. You do can hacks with /tmp files and control values, but they are messy. - Steve