I think my first problem may be that JACK midi ports are not what everything is using, and are more in a "proposed" state; _ALSA_ midi ports are what I'm used to seeing in QJackCtl.
I _think_ I should be looking at some example ALSA code for the MIDI-input, and referring to JACK examples for the audio-output. cheers Rua HM. --- Rua Haszard Morris <[EMAIL PROTECTED]> wrote: > I'm trying to compile the jack_midisine example > client > (from the jack source download) so I can start > playing around with developing a jack client. > > I have installed libjack-dev and libalsa-dev. It > seemed (I could've been mistaken) that the example > clients weren't present in the libjack-dev package, > so > I downloaded the source package from jackaudio. > > Then I configure/make/sudo make install, and > everything seems like I may have done this right, > when > I log out and back in I can get QJackCtl to use the > built (/usr/local/bin/)jackd. > > However, when I run a midi client, the midi ports > show > up in QJackCtl as audio ports. Other than that > things > seemed to work, but I'm guessing I'm going about > this > in a strange/incorrect way. > > Can anyone point me to a howto or give me some > newbie > tips for developing a midi->audio jack client under > 64studio, with minimum impact on the standard > 64Studio > setup? > > Thanks in advance, and apologies for the hairy > newbie > question... > Rua HM. > > Send instant messages to your online friends > http://au.messenger.yahoo.com > > _______________________________________________ > 64studio-devel mailing list > [email protected] > http://lists.64studio.com/mailman/listinfo/64studio-devel > Send instant messages to your online friends http://au.messenger.yahoo.com _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
