Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem programming/using two pedals at the same time #82

Open
zx485 opened this issue May 2, 2023 · 2 comments
Open

Problem programming/using two pedals at the same time #82

zx485 opened this issue May 2, 2023 · 2 comments

Comments

@zx485
Copy link

zx485 commented May 2, 2023

At first, I like to thank you for your efforts and your great program. It made it possible to avoid Windows :-)

I have two pedals (lying around for some years) and now, I was trying to make them work on Kubuntu 22.04. So I connected both to an old USB-1.0 HUB which should be sufficient for that purpose.

Both are shown in lsusb, but I can only program one of them. The other one is kind of ignored. A partial solution was to connect them one after the other to an USB root port and program them one at a time. As a test, I programmed one of them with CTRL-W and the other with CTRL-T.

After reconnecting them to the USB HUB, they both work like programmed, but in footswitch -r only one shows as programmed:

[switch 1]: unconfigured
[switch 2]: l_ctrl+w
[switch 3]: unconfigured

The other one works as programmed, but does not show. Maybe its number is higher than three?
Dunno, so thanks for your input.

Here is my lsusb output:

FootSwitchDevices.txt

@rgerganov
Copy link
Owner

This happens because both pedals have the same vid:pid which is 0c45:7403. Currently there is no way to differentiate between multiple devices with the same vid:pid, sorry.

@zx485
Copy link
Author

zx485 commented May 2, 2023

That's unfortunate. But I suppose/hope that I won't (have to) change the mappings often.
Thank you for your quick reply and your overall effort.

P.S.: Wouldn't it be possible to append the bus:device ID to the vendor:product ID? This way, at least, the settings would be permanent unless the devices are connected to other ports. Or am I missing something?

(You don't have to answer if this would be too complex/breaks something/other.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants