Skip to content

Multiview second row reflows on Take: an in-show camera-off participant briefly drops from the shell roster #725

Description

@iamfatness

Owner report 2026-09-30 (beta ec70a7b): on every cut, the multiview's second row redraws and moves side to side.

Measured in that session:

  • Every Take dropped the multiview source list from 9 to 8 for one sync (~200 ms). 13 takes in 15 s, all the same.
  • The dropped tile was always CoreVideo Producer (the app's own Zoom user, camera off, show slot 9).
  • The wall reflowed from 5+4 to 4+4 and back.
  • The verbose shell log at the 20:34:53 Take shows mv-resolve: slot9 pid=16790528 resolved=False inside the coalesced structural participant rebuild. About 70 ms later it was resolved=True.
  • So the participant list the shell resolved slots against was missing the producer for one apply.
  • The core's multiviewer.sourceCount is just the size of the list the shell sent; the core is a faithful renderer here.
  • Screen recording frames (2.5 s): the 4-wide reflow and back.

Not reproduced in a fresh session. The app was restarted and rejoined. 12 control-API Takes plus operator UI Takes, with Engine off and on, and with 9 and 10 sources: no dips. The trigger appears to be state that accumulates over a long session (that one had run since 18:12, with roster changes).

Unknown: where the short participant list comes from.

Mitigation and diagnostics: in the linked PR.

Activity

  1. added a commit that references this issue on Oct 1, 2026
  2. iamfatness commented on Oct 1, 2026

    @iamfatness
    OwnerAuthor

    Root cause found and fixed in #727. After the supervisor respawns the media core, the shell rejected the new core's roster (its epoch restarts at the same process:meeting numbers) and kept the dead core's for the rest of the session; each Take briefly applied the true roster. Reproduced in the test meeting by killing the core, then verified fixed with the same sequence. Details and evidence are in the PR.

  3. added 3 commits that reference this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogRanked in docs/BACKLOG.md

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions