Take the first frames heading from the telemetry HEAD stream (the World Lock heading).Take the framerate information to compare against cts values in the telemetry to get the right sensor value for each frame.Extract all the frames in the video using ffmpeg.My proposed ffmpeg workflow is as follows I couldn’t find any documentation referencing if the v360 filter supports a time option, so our implementation works by first extracting the frames and applying the filter to them one-by-one.
All that’s needed is to iterate through frames and HEAD values to make the yaw adjustment. It’s easy to align frames to heading values, because we have a HEAD value (heading in degrees) for each frame (with date and cts times) reported in the updated telemetry file. use this value with ffmpeg to adjust yaw.json) - World Lock heading (calculated at step 1) for each frame calculate the yaw adjustment needed using the calculation true heading (reported in telemetry.take the first heading reported in the calculated telemetry file, and assume that as the World Lock heading.To do this, we can take exactly the same approach as I showed you for images in the post Adjusting the yaw of an equirectangular 360 photo using ImageMagick. Now that we have the heading values for each frame in the video ( see last weeks post), we can use them to adjust the yaw in our World Lock video to reverse the effect. Using calculated heading values to ensure videos are shown in 360 players facing the same direction as they were shot.
0 kommentar(er)
