These might be appropriate for a different repo. I'm logging them here as "most likely repo" thanks to Dmitri's CCG sleuthing. Feel free to move or copy them to other repos. Please tag me if you do so, so I can track updates.
These probably need to be handled distinctly, but they're intimately connected so I'm raising one issue for both.
1. transcriber fails mid-meeting
Historically, this was handled by stopping and restarting the recording, but apparently that resulted in overwriting the existing recording (up to "now") with the new recording (starting "now"), so the earlier part of the meeting was lost.
This could be partially handled by naming the recording file with DATETIME instead of just DATE, perhaps rounding to the minute (dropping seconds and fractions thereof). That would make the admin functions a bit more challenging, but would at least keep as much recording as the day's chair was able to capture with timely re-starts.
After-meeting post-processing of the recording to generate a transcript could then be used against all the audio files, hopefully resulting in something more complete than the mid-meeting failure delivers.
2. transcriber doesn't hear some speakers
This is an ongoing problem, which might be related to browser-specific issues on the speaker's side, but the speaker isn't always able to drop-and-reconnect or to change browsers.
This would be less of an issue if the recording is complete, or if the post-processing described above can be run (assuming the recording captures all speakers, even when the transcriber doesn't), but it's still problematic during the meeting.
These might be appropriate for a different repo. I'm logging them here as "most likely repo" thanks to Dmitri's CCG sleuthing. Feel free to move or copy them to other repos. Please tag me if you do so, so I can track updates.
These probably need to be handled distinctly, but they're intimately connected so I'm raising one issue for both.
1. transcriber fails mid-meeting
Historically, this was handled by stopping and restarting the recording, but apparently that resulted in overwriting the existing recording (up to "now") with the new recording (starting "now"), so the earlier part of the meeting was lost.
This could be partially handled by naming the recording file with DATETIME instead of just DATE, perhaps rounding to the minute (dropping seconds and fractions thereof). That would make the admin functions a bit more challenging, but would at least keep as much recording as the day's chair was able to capture with timely re-starts.
After-meeting post-processing of the recording to generate a transcript could then be used against all the audio files, hopefully resulting in something more complete than the mid-meeting failure delivers.
2. transcriber doesn't hear some speakers
This is an ongoing problem, which might be related to browser-specific issues on the speaker's side, but the speaker isn't always able to drop-and-reconnect or to change browsers.
This would be less of an issue if the recording is complete, or if the post-processing described above can be run (assuming the recording captures all speakers, even when the transcriber doesn't), but it's still problematic during the meeting.