-
Notifications
You must be signed in to change notification settings - Fork 15
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
MiniDSP 2x4 support? #229
Comments
Mostly because nobody showed up with a device and the willingness to put some time into it. I suspect that the work started in #222 will be helpful in getting 2x4 support since it might share protocol similarities with these older-generation devices. There is also the issue of the various different plugins available for that device - I did not look into the details yet, but it could mean having to maintain many different integrations for the 2x4, depending on differences and similarities in their protocol. Which plugin version are you using? |
2waySUBAdv I'm quite surprised that nobody showed up with that. I thought that would be one of the most widely used one. That was the reason why I was afraid that this one is working totally different software-wise. ;) |
I took a look at that plugin, it looks feasible to support it. Could you check if |
It doesn't appear. As non-root nothing happens. When I unplug the MiniDSP and run probe again the message is not appearing anymore so at least it detects something it seems. |
I see, thanks. It appears they added the command to identify the device in later models only, but I can use the lack of support as an indicator - at least. |
I'd be interested too, if i knew i would have taken the bigger one... @shavenne did you find any other alternatives ? The Air-thing is horrid (and could break any day too) ! Anything i could do to help (e.g. provide windows wireshark USB traces) ? |
Hi!
I'm just wondering: Is there any special reason why the 2x4 isn't supported yet?
Can I help somehow as someone who has one but has too little programming experience?
'lsusb -v' output
The text was updated successfully, but these errors were encountered: