You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zoom allows recordings to be paused and then resumed. In the backend this appears to be accomplished by stopping the recording, then starting a new one for each section. Unfortunately, these sections are not then concatenated at the end of the overall recording. Instead these are presented as separate files, in the same way that the different recording views are presented. The current code makes the incorrect assumption that each view represents the full recording, and so grabs the first match and ingests this.
Action items:
Find all of the files
Check that they are in order, since it's unclear if Zoom does this
Ingest them all
Trigger a workflow which concatenates them prior to normal processing
Workaround: Encourage your users to not pause the recording, or to start a completely new session.
The text was updated successfully, but these errors were encountered:
I'm not sure, but I think this problem was not caused by pausing the recording but by stopping the recording. Do you want me to test this with "pause recording"?
Pausing the recording leaves you with one recording (four video files obviously), so it's a problem of "stopping" the recording. Which makes sense somehow.
Zoom allows recordings to be paused and then resumed. In the backend this appears to be accomplished by stopping the recording, then starting a new one for each section. Unfortunately, these sections are not then concatenated at the end of the overall recording. Instead these are presented as separate files, in the same way that the different recording views are presented. The current code makes the incorrect assumption that each view represents the full recording, and so grabs the first match and ingests this.
Action items:
Workaround: Encourage your users to not pause the recording, or to start a completely new session.
The text was updated successfully, but these errors were encountered: