Hi everybody!
I have switched just now from the default MIDI on my old system to alsa MIDI with my new system Debian 3.5.
I have made myself some monitoring of the /dev folder to tell me when a new midi device gets connected.
Then I check the input with aconnect -i for getting the client and port number to connect it automatically to Pd.
This works great!
However, I'm having a problem with devices that show up as the same client with the same port number.
For example the EWI-USB and the Panda-Audio midiBeam both show up as client 32:0.
On my old system (Ubuntu 11.10) both would be listed and I could differentiate them by their name.
So I could connect one to Pd MIDI In 1 and the other to Pd MIDI In 2.
Unfortunately on Debian 3.5 only one of them gets listed for each client:port number.
The other one deosn't even show up. I think it's the one that was connected first that works. The 2nd one is being ignored.
Does anybody know a workaround for this?
Is there a file where I can change client or port numbers for specific devices maybe by the PID / VID ?
Thank you!
Ingo
On 05.02.19 09:49, Ingo wrote:
I have switched just now from the default MIDI on my old system to alsa MIDI with my new system Debian 3.5.
welcome to the year 2019. Debian 3.1 was released in 2005, support ended in 2008. Debian 4.0 was released in 2007, support ended in 2010. so i guess you somehow timewarped by a decade.
For example the EWI-USB and the Panda-Audio midiBeam both show up as client 32:0.
now that's a serious problem. imu, the client number is supposed to identify the device. if two devices share the same number, they cannot be uniquely identified. period.
On my old system (Ubuntu 11.10) both would be listed and I could differentiate them by their name.
with the same client ID?
Does anybody know a workaround for this?
does qjackctl show both devices? if so, you could try to use that for the connection management.
are you using my [aconnect] external, or the aconnect cmdline utility?
(the manpage of the latter says, that you can specify clients by name)
fgamsdr IOhannes
welcome to the year 2019. Debian 3.1 was released in 2005, support ended in 2008. Debian 4.0 was released in 2007, support ended in 2010. so i guess you somehow timewarped by a decade.
Sorry, of course that was meant to be Debian 9.5.
For example the EWI-USB and the Panda-Audio midiBeam both show up as client 32:0.
now that's a serious problem. imu, the client number is supposed to identify the device. if two devices share the same number, they cannot be uniquely identified. period.
On my old system (Ubuntu 11.10) both would be listed and I could differentiate them by their name.
with the same client ID?
YES! Both of them show up when sending aconnect -i to a shell in my old Ubuntu but not in the current Debian. Then I could specify the correct one by selcting the name with a route object and connect each one individually to a different port. This obviously won't work anymore if the OS doesn't recognize both of them.
Does anybody know a workaround for this?
does qjackctl show both devices? if so, you could try to use that for the connection management.
Unfortunately I don't have qjackctl installed ... :-(
are you using my [aconnect] external, or the
aconnectcmdline utility? (the manpage of the latter says, that you can specify clients by name)
I didn't know about that external. Which library is it in? So far I had been using shell for finding the client id and connecting it to Pd. Maybe your external does a better job with my scenario. It's definitely worth giving it a try.
Ingo
On Tue, 2019-02-05 at 13:57 +0100, Ingo wrote:
does qjackctl show both devices? if so, you could try to use that for the connection management.
Unfortunately I don't have qjackctl installed ... :-(
Fortunately, it's free software and can be installed with 'apt installed qjackctl' on a Debian-like system ... :-)
Roman
On Tue, 2019-02-05 at 14:47 +0100, Roman Haefeli wrote:
On Tue, 2019-02-05 at 13:57 +0100, Ingo wrote:
does qjackctl show both devices? if so, you could try to use that for the connection management.
Unfortunately I don't have qjackctl installed ... :-(
Fortunately, it's free software and can be installed with 'apt installed qjackctl' on a Debian-like system ... :-)
argh.. should read:
apt install qjackctl
Roman
I know it's easy to install but I have a "closed" operating system that cannot be changed that easily anymore. It's a "hardware" style device that's out with quite a few people already. Updating the operating system is not an option for any kind of a short term solution.
Ingo
-----Original Message----- From: Pd-list [mailto:pd-list-bounces@lists.iem.at] On Behalf Of Roman Haefeli Sent: Tuesday, February 05, 2019 2:47 PM To: pd-list@lists.iem.at Subject: Re: [PD] aconnect midi devices with identical client and port numbers
On Tue, 2019-02-05 at 13:57 +0100, Ingo wrote:
does qjackctl show both devices? if so, you could try to use that for the connection management.
Unfortunately I don't have qjackctl installed ... :-(
Fortunately, it's free software and can be installed with 'apt installed qjackctl' on a Debian-like system ... :-)
Roman
On Tue, 2019-02-05 at 16:53 +0100, Ingo wrote:
I know it's easy to install but I have a "closed" operating system that cannot be changed that easily anymore. It's a "hardware" style device that's out with quite a few people already. Updating the operating system is not an option for any kind of a short term solution.
Ah, sorry - was missing that context.
Roman
On 05.02.19 13:57, Ingo wrote:
are you using my [aconnect] external, or the
aconnectcmdline utility? (the manpage of the latter says, that you can specify clients by name)I didn't know about that external. Which library is it in?
it used to be a standalone "library" with a single [aconnect] object. i haven't looked at it in ages.
So far I had been using shell for finding the client id and connecting it to Pd. Maybe your external does a better job with my scenario. It's definitely worth giving it a try.
i don't think it will do any better job regarding your actual problem (rather the opposite).
it might integrate better into Pd, though.
gfmasdr IOhannes
- IOhannes m zmoelnig zmoelnig@iem.at [2019-02-05 15:02]:
On 05.02.19 13:57, Ingo wrote:
are you using my [aconnect] external, or the
aconnectcmdline utility? (the manpage of the latter says, that you can specify clients by name)I didn't know about that external. Which library is it in?
it used to be a standalone "library" with a single [aconnect] object. i haven't looked at it in ages.
So far I had been using shell for finding the client id and connecting it to Pd. Maybe your external does a better job with my scenario. It's definitely worth giving it a try.
I was trying to get such a thing to work with pdreceive as asked on this list a while ago https://lists.puredata.info/pipermail/pd-list/2019-01/124326.html but did not find out how and did not get any replies (yet). Perhaps this is a good occasion to ask again? ;)
-
Ingo -
IOhannes m zmoelnig -
Peter P. -
Roman Haefeli