Repository navigation
spec(t27f): frame_render -- display list ops to PPM frames, the M6 render harness (refs #11781, #10265) - #11816
Merged
Merged
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The missing M6 piece between export_video.t27's records and the mp4: a pure rasterizer for the display list ops into PPM frames at the export presets (1920x1080 / 1080x1920), plus the P6 writer -- ffmpeg consumes PPM sequences directly, so the lab driver loops
frame_bytesthrough ffmpeg with no other new plumbing.NOT CLAIMED: stroke/text/image/clip rendering, scale (needs a display_list encoding change), PNG, the ffmpeg invocation and the MP4 -- the lab loops frame_bytes at the presets for k in 0..899; LAB_RUN_DONE stays false until that dispatch.
phi^2 + 1/phi^2 = 3 | TRINITY