Hello and thanks for the response :)<br>I&#39;ve inlined my responses below:<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
JACK does not and will not support varispeed. Therefore slaving to MTC<br>
is going to be pretty limited. MMC also sends some speed commands that<br>
could not be supported by JACK.<br>
<div class="Ih2E3d"></div></blockquote><div><br>I understand, but I think limited MTC support is better than nothing. That being said, I don&#39;t think it&#39;s necessary to change JACK for this purpose, jackctlmmc&#39;s approach of being a jack compliant app that can drive JACK transport by listening to MMC signals seems like an elegant approach.<br>
&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
&gt; There&#39;s a small program called jackctlmmc that seems to do want I<br>
&gt; want, but it&#39;s a bit limited (seems pretty hardcoded) and I think that<br>
&gt; such a desirable feature should be integrated into a more widely used<br>
&gt; program. Any thoughts?<br>
<br>
</div>what does &quot;hardcoded&quot; mean?</blockquote><div><br>I made that comment in ignorance. I didn&#39;t see a place in the code where you could choose which MIDI device/port you were reading from, so I assumed that it just took the first registered one or hardcoded (specified in code instead of parameters passed into the program) a particular port. On closer inspection, it seems that you either have to patch a midi port to the application via JACK so it knows which one to read from, or it just reads from all alsa midi signals, either of which is perfectly reasonable. I&#39;m new to the JACK and ALSA APIs, and I&#39;m still waiting on a cable order to get my 8-track to talk to my PC, so I can&#39;t really test to see how this stuff works.<br>
<br>Currently jackctlmmc supports the &quot;play&quot;, &quot;stop&quot;, and &quot;rewind&quot; messages from MMC, and I&#39;m going to play with the code to see if I can add support for &quot;locate&quot; using jack_transport_locate() so that players can have a primitive seek-to type of function. I think that even this limited subset of MMC functionality is very desirable for linux audio engineers. I just want to be able to sit at my 8-track with my guitar and play/stop, rewind, and maybe seek around without having to keep clicking a mouse on a JACK app. <br>
<br>I&#39;m surprised that jackctlmmc doesn&#39;t seem to be that widely used (I can&#39;t find any packages for it in the major linux distros, and it only seems to be distributed via source code) when it provides such useful functionality. I&#39;d love to see it&#39;s functionality integrated into a GUI app like QJackCtl (which already has JACK transport buttons for play, rewind, fast-forward) instead of being a console application, but that&#39;s a subject for another email.<br>
<br>Thanks for your reply,<br>-- Alex<br></div></div>