> 1 - how to cleanly handle wave tables ? If you were to write an
> oscillator
> for example, how would you write the plugin:
>
> 2 -how to handle a list of parameters ? simply by accessing through a
> LADSPA_Data[]
> and a size, as in 1.b ?
>
There is no good way right now.
It appears to me that all these need are PortRangeHints
that can communicate a few different types. (and make connect_port
take a void* whose type depends on the range hints) ... someday.
(the design must be fairly careful for binary compatibility:
- one LADSPA_PORT_TYPED hint
- only allowed with LADSPA_PORT_CONTROL hint
- which makes the final member ``type'' of LADSPA_PortRangeHint
valid. It could be an enum or string for the type,
(LADSPA_TYPE_STRING, LADSPA_TYPE_FLOAT_ARRAY, etc))
- Dave
(ps for (1) it might be sort-of possible to use an environment variable pointing
to a .wav file, say -- at least the user would have some,
although pathetic, control)
