Re: midi backend not working in qjackctl?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I appear to be using the alsa backend - at least, 'alsa' is what's selected under the 'driver' drop-down box in qjackctl.

Thanks anyway.

On Mon, Mar 12, 2012 at 11:02 PM, Arnold Krille <arnold@xxxxxxxxxxxxx> wrote:
On Monday 12 March 2012 20:44:50 James Mckernon wrote:
> I seem to recall that setting qjackctl's 'midi driver' option to 'seq' is
> supposed to make a copy of all the midi ports in the 'alsa midi' tab under
> the 'jack midi' tab. This used to work fine for me, but bafflingly doesn't
> seem to work now. The ports simply don't appear as they should, whatsoever.

Are you using the alsa-backend or the firewire-backend? Only the first supports
what you want. With the firewire-backend you have to use a2jmidid...

> If I can't fix it, I guess I'll just start using a2jmidid instead, but I'd
> prefer to use Jack's internal solution. Any ideas why this might not be
> working, how to fix it, or where to investigate? Thanks!

Have fun,

Arnold
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user


_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux