You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, apparently the stream handler_name has changed again in Hero6 files. And that makes automated data extraction difficult for those of us who use ffmpeg. If I'm not wrong, for Hero5 files up to 60 fps, it was something like
So they can be retrieved with the 0:3 of the H5 sub 60fps command, but not with the previously universal 0:m:handler_name:" GoPro MET" and 0:m:handler_name:"GoPro MET" does not work either for some reason I don't comprehend.
Does anyone know how to solve this? Maybe using regular expressions or looking for the "(gpmd / 0x646D7067)" bit?
The text was updated successfully, but these errors were encountered:
I wonder what the most cross-platform solution would be, perhaps a perl or python script rather than a bash or batch script? I don't run windows, does it ship with another cross-platform scripting language?
So, apparently the stream handler_name has changed again in Hero6 files. And that makes automated data extraction difficult for those of us who use ffmpeg. If I'm not wrong, for Hero5 files up to 60 fps, it was something like
Which could be extracted via
ffmpeg -y -i VIDEOFILE.MP4 -codec copy -map 0:3 -f rawvideo DATA.BIN
Then, over 60 fps the Stream was:
So this call, despite the awkward tabulator character before "GoPro MET" would work for both:
ffmpeg -y -i VIDEOFILE.MP4 -codec copy -map 0:m:handler_name:" GoPro MET" -f rawvideo DATA.BIN
Now, Hero6 files don't have the tabulator character:
So they can be retrieved with the 0:3 of the H5 sub 60fps command, but not with the previously universal
0:m:handler_name:" GoPro MET"
and0:m:handler_name:"GoPro MET"
does not work either for some reason I don't comprehend.Does anyone know how to solve this? Maybe using regular expressions or looking for the "(gpmd / 0x646D7067)" bit?
The text was updated successfully, but these errors were encountered: