[LAD] LV2 port groups

[Jörn Nettingsmeier]

michael, there are plans to implement the ACN/SN3D scheme in the LV2
plugin standard.
since it's based on rdf, the question is whether it might feasible to
use the URLs for each ACN on ambisonics.ch as unique identifiers (which
would be quite elegant and point users right to the relevant
documentation).
however, that would depend on whether you could guarantee stability of
said URL space. a short excerpt of the preceding discussion is quoted
below. please maintain the cc: list when replying.

best,

jörn



David Robillard wrote:
> On Sun, 2009-08-16 at 19:22 +0200, Jörn Nettingsmeier wrote:
>> David Robillard wrote:
>>> On Sun, 2009-08-16 at 18:27 +0200, Jörn Nettingsmeier wrote:
>>>> David Robillard wrote:
>>>>> On Mon, 2009-08-10 at 11:02 -0400, David Robillard wrote:
>>>>>> http://lv2plug.in/ns/dev/port-groups.lv2/port-groups.html
>>>>> P.S. Comments on this from anyone with experience in multi-channel stuff
>>>>> would be appreciated if there's any problems.
>>>>>
>>>>> It's being used to support proper multi-channel streams for LV2 in
>>>>> GStreamer (work in progress), in keeping with the theme of getting along
>>>>> better with them desktop guys :)
>>>>>
>>>>> Personally I would like to see this sort of metadata get exposed at the
>>>>> JACK level quite a bit (e.g. so things can do auto-connect logically).
>>>>> All we'd need is a key/value system...
>>>> is anybody using this yet? if not, can i suggest that the ambisonic
>>>> groups be renamed to #H#P, and that #H#V be reserved to that new scheme
>>>> introduced by travis, as explained in another mail?
>>> (The "re-use" of #H#V there seems crazy to me... (re: your other email))
>>>
>>> Anyway, no, nobody is using this yet.  I'm really just defining things
>>> at this point so future stuff that needs it can use it easily and get
>>> along.  First thing's first and all that.
>>>
>>> I will name the groups (multi-channel) H#P.  I suppose I should use e.g.
>>> acn1Channel rather than wChannel for the roles (single channel) too...
>> yes. with all that rdf magic, is it possible to include a pointer to
>> http://ambisonics.ch/standards/channels/ directly in the spec?
> 
> Good point.  They actually have existing URIs for each channel, e.g.
> http://ambisonics.ch/standards/channels/ACN3
> 
> I could maybe just use these directly as the URI for the channels... how
> stable is this URI scheme?
> 
> (I'll work in links either way, excellent documentation...)
> 
> Thanks,
> 
> -dr
>