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

Excerpts from Arnold Krille's message of 2010-08-27 11:16:43 +0200:
> 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

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
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev