[LAD] Whitespaces in jack client/port names / jack_connect

[Arnold Krille]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20100827/4497b341/attachment.pgp>