Skip to content

[players] Display shot frame_in numbering in the frame counter#2108

Open
frankrousseau wants to merge 1 commit into
cgwire:mainfrom
frankrousseau:fix-1936-custom-frame-start
Open

[players] Display shot frame_in numbering in the frame counter#2108
frankrousseau wants to merge 1 commit into
cgwire:mainfrom
frankrousseau:fix-1936-custom-frame-start

Conversation

@frankrousseau

Copy link
Copy Markdown
Contributor

Problems

Solutions

  • The start frame is carried by the shot's existing data.frame_in metadata: a new getEntityFrameStart helper reads it and the players resolve it from the store shot map (task.entity_id in PreviewPlayer, current entity in PlaylistPlayer)
  • The offset is display-only, via an opt-in frameStart prop (default undefined) on PlayerPlaybackBar (frame indicator and total) and VideoProgress (hover frame and handle labels); internal frame math, seeks, annotation frame keys and emitted frame events are untouched, and consumers that do not bind the prop keep the 1-based display

Studios number their frames like DCCs do (first frame = 1001), but the
player frame counter always starts at 1. When the displayed shot carries
a data.frame_in start frame, shift the playback-bar frame indicator and
the progress-bar hover / handle labels so the on-screen numbers match
the production numbering.

The offset is presentation-only: internal frame math, seeks, annotation
frame keys and emitted frame events are untouched. It is carried by an
opt-in frameStart prop on PlayerPlaybackBar and VideoProgress, bound by
PreviewPlayer (task page) and PlaylistPlayer; consumers that do not bind
it keep the 1-based display.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Kitsu review player frame / tc custom start number instead of 0

1 participant