On Sun, Nov 15, 2015 at 8:56 PM, Chris Caudle <chris(a)chriscaudle.org> wrote: all true, although a port's flags do provide some indications: IsTerminal: this port represents the "edge" of JACK: data delivered or received here comes from or goes to "outside" JACK IsPhysical: this port represents a hardware audio channel there is also a metadata API that allows arbitrary information to be associated with ports. Unfortunately, it has only been implemented for JACK1 at this time.

@Paul and Frederick - Thank you both. This clears everything up. :) @Paul - the metadata api you mentioned, is there any plans of this coming to jack2? On Tue, Nov 17, 2015 at 7:39 AM, Frederick Gleason <fredg(a)paravelsystems.com > On Nov 15, 2015, at 20:03 57, Hai Nguyen <codingforlove(a)gmail.com> > > So I was wondering what kind of mapping there is between say L and R > > channels and JACK ports? Or does a mapping even exists? > > Assuming that one is speaking of *audio* ports (as opposed to, say, MIDI), > all ports are single-channel. Designations like ‘left’ or ‘right’ (or > 'left-front', ‘right-rear’, etc) are up to the application layer. JACK > provides the mechanism, not the policy. > > Cheers! > > > |---------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |----------------------------------------------------------------------| > | The real problem with hunting elephants is carrying the decoys. | > | -- Anonymous | > |---------------------------------------------------------------------| > > _______________________________________________ > Jack-Devel mailing list > Jack-Devel(a)lists.jackaudio.org > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >

I have no real involvement with JACK2 whatsoever. Last I knew, empty stub functions for the metadata API had been added by felipe coehlo (falktx) but I know nothing more than that. On Tue, Nov 17, 2015 at 1:06 PM, Hai Nguyen <codingforlove(a)gmail.com> wrote: