Re: JACK message: ports used in attemped connection are not of the same data type

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

 



On Sun, Oct 24, 2010 at 3:13 PM, Jeremy Jongepier <autostatic@xxxxxxxxx> wrote:

> Problem solved. I have a QjackCtl start-up script for a2jmidid that ran well
> with my other Focusrite card but the Saffire Pro 40 takes longer to
> initialize. What happens now is that a2jmidid comes up before the audio
> ports are created which causes these warnings. I've adapted my start-up
> script to wait until the audio ports come up before starting up a2jmidid.
> Works fine again. Thanks for the pointers everyone.

this problem is caused by apps that look for ports with the
JackPortIsPhysical flag set (or even just the first ports), and never
bother to check the type.
_______________________________________________
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