<div dir="ltr">@Paul and Frederick - Thank you both. This clears everything up. :)<div><br></div><div>@Paul - the metadata api you mentioned, is there any plans of this coming to jack2? </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 17, 2015 at 7:39 AM, Frederick Gleason <span dir="ltr"><<a href="mailto:fredg@paravelsystems.com" target="_blank">fredg@paravelsystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Nov 15, 2015, at 20:03 57, Hai Nguyen <<a href="mailto:codingforlove@gmail.com">codingforlove@gmail.com</a>> wrote:<br>
<br>
> So I was wondering what kind of mapping there is between say L and R<br>
> channels and JACK ports? Or does a mapping even exists?<br>
<br>
</span>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.<br>
<br>
Cheers!<br>
<br>
<br>
|---------------------------------------------------------------------|<br>
| Frederick F. Gleason, Jr. | Chief Developer |<br>
| | Paravel Systems |<br>
|----------------------------------------------------------------------|<br>
| The real problem with hunting elephants is carrying the decoys. |<br>
| -- Anonymous |<br>
|---------------------------------------------------------------------|<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Jack-Devel mailing list<br>
<a href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a><br>
<a href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org" rel="noreferrer" target="_blank">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a><br>
</div></div></blockquote></div><br></div>