Repository navigation
fix(audeze): remove parameter-setting packet from Maxwell initialization - #577
Merged
Merged
Conversation
fix(audeze): remove packet from Maxwell 2 initialization
8 tasks done
AdrianKuriata
pushed a commit
to AdrianKuriata/HeadsetControl-GUI
that referenced
this pull request
Sep 11, 2026
Released headsetcontrol up to 4.1.0 sends a DSP parameter write on every info read, and the app's 5 s refresh loop would send it constantly against a real Maxwell. The target builds upstream master into .upstream/ and puts it first on PATH; the script refuses to build if the packet ever reappears. Temporary — delete it once Sapd/HeadsetControl#577 is in a release. Claude-Session: https://claude.ai/code/session_01SkTQSQNwRB7RkCXW5coHHc
2 tasks done
6 tasks done
AdrianKuriata
added a commit
to AdrianKuriata/HeadsetControl-GUI
that referenced
this pull request
Oct 16, 2026
* feat(detect): require headsetcontrol 4.1.0 (#67) 4.1.0 carries our upstream #549 and #550, so a parameter write costs 0.07 s instead of 2.90 s on the Maxwell 2. The floor is now a latency one, not a capability one — 4.0.0 works, just slowly — and ADR 0016 records that. Fixtures re-recorded against 4.1.0: api_version is 1.5, a write lists devices but reads no values from them, and the test device gained CAP_SIDETONE_STATUS (rendered in #68). Reads come from a master build on purpose — released 4.1.0 still sends the packet that shifts a Maxwell's audio balance (upstream #577). Install screens offer upstream's PPA/COPR/AUR first, packages second, source last. Claude-Session: https://claude.ai/code/session_01SkTQSQNwRB7RkCXW5coHHc * chore(dev): add make dev-upstream, an Audeze-safe dev run (#67) Released headsetcontrol up to 4.1.0 sends a DSP parameter write on every info read, and the app's 5 s refresh loop would send it constantly against a real Maxwell. The target builds upstream master into .upstream/ and puts it first on PATH; the script refuses to build if the packet ever reappears. Temporary — delete it once Sapd/HeadsetControl#577 is in a release. Claude-Session: https://claude.ai/code/session_01SkTQSQNwRB7RkCXW5coHHc * fix(lint): keep the dev-upstream build out of ESLint and Prettier (#67) CMake writes files named compiler_depend.ts under .upstream/, which the type-aware ESLint run then tries to parse as TypeScript — 34 errors the moment anyone runs make dev-upstream. .gitignore does not reach either tool. Claude-Session: https://claude.ai/code/session_01SkTQSQNwRB7RkCXW5coHHc --------- Co-authored-by: tinker <kuriatadev@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #561
This removes the parameter-setting packet from the initialization sequences of both Audeze Maxwell and Audeze Maxwell 2.
On my original Maxwell (0x3329:0x4b19), the packet caused a persistent left/right audio imbalance after a battery query. After removing it:
Hardware testing was performed on the original Maxwell. I do not have a Maxwell 2 available for hardware testing.