2011/3/2 Olivier Guilyardi :
Mmm, this answer goes straight to the heart of the problem: what does
the UI actually represent?
Your examples show quite clearly that the visualization part might be
of great help, and I honestly won't support the idea that the host
should do that, since there are thousands of ways you could represent
Yet a problem remains... is data visualization really indivisible from
a plugin state and/or its input parameters?
Or, in more practical terms, should we consider visualization
belonging to the plugin GUI or not? I suspect that in theory it is
not, but in real world it is... since it would really be madness to
ask a plugin how it treats data, how could it ever be represented in
the most meaningful way w.r.t. its processing algorithm and asking it,
optionally, for a self representation in either a form of data that is
directly comparable to the input/output representation (compressor and
EQ example) or whatever else...
(I'm scared of myself at times)
Linux-audio-dev mailing list