Hey! At the moment, failures while writing either the microphone or system audio track are only reported to stderr. The recording UI can continue to indicate a healthy active session, so a user may only learn that a track was incomplete or silent after the meeting has ended and transcription begins.
It would be useful to make the recording state reflect the health of each track as failures occur, and to persist that final status in meta.json. That would give users an immediate warning when a session is degraded while also making incomplete recordings diagnosable and recoverable downstream.
I’d be happy to put together a small, focused change if that aligns with the intended UX
Thank you!
Hey! At the moment, failures while writing either the microphone or system audio track are only reported to
stderr. The recording UI can continue to indicate a healthy active session, so a user may only learn that a track was incomplete or silent after the meeting has ended and transcription begins.It would be useful to make the recording state reflect the health of each track as failures occur, and to persist that final status in
meta.json. That would give users an immediate warning when a session is degraded while also making incomplete recordings diagnosable and recoverable downstream.I’d be happy to put together a small, focused change if that aligns with the intended UX
Thank you!