23 Oct
2010
23 Oct
'10
6:36 p.m.
Dear all,
Anybody any clue what the following JACK message means?
"ports used in attemped connection are not of the same data type"
JACK 0.118.0
Ubuntu 10.04 64bits
FFADO from svn trunk (2.999.0)
Focusrite Saffire Pro 40
This is the first time I encounter this message, didn't see this on the
other 64bits machine where I used this soundcard.
Thanks in advance,
Jeremy
23 Oct
23 Oct
7:51 p.m.
On Sat, Oct 23, 2010 at 12:36 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
Dear all,
Anybody any clue what the following JACK message means?
"ports used in attemped connection are not of the same data type"
since JACK has only 2 data types at present, it implies that you were
trying to connect audio & MIDI ports.
24 Oct
24 Oct
1:10 p.m.
On 10/23/2010 07:51 PM, Paul Davis wrote:
On Sat, Oct 23, 2010 at 12:36 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
Hello Paul,
That is the point, I wasn't doing that deliberately. This message
appears with practically every audio connection I try to make. And I'm
using QjackCtl which doesn't allow for making that kind of connections
afaik.
But at least I know what it means, thanks (pretty straighttforward
though, should've figured it out myself). And indeed, easy to reproduce
on the command line:
jack_connect system:capture_1 yoshimi:midi\ in
Results in a "ports used in attemped connection are not of the same data
type" message (with a little typo). Now my question remains why it appears.
Best,
Jeremy
Dear all,
Anybody any clue what the following JACK message means?
"ports used in attemped connection are not of the same data type"
since JACK has only 2 data types at present, it implies that you were
trying to connect audio& MIDI ports. 
6:37 p.m.
Jeremy Jongepier wrote:
On 10/23/2010 07:51 PM, Paul Davis wrote:
I have 2 USB audio devices - one a USB sound card, the other a MIDI
connection. Sometimes JACKDMP 1.9.2 insists on trying to use the MIDI
device as an audio OUT port.
I don't know why. Usually goes away if I leave the MIDI connection
unplugged when I start the computer up, or simply tell QJackCtl to use
the appropriate hardware-numbered port. But it could be related to the
fact that sometimes the built-in Intel audio chip appears, and sometimes
it doesn't!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
On Sat, Oct 23, 2010 at 12:36 PM, Jeremy
Jongepier
<jeremy(a)autostatic.com> wrote:
Hello Paul,
That is the point, I wasn't doing that deliberately. This message
appears with practically every audio connection I try to make. And I'm
using QjackCtl which doesn't allow for making that kind of connections
afaik.
But at least I know what it means, thanks (pretty straighttforward
though, should've figured it out myself). And indeed, easy to reproduce
on the command line:
jack_connect system:capture_1 yoshimi:midi\ in
Results in a "ports used in attemped connection are not of the same data
type" message (with a little typo). Now my question remains why it appears. Dear all,
Anybody any clue what the following JACK message means?
"ports used in attemped connection are not of the same data type"
since JACK has only 2 data types at present, it implies that you were
trying to connect audio& MIDI ports.
9:13 p.m.
On 10/24/2010 01:10 PM, Jeremy Jongepier wrote:
On 10/23/2010 07:51 PM, Paul Davis 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.
Best,
Jeremy
On Sat, Oct 23, 2010 at 12:36 PM, Jeremy
Jongepier
<jeremy(a)autostatic.com> wrote:
Hello Paul,
That is the point, I wasn't doing that deliberately. This message
appears with practically every audio connection I try to make. And I'm
using QjackCtl which doesn't allow for making that kind of connections
afaik.
But at least I know what it means, thanks (pretty straighttforward
though, should've figured it out myself). And indeed, easy to reproduce
on the command line:
jack_connect system:capture_1 yoshimi:midi\ in
Results in a "ports used in attemped connection are not of the same data
type" message (with a little typo). Now my question remains why it appears.
Best,
Jeremy Dear all,
Anybody any clue what the following JACK message means?
"ports used in attemped connection are not of the same data type"
since JACK has only 2 data types at present, it implies that you were
trying to connect audio& MIDI ports.
11:37 p.m.
On Sun, Oct 24, 2010 at 3:13 PM, Jeremy Jongepier <autostatic(a)gmail.com> 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.
5219
days inactive
5220
days old
linux-audio-user@lists.linuxaudio.org
5 comments
4 participants
participants (4)
-
david -
Jeremy Jongepier -
Jeremy Jongepier -
Paul Davis