Closed himynamesdave closed 9 months ago
I can just scale with ffmpeg, I don't want to deal with compiling an external library on install or whatever
@fqrious that's not acceptable, as quality will be lost.
Did you see https://github.com/trek-view/gopro2frames
This is already implemented there
Well, if you insist.
@fqrious this is still happening
https://github.com/trek-view/max2sphere#examples-macos
Have a read of that.
You need to read the input video size (it can be one of two sizes) and apply the correct -w
flag depending on the input
Original spec (below under =====) was to use max2sphere.
We now use ffmpeg #48 (which is fine in theory).
However, the aspect ratio created from the frames is incorrect and not accepted by GSV
Can we resolve this with ffmpeg?
If not, we might have to go back to max2sphere.
https://github.com/trek-view/max2sphere/blob/main/docs/dev-notes.pdf (here output is dependant on input size, and uses custom masks)
Note, using ffmpeg to force aspect ration changes is not acceptable, as it will distort image
======
Processing is broken up into four key parts;
4c Processing - extract GPS from video
Same as 3c: Processing - extract GPS
4c Processing - extracting frames from .360 input
The following command can be used to extract frames from the video;
Where
XXX
= framerate user passes in CLI.Note: if timewarp mode is used, the track numbers are different:
Regular video =
-map 0:0
and-map 0:5
Timewarp video =-map 0:0
and-map 0:4
(not currently supported)4c Processing - turning extracted frames into equirectangular projections using max2sphere
Using max2sphere each frame can be turned into equirectangular frames;
Note,
-w
flag variable (XXXX
), is the same asImageWidth
of extracted frame:For
-m
flag variableYYYY
is equal to number of frames extracted from the video.4c Processing - geotag extracted frames
Same as 3c: Processing - geotag the extracted frames.
Script now continues rest 2c processing (GPS smoothing)