Register | Login
Attackpoint - performance and training tools for orienteering athletes

Discussion: Camera makes 12 min chunks?...

in: Spike; Spike > 2018-12-15

Dec 17, 2018 3:55 PM # 
Jagge:
Camera makes 12 min chunks? Only first file name was correct?

I wonder would the de-shake option with some black borders make that unavoidable left-right swaying any less disturbing.
Advertisement  
Dec 17, 2018 7:02 PM # 
Spike:
It is an old GoPro and it saves a new file every 12 minutes, so a run of 50 minutes is 5 files. The file names follow a set format. I got the first one correctly, but then mis-spelled the other 4 (mistaking the letter O for the number 0).

I fixed the file names and started the program again. I left it running (mapflixer stabilize) when I left for work this morning.

I'll give the black border option a try. I've been using the first option for stabilize because I don't really like how that black box looks, but it might work a bit better.
Dec 17, 2018 8:14 PM # 
Pink Socks:
What are the specs on your computer?

Your recent posts inspired me to download mapflixer and wear my old GoPro at this weekend's race (45 minutes).

I have a laptop from 2014 with 8MB of RAM and an i7 CPU. Hopefully that's enough to create a movie without waiting too long for it.
Dec 17, 2018 8:46 PM # 
Spike:
I don't remember the specs for my computer, I'll try to remember to check when I get home.

If you play around with mapflixer, I recommend starting with something short - like a 5 minute video on a sprint map. That way if you've got a problem in the configuration file it will show up quicker.

The video function for map.routegadget.net is really easy to use and would be quicker. There's a video demonstrating how it works on the Routegadget Facebook page (I think).

I've been playing around with mapflixer as more of a long-range project. If you just want to compare video to GPS track on a map, the video function for map.routegadget.net is great.
Dec 17, 2018 8:58 PM # 
Jagge:
What it comes to mapflixer, ffmpeg makes most of the work, very little cpu time is used by other tasks. ffmpeg's stabilizer just isn't really that fast.

My laptop is from 2013 and about like that. To make it fast you can bypass stabilization (setting in ini file) and maybe also drop map frame rate from 15 to for example 4 map frame second. That should make 45 min video it finish in about 2 hours. With stabilization it should take maybe 5-6 hours or so - very long time anyway, and laptop cooler pad may make some difference. Map frame rate doesn't make much any difference if stabilization gets done, stabilization doesn't use all cores and map stuff gets done parallel with stabilization.

Please login to add a message.