-
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
Add support for more products #105
Conversation
Hello, if I can assist with either the 4x10HD (2x8) or the OpenDRC (4x8) please let me know what you need. |
Thank you! I'm going to finish tweaking the verbose output so that it gives you human-readable addresses. Then it should be a matter of opening the plugin app and taking notes about what does what. |
@professorpolymath question regarding the minisharc:
|
Thanks. I must not have recognized the name of that value. The last commit pushes what's needed in order to gather information about the devices. I've extracted all the addresses (from the xml config) through some custom code generating a list of symbols. Most of the configuration is handled through these and go through the same command with a changing address. Reading values from the device also uses that same address space, but since devices don't allow reading back the config, they all read zeros unless they report some audio levels (like input/output gain and compressor feedback). There is some logic in how these symbols are used for, what I'm looking for first is confirmation that I have done the right mapping for the miniSHARC (because the symbols were very similar to the 2x4HD). The only part I'm really missing is the compressor feedback, which should you should see flying by the console when viewing the UI you've shown me in the screenshot. For the 4x10 I think we'll need to change each param and take note of what does what. Since there is some logic involved I'd start by doing it for one input and one output channel, so we can see the pattern and then confirm it's the same for the rest of the channels. Gathering infoGrab the latest build from this branch (at the bottom of this page). Confirm that
Start the server component with verbosity on ( Connect to the server component with the official plugin app, you'll see a bunch of things:
In that example, we can associate the mute of input channel 0 to minidsp-rs/protocol/src/device/m2x4hd.rs Lines 357 to 366 in 54e6200
Here is the same file but for the minisharc: minidsp-rs/protocol/src/device/msharc4x8.rs Lines 811 to 822 in 54e6200
These are all generated, so we're looking for the logic so we can write something like this: minidsp-rs/devtools/src/codegen/msharc4x8/mod.rs Lines 22 to 31 in 54e6200
Well that was a bit of a long post, let me know what I missed that isn't obvious 😅 |
miniSharc plugin open to output tab.
|
miniSharc -- while plugin running, muting the four inputs in turn
|
Ah great. I've adjusted the device spec for the msharc4x8. |
Starting to gather the requirements for multiple devices.
Aiming to support:
Todos: