Skip to content

Add server-initiated-volume-curve scenario (#64)#72

Closed
balloob wants to merge 1 commit into
claude/conformance-static-delayfrom
claude/conformance-volume-curve
Closed

Add server-initiated-volume-curve scenario (#64)#72
balloob wants to merge 1 commit into
claude/conformance-static-delayfrom
claude/conformance-volume-curve

Conversation

@balloob
Copy link
Copy Markdown
Collaborator

@balloob balloob commented May 27, 2026

Summary

Notes

Test plan

  • python -m compileall src scripts
  • python -m conformance.cli run --results-dir results --from aiosendspin --to aiosendspin --timeout-seconds 25 shows the new scenario row with the expected fail-fast reason

Adds the volume calibration scenario from #64.
Per the audit, sendspin-go and sendspin-js apply linear `vol/100`
gain instead of the spec's implied `(vol/100)^1.5` perceptual curve.
A multi-room group containing one go/js player and one
rs/SendspinKit/cli player has an audible loudness mismatch at any
volume below 100.

`volume-perceptual-curve` is declared on the aiosendspin server only.
Every client case fails fast until each adapter declares the
capability based on the SDK's exposed surface.
@balloob
Copy link
Copy Markdown
Collaborator Author

balloob commented May 27, 2026

Closing per discussion in #68 — dropping scaffolding-only scenarios in favor of real end-to-end tests as SDK surface lands.

@balloob balloob closed this May 27, 2026
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

Successfully merging this pull request may close these issues.

1 participant