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

MiniDSP 2x4 support? #229

Open
shavenne opened this issue Oct 12, 2021 · 6 comments
Open

MiniDSP 2x4 support? #229

shavenne opened this issue Oct 12, 2021 · 6 comments

Comments

@shavenne
Copy link

shavenne commented Oct 12, 2021

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

@mrene
Copy link
Owner

mrene commented Oct 12, 2021

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?

@shavenne
Copy link
Author

shavenne commented Oct 13, 2021

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. ;)

@mrene
Copy link
Owner

mrene commented Oct 17, 2021

I took a look at that plugin, it looks feasible to support it. Could you check if minidsp probe detects the device? if so what hardware id and dsp version is it reporting?

@shavenne
Copy link
Author

shavenne commented Oct 17, 2021

It doesn't appear. As non-root nothing happens.
With sudo:
[2021-10-17T14:35:51Z ERROR minidsp::transport::multiplexer] recv loop exit: ParseError(EmptyPacket)

When I unplug the MiniDSP and run probe again the message is not appearing anymore so at least it detects something it seems.

@mrene
Copy link
Owner

mrene commented Oct 17, 2021

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.

@fthiery
Copy link

fthiery commented Feb 17, 2022

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) ?

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

3 participants