<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 16/10/14 18:19, Phil CM wrote:<br>
</div>
<blockquote cite="mid:543FFE21.3040901@gnu.org" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Re: [LAD] How can a LV2 plugin know on what host's
MIDI Channel it's on?</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date:
</th>
<td>Thu, 16 Oct 2014 13:16:38 -0400</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From:
</th>
<td>Paul Davis <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:paul@linuxaudiosystems.com"><paul@linuxaudiosystems.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td>Phil CM <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:philcm@gnu.org"><philcm@gnu.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 16, 2014 at 12:59 PM,
Phil CM <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:philcm@gnu.org" target="_blank">philcm@gnu.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class=""> <br>
<div>On 16/10/14 17:15, Paul Davis wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 16, 2014
at 11:42 AM, Phil CM <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:philcm@gnu.org"
target="_blank">philcm@gnu.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">Is there a
way to retrieve this info (and others,
ideally) from the host, thus removing the
need for a "midi channel" control port?<br>
</blockquote>
<div><br>
</div>
<div>I think you're confused. The host
doesn't put a plugin on a MIDI channel. It
delivers MIDI events to the plugin which
might be on any channel. <br>
</div>
</div>
</div>
</div>
</blockquote>
</span> But in Qtractor I do have a choice of what
MIDI channel (or any/omni, for that matter) I'm
sending signal to on that particular track... So, no?
No way for the plugin to retrieve any info from the
host (I mean specific info, not just instantiated,
port enum et al) I guess it makes sense since it would
introduce a breaking point. Sorry, I don't really
speak english, I'm just persuaded I do.<span class=""><br>
</span></div>
</blockquote>
<div><br>
</div>
<div>That is a host-specific issue. The part of the LV2
specification and the existing extensions don't describe
that functionality. As far as the plugin is concerned,
it just gets MIDI events. If the host is filtering some
of them, the plugin has no way to determine this
programmatically.<br>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Wow, not even the very channel it's broadcasting on in readable?
Does that mean that I <b>have</b> to implement a MIDI channel
selection in my synth? There is no way to go around this?<br>
<br>
--Phil<br>
</body>
</html>