We have added native Mapillary support for the .360 videos from the GoPro MAX2 camera. This means you don’t need to do any video stitching or other manual steps, you can simply drag the .360 videos from the camera straight to the Mapillary Desktop Uploader (or use mapillary_tools to upload). We take care of extracting the gps and stitching the video for you.
We’ve also updated the help center article with the suggested GoPro MAX2 settings. The GoPro MAX2 is now our recommended consumer 360 camera thanks to its higher resolution, built-in GPS, relatively affordable price, and ease of use with Mapillary (drag & drop). Note that the original GoPro MAX continues to be fully supported as well.
The MAX and MAX2 guide for Mapillary is really good! However, I would like to recommend one change, particularly regarding 360° video recording in the “ Driving Setup” section. Generally speaking, you want to record 25 or 30 fps videos with anti‑flicker (rolling shutter compensation) set to 50 Hz and 60 Hz respectively, rather than 24 fps. The 24 fps mode is basically broken on the MAX(2) cameras because there is really no good way to make anti‑flicker (rolling shutter compensation) work at 50 Hz or 60 Hz (effectively 59.94 Hz). There is no 24 fps specific rolling shutter compensation in these cameras.
By default, 24 fps on these GoPro cameras is NOT true 24 fps but 24÷1.001 ≈ 23.976023976 fps. This causes all sorts of trouble, especially with anti‑flicker (rolling shutter compensation) and video cuts. However, you can enable true 24 fps video stream encoding if you have the GoPro Labs firmware installed and 24HZ=1 configured. Most users will not want or be able to go to these lengths to make such adjustments. GoPro should have fixed the 24 fps mode by design. 24 fps has been the cinematography standard ever since, NOT some 23.976024…something fps. But, it is the GoPro way of doing things, I guess.
The bit rate advantage of 24 fps over 25 fps in video/image quality is completely negligible (in like 99.999% of cases).
Contributors should prefer capturing in 25 fps over 29.97 fps (or 30 fps, as GoPro puts it). And yes, even our NTSC loving friends because 25 fps gives finite fraction timestamps. No other recording speed mode results in finite fraction frame times, not even true 24 fps. 25 fps makes life so much easier for everybody.
Sure, if you capture in 30 fps because you also have other use cases for the same footage then go ahead and do so if you must. But, do not complain if things do not work smoothly for mapping.
Generally yes, you can mix image files from different sources on one SD card, just like with every other file type. SD cards do not care what you put on them, neither do cameras, usually. You can even mix images from different cameras and projection types in one sequence. However, you cannot mix videos with images in the Mapillary upload tools. So, I am not entirely sure what you are aiming at with this question?
However, I would like to recommend one change, particularly regarding 360° video recording in the “
Driving Setup” section. Generally speaking, you want to record 25 or 30 fps videos with anti‑flicker (rolling shutter compensation) set to 50 Hz and 60 Hz respectively, rather than 24 fps. The 24 fps mode is basically broken on the MAX(2) cameras because there is really no good way to make anti‑flicker (rolling shutter compensation) work at 50 Hz or 60 Hz (effectively 59.94 Hz). There is no 24 fps specific rolling shutter compensation in these cameras.
23.976024…something fps. But, it is the GoPro way of doing things, I guess. 
