I have just obtained a GoPro Max and have done some preliminary capture to 360 photos with the recommended Time Lapse / 2 second interval settings.
However I see a similar 360 time lapse video at a 0.5 second interval. Is it feasible to extract the images and upload to Mapillary with the processing scripts? The resolution appears to be a bit lower than the in-camera stitching, but should be usable. I would think it would be better to use the 0.5 second interval on bicycle for example.
I did some experimenting with the 360 video/time lapse at 0.5 second interval. I was able to convert the video to equirectangular format with the GoPro app, then extract the images, GPX, and insert EXIF information to match the 360 photo/time lapse mode.
I don’t know the advantages or disadvantages of this mode yet, but it’s interesting to see that the GoPro app export has an option to perform horizon leveling.
Can you share the exact timelapse settings you used?
Was this timewarp or timelapse?
https://guides.trekview.org/trek-pack/v2/kit-setup#shooting-modes
The setting was to start with the exact same mode as above: 360 Time Lapse, format = photo.
Then change the format to video and it will allow selecting 0.5s interval under time lapse.
I’m guessing that it can perform faster and achieve 0.5s because it doesn’t have to do in-camera stitching. I’m also guessing that the later conversion to a standard H.264 format with the GoPro app might lose a bit of resolution (5760x2880 to 4096x2048). I haven’t been able to do tests with a bike yet, but I’m hoping that the side view has minimal resolution loss from motion blur.
I’d suggest converting the interim jpg photos back to H264 video is going to lower the image quality too. Video codecs rely on the brain integrating multiple images, so they can afford to be of less quality to reduce filesize.
The 360 Timelapse / Video @ 0.5sec produces a GoPro format .360 video file, which I couldn’t get FFMPEG to recognize directly and create the proper spherical image files extract. So it was the .360 video file that I was converting to H.264 format video. That may work in the future if someone integrates the GoPro codec logic into FFMPEG.
I finally have a processing chain for the time lapse video. It’s very clumsy and I was too lazy to write part of it in Python so it includes a Windows executable in DotNet. In a quick test, I didn’t have a proper mount - just a tripod in a backpack so the whole sequence was tilted. I prefer the video because of the built in horizon leveling if nothing else.