Something that was suggested for GMPI, and might be applicable for LADSPA is a convetion where port names can be written as paths, eg for a delay line you might have "delay/base delay (ms)" "delay/feedback (%)" "lfo 1/ammount (%)" "lfo 1/wave" "lfo 1/frequency" "lfo 2/ammount (%)" "lfo 2/wave" "lfo 2/frequency" this would allow the host to group the controls logically when building the UI, eg. tabbing them, and friendlier OSC reflections of plugins.

It would require that lexical /'s be escaped, but other than that it should be transparent. Its only worth adding if hosts would implement something using it though, as it would cause a bit of disruption, there are about 30 exisiting ports with /'s in them.

Something that was suggested for GMPI, and might be applicable for LADSPA is a convetion where port names can be written as paths, eg for a delay line you might have "delay/base delay (ms)" "delay/feedback (%)" "lfo 1/ammount (%)" "lfo 1/wave" "lfo 1/frequency" "lfo 2/ammount (%)" "lfo 2/wave" "lfo 2/frequency" this would allow the host to group the controls logically when building the UI, eg. tabbing them, and friendlier OSC reflections of plugins. It would require that lexical /'s be escaped, but other than that it should be transparent. Its only worth adding if hosts would implement something using it though, as it would cause a bit of disruption, there are about 30 exisiting ports with /'s in them. A different character could be used, but / seems like the obvious one.