On Sun, 1 Nov 2009, Paul Davis wrote:
>
> i meant to use a name. LV2-E<N> would simply mean LV2 core + {some
> defined set of extensions}. plugin and host authors could then talk
> about using "LV2-E<N>".
> the E<N> part merely designates a particular set of extensions, which
> might be 2 extensions, or 100.So... something like this? LV2-EBasic := LV2 core + URI Map + MIDI Event LV2-EPlus := LV2-EBasic + External UI LV2-EExtreme := LV2-EPlus + dynparam + Progress LV2-EVideo := LV2-EBasic + SMTP + Transport Note: Yes, I know some of those extensions don't exist or are proposals. Some may not even relate. I'm still trying to understand it. :-) BTW: Some of the extension API's seem more like plumbing. Resources for communicating between plugins. Things that have little relevence to the end user. For example, the URI Map seems like it's just a utility for an extension or a plugin -- but the host doesn't necc. need to add support for it. Is this right? Peace, Gabriel _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
