There were still repeated frames, or frames that didn’t have any temporal changes. This created another intermediate that was technically 30FPS but not temporally. Because the original capture didn’t have a consistent frame rate, using nearest neighbour was all that was needed. The second stage was to create a 30FPS project to create a 30FPS intermediate. So the first process was to make a project to create an intermediate that was 4K UHD 2.4:1 which 1:1 pixel matched the 2.4:1 live content area of the 16:9 capture and the full frame 16:9 elements where centre cropped/re-framed to 2.4:1 Creating a 2.4:1 master also helped for further processing time and file sizes by getting rid of the redundant black data (letterbox bars). The original capture uses a mixture of 2.4:1 within 16:9 and also full frame 16:9. I ran through different processes and projects for each stage of the processing, using Resolve’s functions for reframing, re-timing using various methods including optical flow and then the upscaling using super scaling to create my intermediates and final master. So basically there are a lot of repeated frames in the gameplay and capture, it’s basically 30FPS within 59.94FPS but there are drops to about 25FPS during the demo, so it’s not even a consistent 30FPS. Although captured at 59.94 because this is the frame rate of the HDMI output if the Xbox, the frame rate of the demo is maximum 30FPS. The Matrix Awakens demo and gameplay was captured from my Xbox Series X at 4K 60FPS, or to be more precise, 4K UHD 3840x2160 at 59.94FPS.
This video was done as an exercise to test the video processing ability between the M1 Max MacBook Pro and DaVinci Resolve. The Matrix Awakens upscaled to 8K & frame rate converted to 60FPS using DaVinci Resolve & M1 Max MacBook Pro. Below is the blurb from the YouTube description. This is an example of an exorcise testing re-framing, re-scaling and frame rate conversion.
Still learning some of the functions in Resolve.
0 kommentar(er)
