Galaxy S5 / GoPro Hero 4 Black Overlay Crash

[gryfon]

Greetings,

Just trying out the LapTimer SW for the first, using a Galaxy S5 and a Hero4 Black GoPro.

One issue I had is that everytime I tried to do an overlay, I had a crash notice where the app said it had to close and asked if I wanted to send a report (which I did). The app would find the GoPro file, indicate which portion of the file was going to be used for the lap, but then fail as soon as the hourglass appeared for the processing.

I was using 1080p @ 120 frames/sec on the GoPro and I was manually moving the file from the GoPro to my laptop and then to my phone, and linking it to the lap. Although I could watch the raw video in LapTimer, I know that the 120 frames/sec files can not be viewed even in the GoPro app.

When I changed the GoPro to 1080p @ 60 frames/sec, I stopped having issues and I have now done a number of overlays with no issues, even when dividing the GoPro file into multiple laps.

Wondering if anyone else has the same issue with frame rates above 60 with the Android/Hero4 combination. I really like the 120 frames/sec for doing slow motion stuff, so it would nice to be able to make it work.

[Harry]

I assume there is some timestamp issue leading to division by zero or similar. LapTimer calculated with hundreds seconds internally, which is good enough for 100 frames per second (i.e. 30 pr 60 fps work), but for 120 there will be situations the frame timestamp resolution is finer than LapTimer's... Just a guess. I'd actually need to check this with a 120 fps video...

- Harry