17 Mar
2020
17 Mar
'20
3:52 p.m.
I noticed an oddity when using the aconnect command with names
containing spaces:
aconnect tickle:0 Pure Data:1
surprisingly this works without issues even thouth there is a space ind
the input port name.
the other way round it fails.
aconnect Pure Data:1 tickle:0
invalid destination address Data:1
but using hyphens it works:
aconnect 'Pure Data:1' tickle:0
in the manpage for aconnect two other tools are mentioned:
SEE ALSO
aseqnet(1), aseqview(1)
they are not available in my repositories. Are they deprecated?
m.
17 Mar
17 Mar
4:01 p.m.
Mar 17 2020, Max has written:
...
aconnect tickle:0 Pure Data:1
surprisingly this works without issues even thouth there is a space ind
the input port name.
Probably because the port with the space in it is the last
commandline
argument.
the other way round it fails.
aconnect Pure Data:1 tickle:0
invalid destination address Data:1
In shell spaces have to be quoted/escaped
somehow, because a normal
space means that one argument ends and another begins. To be save:
always quote names with spaces. Not sure if escaping them would work
with backslash, as happens with filenames:
aconnect Pure\ Data:1 tickle:0
...
aseqnet(1), aseqview(1)
they are not available in my repositories. Are they deprecated?
On Archlinux
aseqnet is part of alsa-utils, which is the same as
aconnect. I'm running version 1.2.2 .
aseqview has its own package, which is only available in a user
repository, so might be out of date or rarely used today, due to better
alternatives perhaps.
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* SoundCloud: https://soundcloud.com/jeanette_c
* Twitter: https://twitter.com/jeanette_c_s
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
Just call out my name, and I will be there... <3
(Britney Spears)
4:17 p.m.
On 17.03.20 15:01, Jeanette C. wrote:
It gets weirder. Trying different escaping
$ aconnect tickle:0 'Pure Data':1
Connection failed (Operation not permitted)
$ aconnect tickle:0 'Pure Data:1'
Connection failed (Operation not permitted)
$ aconnect tickle:0 Pure\ Data:1
Connection failed (Operation not permitted)
but, as i wrote before,
$ aconnect tickle:0 Pure Data:1
just works.
aconnect
tickle:0 Pure Data:1
surprisingly this works without issues even thouth there is a space
ind the input port name.
Probably because the port with the space in it is the
last commandline
argument.
4:38 p.m.
Mar 17 2020, Max has written:
...
It gets weirder. Trying different escaping
$ aconnect tickle:0 'Pure Data':1
...
That quotation might not work at all, because you quote only part of the
port name anyway.
Still, have you checked that the ports aren't connected already? That
might be a reason.
I usually use quoting with double quotes, but have also tried single
quotes, as you did, and escaping a space character with a backslash,
which also worked.
Also you say that "Pure Data:1" is an input port. Just, because there
can be confusion with input and output, especially when hardware ports
are involved: will PureData read MIDI from that port into the program?
Normally aconnect complains if you don't sort portnames correctly on the
commandline. First the port that produces MIDI and then the port that
consumes/reads MIDI.
Alternatively: if it is possible for you to use a graphic desktop
environment in this situation, you can find very handy patch bays, which
will take care of all these oddities.
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* SoundCloud: https://soundcloud.com/jeanette_c
* Twitter: https://twitter.com/jeanette_c_s
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
Just call out my name, and I will be there... <3
(Britney Spears)
5:01 p.m.
Am 17.03.20 um 15:17 schrieb Max:
$ aconnect tickle:0 'Pure Data':1
Connection failed (Operation not permitted)
$ aconnect tickle:0 'Pure Data:1'
Connection failed (Operation not permitted)
$ aconnect tickle:0 Pure\ Data:1
Connection failed (Operation not permitted)
Those are all equivalent command lines. They all result in the string
"Pure Data:1" being passed as the second command line argument.
That's unix shell 101 and has nothing to do with aconnect itself.
$ aconnect tickle:0 Pure Data:1
just works.
Look at the acconnect man page:
'The address can be given using the client's name.
% aconnect External:0 Emu8000:1
Then the port 0 of the client matching with the string "External" is
connected to the port 1 of the client matching with the "Emu8000".'
The keyword here is "matching", i.e. you can refer to clients using a
sub-string of their name and that's what's happening in your example.
So you have three command line arguments: "tickle:0", "Pure" and
"Data:1"
The first two cause a connection to be made on their own and the third
is just ignored, AFAICT:
https://git.alsa-project.org/?p=alsa-utils.git;a=blob;f=seq/aconnect/aconne…
Chris
18 Mar
18 Mar
3:02 p.m.
On 17.03.20 15:47, Christopher Arndt wrote:
ok, got it, It's some kind of "smartness" in aconnect which is
obfuscating my user error.
It seems that while software has these ports 0 and 1 like in "Pure
Data:0" for the MIDI sink and "Pure Data:1" for the MIDI source,
For hardware, both sink and source are referred to as the ID 0.
Is that correct?
In my case this it what works:
aconnect "tickle:0" "Pure Data:0"
aconnect "Pure Data:1" "tickle:0"
I also tried with some other MIDI hardware here and it seems to be
consistent with what Korg and AKAI are doing.
m.
$ aconnect
tickle:0 Pure Data:1
just works.
Look at the acconnect man page:
'The address can be given using the client's name.
% aconnect External:0 Emu8000:1
Then the port 0 of the client matching with the string "External" is
connected to the port 1 of the client matching with the "Emu8000".'
The keyword here is "matching", i.e. you can refer to clients using a
sub-string of their name and that's what's happening in your example. 
7:27 p.m.
Aha! Thanks for solving that riddle for me.
Can someone who is on the alsa-devel mailinglist post this bug please?
https://www.alsa-project.org/main/index.php/Bug_Tracking
m.
On 17.03.20 16:31, Clemens Ladisch wrote:
Max wrote:
aconnect tickle:0 Pure Data:1
aconnect ignores the third parameter. (This is a bug.)
It then connect port "tickle:0" to the first port of the client whose
name begins with "Pure", i.e., "Pure Data:0".
Regards,
Clemens
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2040
days inactive
2041
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Christopher Arndt -
Clemens Ladisch -
Jeanette C. -
Max