Skip to content

Choose audio devices during preflight #411

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.

Sign up for GitHub

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

Merged
jserv merged 1 commit into from
Oct 23, 2026
+2,088 −216
Merged

Choose audio devices during preflight #411

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,6 +152,14 @@ it is unavailable or declined; the signed integrity trail and the report record
that neutral condition and why. A recorded interview still requires its camera
before it can start.

Where the browser supports device selection, preflight offers microphone and
output selectors using System default until another device is chosen. Changing
the microphone releases the previous track and requires a fresh sound check;
the selected track is published to the interview. The output selection applies
to test sounds and Jim's voice, is shared with the Meet sidebar, and is
remembered across reloads. A saved output that is no longer listed falls back
to System default.

Candidates can present the interview in Google Meet by sharing the CodeTrial tab
with tab audio enabled. Meet owns the shared tab after that, and face-presence
analysis is disabled for the session. See the
Expand Down
Loading