maxsSphere Batch takes raw GoPro .360 frames (two strips of cube map projections encoded as EAC) and converts them to a more widely recognised equirectangular projection.
The max2sphere command line utility should build out of the box on Linux using the simple Makefile provided. The only external dependency is the standard jpeg library (libjpeg), the lib and include directories need to be on the gcc build path. The same applies to MacOS except Xcode and command line tools need to be installed.
$ git clone https://github.com/trek-view/max2sphere
$ make -f Makefile
$ @SYSTEM_PATH/max2sphereWhere @SYSTEM_PATH is full route to repo and max2sphere command, e.g.
/Users/dgreenwood/Documents/repos/trek-view/max2sphere/max2sphereI ran into a few issues with my new Mac with an M1 chop that required a slightly different Makefile (because homebrew directory issues finding installed files, specifically fatal error: 'jpeglib.h' file not found).
To address this, instead use the following Makefile;
$ git clone https://github.com/trek-view/max2sphere
$ cd max2sphere
$ make -f Makefile-MacM1
$ @SYSTEM_PATH/max2sphereAn issue was raised identifying issues with Linux distros. In this case it was due to the Makefile config.
To address this, instead use the following Makefile;
$ git clone https://github.com/trek-view/max2sphere
$ cd max2sphere
$ make -f Makefile-Linux
$ @SYSTEM_PATH/max2sphereThis script is designed to be used with frames.
You will need to first convert a .360 video to frames and then pass the two corresponding frames to the script (2 frames because .360's use 2 video tracks).
You can use ffmpeg to split your .360 video into frames (below at a rate of 1 FPS).
$ ffmpeg -i INPUT.360 -map 0:0 -r 1 -q:v 1 track0/img%d.jpg -map 0:5 -r 1 -q:v 1 track5/img%d.jpgNote: this assumes video tracks are 0:0 and 0:5. If timelapse mode is used, the tracks are different:
-map 0:0 and -map 0:5-map 0:0 and -map 0:4$ max2sphere [options] DIRECTORY_%d/img_%4d.jpgVariables:
The DIRECTORY_%d should contain two %d entries, one for each video track (e.g. DIRECTORY_1 and DIRECTORY_2).
The img_%4 should contain sequentially numbered frames from each track with matching numbers (e.g. DIRECTORY_1/img_1.jpg and DIRECTORY_1/img_2.jpg).
Options:
-w n sets the output image width, default: -1-a n sets antialiasing level, default = 2-o s specify the output filename, default is based on track0 name. If specified then it should contain one %d field for the frame number-n n Start index for the sequence, default: 0-m n End index for the sequence, default: 100000-d enable debug mode, default: offmax2sphere will first look for a lookup table (these are stored in the root directory once the script has successfully run once).
If it finds one it will read it and use it during the current processing run.
If it doesn't find a lookup table (or if the read above fails) it will create one and save it to disk and then use it during the current processing run.
Lookup tables rely on four values: the template number, the output width and height, and the antialising value.
e.g. Template 0, width 5376, height 2688 and antialising of 2.
In the case above where the output image width was autodetermined the lookup table is called 0_5376_2688_2.data
The template refers to the recording mode, the template defines the various geometric values the code needs in order to extract out the parts correctly.
Currently two recording modes are supported. At the top of the max2sphere.c file you will see the line referencing them:
FRAMESPECS template[NTEMPLATE] = {{4096,1344,1376,1344,32,5376},{2272,736,768,736,16,2944}};The lookup table does take almost no time to read, compared to calculating the lookup table. However it does end up taking a decent about of disk space, almost 700MB in this case.
For us, this is acceptable as we only ever have 2 static lookup tables using default settings for 5.6k and 3k videos.
You can download these here:
5-6-video-4096w.data (5.6k)
pip3 install gdown
$ gdown --id 1_kynph90d3ZnaONQNXKCjZzgyMgd-Yfw3k-video-2272w.data (3k)
pip3 install gdown
$ gdown --id 1LjZO_e-yhfMRuTcwkp2aLPQchNvvJwfjSingle image
$ /Users/dgreenwood/max2sphere/max2sphere -w 3072 -n 1 -m 1 -o testframes/3k/single/STITCHED/GS018423_%d.jpg testframes/3k/single/track%d/GS018423_%d.jpgDirectory of images
$ /Users/dgreenwood/max2sphere/max2sphere -w 3072 -n 1 -m 4 -o testframes/3k/directory/STITCHED/GS018423_%d.jpg testframes/3k/directory/track%d/GS018423_%d.jpgSingle image
$ /Users/dgreenwood/max2sphere/max2sphere -w 5376 -n 1 -m 1 -o testframes/5_6k/single/STITCHED/GS018421_%d.jpg testframes/5_6k/single/track%d/GS018421_%d.jpgDirectory of images
$ /Users/dgreenwood/max2sphere/max2sphere -w 5376 -n 1 -m 4 -o testframes/5_6k/directory/STITCHED/GS018421_%d.jpg testframes/5_6k/directory/track%d/GS018421_%d.jpgIf you see the warning:
ReadFrame() - Failed to open "testframes/5_6k/track0/GS018421_11.jpg"It is likely the value for -m used does not match the number of frames in the directories used.
This is not a critical error, and you should find all processed frames.