<br><br><div class="gmail_quote">On Sat, May 29, 2010 at 8:55 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 everyone!<br>
Sorry to bother again, but I'm confused. I want to do a little skullduggery. So I started these:<br>
jackd - for basic audio/midi and transport<br>
a2jmidid -e - To expose my ALSA MIDI ports to JACK<br><br></blockquote><div><br>good decision<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
j2amidi_bridge - to expose my JACKMIDI stuff to ALSA<br></blockquote><div><br>unnecessary decision. a2jmidi -e is already there.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
jack_midi_clock - to generate a good clocksource, that's bound to the transport system of JACK<br></blockquote><div><br>not sure what kind of clock this generates, but fine.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Now I want to start a midi sequencer (alsamidi capable) and connect the jack_midi_clock to it.<br></blockquote><div><br>but you haven't started one yet. or so it appears ...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The midi sequencer somehow has it's ports hidden, but can connect to any input/output alsaseq port.<br></blockquote><div><br>its ports should not be hidden. do they show up in aconnect -i and/or aconnect -o? <br></div>
</div>