-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add parsing for Gopro *.360 format #12
Comments
An easy way to solve this is with the imagemagick python API replicating (and modifying for resolution of our 1/2 resolution data) this bit of work from here:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GoPRO .360 format is weird. Fortunately, David at Trekview did the homework in this 4 part series:
https://www.trekview.org/blog/2021/reverse-engineering-gopro-360-file-format-part-1/
https://www.trekview.org/blog/2021/reverse-engineering-gopro-360-file-format-part-2/
https://www.trekview.org/blog/2021/reverse-engineering-gopro-360-file-format-part-3/
https://www.trekview.org/blog/2021/reverse-engineering-gopro-360-file-format-part-4/
The TL;DR is that it is a cube format already, but split into 2 video channels, with some (36 pixels) overlap between the cube faces in order to allow for blending.
The text was updated successfully, but these errors were encountered: