This script allows videos taken with a Samsung Gear 360 to be stiche and edited using the "PIXPRO 360 VR SUITE" program, used for the KODAK ORBIT360 cameras.
Requirements:
Usage:
.\gear360-to-orbit360.ps1 -input_file <input_file> [-output_file <output_file>] [-metadata_dir_path <metadata_dir_path>] [-ffmpeg_path <ffmpeg_path>] [-mp4edit_path <mp4edit_path>]
Example usage:
.\gear360-to-orbit360.ps1 -input_file .\video.MP4 -metadata_dir_path .\metadata\ -ffmpeg_path .\ffmpeg\ffmpeg.exe -mp4edit_path .\bento4\mp4edit.exe
If no output filename is given, the default output filename will be the same as the input name with _processed appended.
I had an ORBIT360 camera that I really liked. The software provided to stitch the videos together was really simple to use and did most of the things I needed to do. However during a motorcycle roadtrip to the USA the camera crapped out and stopped working. So I got a used Samsung Gear 360 from eBay as a replacement.
I really like the Gear 360 too, but I wasn't satisfied with the options available to stitch the videos, so I found a way to stitch the videos with a software I know and like.
The ORBIT360 inserts some metadata in the MP4 files it generates. If this data is absent from the file, the stitching software refuses to open the file.
This script resizes the video to the same resolution as an ORBIT360 file, It then copies the folloing atom keys and their original values from a source ORBIT360 file into the Gear 360 file:
moov/udta/©fmt: Contains the string "JK Imaging Ltd."moov/udta/©inf: Contains the string "KODAK PIXPRO ORBIT 360 4K"moov/udta/m cm: Not quite sure what this is used formoov/udta/m vr: Not quite sure what this is used formoov/udta/SNum: Seems to contain the serial number of the camera on which the source video was takenmoov/udta/rads: Not quite sure what it does, but if this key is ommited, the software only shows video from one lens