Desktop Recording SDK Adhoc / In-Person Meetings

The Desktop Recording SDK's adhoc / in-person recording mode is useful if you want to record the audio for a meeting outside of a supported meeting platform (e.g. Zoom, Teams, Google Meet). This could either be to capture the audio of an in-person meeting, or to capture the mic and speaker streams of the desktop.

🚧

Given that adhoc and in-person meetings occur outside of a meeting provider, it is not possible to create a diarized transcript or give active speaker timelines in this mode. Instead, the local machine's mic stream will be labelled as "Host". Any other audio stream will be labelled as "Guest".

Enabling adhoc / in-person recordings using the DSDK

To record using the adhoc / in-person recording mode, use the DSDK's prepareDesktopAudioRecording call. This function allows you to obtain a window_id to pass to the DSDK's startRecording call, instead of obtaining the ID from the meeting-detected or meeting-updated event.

Regular recording flow:

1. A meeting starts on a meeting provider
2. The DSDK sends a meeting-detected event, which contains a window ID
3. You pass the window ID to the startRecording function (along with your SDK upload token) to start recording that meeting provider

Adhoc / in-person flow:

1. You call prepareDesktopAudioRecording to obtain a window ID
2. You pass the window ID to the startRecording function (along with your SDK upload token) to start recording the system's Mic and Speaker audio streams.

📘

From a technical perspective, there is no difference between an adhoc recording and an in-person recording. Using the prepareDesktopAudioRecording call will mix and record the audio streams of your system's mic and speaker.

FAQs

Why are speaker labels returned as "host"/"guest"?

The ad-hoc/in-person meeting feature does not provide speaker labels. Instead, the local machine's mic stream will be labelled as "Host". Any other audio stream will be labelled as "Guest".

For example - if you're using this feature to capture audio for an unsupported platform, then the audio picked up by the local machine's mic will be labelled "Host" and the audio from the other participants in the meeting will be labelled "Guest".

If you want the diarized speakers, consider using machine diarization instead.

Why does audio stop if I change my microphone or speaker during a whole-desktop recording?

Whole-desktop recordings bind to the system’s default microphone and speaker when recording starts. Changing audio devices mid-recording is not currently supported and may cause audio capture to stop.