26 Aug
2010
26 Aug
'10
11:34 p.m.
Hi,
I have issues with jack client names that contain whitespaces.
Example:
$ jack_connect MPlayer [19079]:out_0 system:playback_2
ERROR [19079]:out_0 not a valid port
Any idea how I can make this work? I tried:
$ jack_connect "MPlayer [19079]:out_0" "system:playback_2"
ERROR MPlayer [19079]:out_0 not a valid port
$ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2'
ERROR MPlayer [19079]:out_0 not a valid port
So I wonder whether spaces in jack client names and ports are even
allowed, since imho jack_connect is a rather fundamental tool, and
either the tool or those clients are broken.
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
26 Aug
26 Aug
11:56 p.m.
On Thursday 26 August 2010 19:34:04 Philipp wrote:
Hi,
I have issues with jack client names that contain whitespaces.
Example:
$ jack_connect MPlayer [19079]:out_0 system:playback_2
ERROR [19079]:out_0 not a valid port
Any idea how I can make this work? I tried:
$ jack_connect "MPlayer [19079]:out_0" "system:playback_2"
ERROR MPlayer [19079]:out_0 not a valid port
$ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2'
ERROR MPlayer [19079]:out_0 not a valid port
So I wonder whether spaces in jack client names and ports are even
allowed, since imho jack_connect is a rather fundamental tool, and
either the tool or those clients are broken.
Do you need to escape the space?
http://digitaldub.wordpress.com/2009/12/16/linux-audio-session-scripting/
"The backslash in the string USB\ Device:1 is an escape character. When
interpreted on execution, the character following the escape character (here
whitespace, wich happened to be part of the device name listed by aconnect)
will loose its special function as a seperator. An other option would be to
use quoting and write
aconnect 'USB Device':1 aeolus:0
Read more about quoting here if you want."
all the best,
drew
27 Aug
27 Aug
8:52 a.m.
Excerpts from drew Roberts's message of 2010-08-27 01:56:15 +0200:
On Thursday 26 August 2010 19:34:04 Philipp wrote:
Thanks!
Both variants work:
jack_connect MPlayer\ [5818]:out_0 system:playback_1
jack_connect 'MPlayer [5818]':out_0 system:playback_2
But what a pain..
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
Hi,
I have issues with jack client names that contain whitespaces.
Example:
$ jack_connect MPlayer [19079]:out_0 system:playback_2
ERROR [19079]:out_0 not a valid port
Any idea how I can make this work? I tried:
$ jack_connect "MPlayer [19079]:out_0" "system:playback_2"
ERROR MPlayer [19079]:out_0 not a valid port
$ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2'
ERROR MPlayer [19079]:out_0 not a valid port
So I wonder whether spaces in jack client names and ports are even
allowed, since imho jack_connect is a rather fundamental tool, and
either the tool or those clients are broken.
Do you need to escape the space?
http://digitaldub.wordpress.com/2009/12/16/linux-audio-session-scripting/
"The backslash in the string USB\ Device:1 is an escape character. When
interpreted on execution, the character following the escape character (here
whitespace, wich happened to be part of the device name listed by aconnect)
will loose its special function as a seperator. An other option would be to
use quoting and write
aconnect 'USB Device':1 aeolus:0
Read more about quoting here if you want."
all the best,
drew 
9:16 a.m.
On Friday 27 August 2010 01:34:04 Philipp wrote:
Hi,
I have issues with jack client names that contain whitespaces.
Example:
$ jack_connect MPlayer [19079]:out_0 system:playback_2
ERROR [19079]:out_0 not a valid port
Any idea how I can make this work? I tried:
$ jack_connect "MPlayer [19079]:out_0" "system:playback_2"
ERROR MPlayer [19079]:out_0 not a valid port
$ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2'
ERROR MPlayer [19079]:out_0 not a valid port
So I wonder whether spaces in jack client names and ports are even
allowed, since imho jack_connect is a rather fundamental tool, and
either the tool or those clients are broken.
Yes, spaces in client and port names are allowed.
Yes, some clients have problems with that (jconvolver comes to mind). Buts its
the clients that need fixing there.
Yes, on the commandline you need to quote the spaces so they count as one
argument. But that is the case for every commandline tool when an argument
with spaces shouldn't be devided in two arguments.
Have fun,
Arnold
9:27 a.m.
Excerpts from Arnold Krille's message of 2010-08-27 11:16:43 +0200:
On Friday 27 August 2010 01:34:04 Philipp wrote:
Thanks.
It's just a pain for me because I use a jack_lsp -c / jack_connect
equivalent in my program, and now need to add a bunch of parsing /
string manipulation stuff to handle those few clients that use spaces.
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
Hi,
I have issues with jack client names that contain whitespaces.
Example:
$ jack_connect MPlayer [19079]:out_0 system:playback_2
ERROR [19079]:out_0 not a valid port
Any idea how I can make this work? I tried:
$ jack_connect "MPlayer [19079]:out_0" "system:playback_2"
ERROR MPlayer [19079]:out_0 not a valid port
$ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2'
ERROR MPlayer [19079]:out_0 not a valid port
So I wonder whether spaces in jack client names and ports are even
allowed, since imho jack_connect is a rather fundamental tool, and
either the tool or those clients are broken.
Yes, spaces in client and port names are allowed.
Yes, some clients have problems with that (jconvolver comes to mind). Buts its
the clients that need fixing there.
Yes, on the commandline you need to quote the spaces so they count as one
argument. But that is the case for every commandline tool when an argument
with spaces shouldn't be devided in two arguments.
Have fun,
Arnold
4997
days inactive
4998
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Arnold Krille -
drew Roberts -
Philipp -
Philipp Überbacher