First I have to process the .360 video in GoPro Player. I then use GoThru StreetBuilder on MacOS to sample GoPro MAX .mp4-videos. After GTSB has processed the pictures, I just copy them from the program folder. GTSB lets you set a distance interval between 3 and 7 meters and renames photos with the suffix “selected”.
One downside with GTSB is that it removes all meta-data from the photos, so I have to reconstruct the data through several apps and steps.
I use MetaImage to change date/time based on data from the videos original GPS-data.
Then I use HoudahGeo to import the GoPro video’s GPX-data extracted from GoPro Telemetry Extractor.
Bonus step: I then use Pixelmator Pro and Automator to add a graphic logo to overlay my helmet.
I know that @trekview is working on a process that will make the whole process from video to photos a one-click process.
I’m relying on GoPro max behavior of recording a matching GPS entry for each video frame. GPS time is assumed to be accurate and can be used to match each video frame. If GPS has not been acquired or lost, there will be an invalid/placeholder entry and that image frame is skipped.
I took the time for a bit of clean up of the source code to the .NET app at GitHub - bikeoid/AddExifInfo: Match extracted GPS info to GoPro image files and add to EXIF . I use it with a mishmash of Windows and WSL (Windows Subsystem for Linux) batch files, so I haven’t included those. I think it will build with the Community Edition of Visual Studio, but I can create a binary executable if needed.
Hey @badgerseatfrogs1, did you ever found a solution to your problem?
I would also be interested in a consumer camera that can produce RAW photos at around 0.5 second intervals.