<br><br><div class="gmail_quote">On Sat, May 29, 2010 at 10:11 AM, Julien Claassen <span dir="ltr"><<a href="mailto:julien@c-lab.de">julien@c-lab.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello Paul!<br>
No my sequencer's ports don'te really appear. they appear, when they are connected to somthing.<br>
I now did it like this:<br>
I saw that jack_midi_clock was automatically connected to<br>
j2a_bridge:playback<br>
In ALSA I have port 129 listed with "aconnect -li".<br>
So I asked my sequencer to connect to 129 and get its clock source there. The rest of the sequencer connections were pure ALSa for the test.<br>
Then I started jack_transport and told it to "play".<br>
Nothing happened, yet that might be due to the clock. But would you say, that this setup looks sane?<br></blockquote><div><br>i can see no reason to be using j2a_bridge at all for what you're doing. <br></div></div>