2011/9/26 David Robillard <[email protected]>: > <pedantry> > It's debatable whether or not this violates the spec: > > "Hosts that do not support a specific port class MUST NOT instantiate the > plugin, unless that port has the connectionOptional property set" > > This is ambiguous. We might want to reword that slightly in the next > revision to explicitly state that hosts can instantiate if they understand > *some subset* of the port types that describes a port type they support, > i.e. unknown additional types can be ignored. This implies new port types > can't modify the definition of others, which is good and should be explicit > anyway. > </pedantry>
<useless-rant> This is IMO unfortunate of the LV2 spec, a host does not only have to check for supported features, but also go through all ports and check type and connectionOptional. We could just have features for port types defined in extensions... </useless-rant> Stefano _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
