Just tested, no identical frames on 20160323 using a wall socket and 32GB sandisk ultra
The first camera, yes, I tested it indoors, no GPS plugged in, using a Samsung USB power supply that was able to put out a stable 1A (same output as on the provided power supply). Same problem, no matter which MicroSD card I used (see previous post). The second camera, I used only what came in the box with it; didn't want to add any other possible factors to the equation other than "Use it as intended, see if it works." I don't believe it's a power supply issue, since I tested the socket on my car as well, and it's behaving normally.Strange. I think I'll change to the beta9 to investigate if it happens to me.
Did you run it from a wall socket as well?
With the first camera, I personalized the settings when I first got the cam (set the rego number, turned off the G-sensor) and that's it. The second cam, I left at stock settings, as it came in the box. Didn't enter the menus at all. Just plugged it in with the supplied power cord and GPS, and let it run.still something we need to check regardless, there may be a pattern to the problem, a particular combination of menu settings etc that cause it to happen, something like that
Heh... the whole "human eye can only see 24/25 fps" myth is exactly that - a myth. Try telling a professional gamer that there's no detectable difference between 30, 60, and 90fps on a PC, and you'll get your ears chewed off. There's a reason the brand spanking new VR helmets like the Oculus Rift and HTC Vive reject any software that runs below 60fps; motion sickness becomes a real issue otherwise.Offtopic: Our eyes catch about 25 frames per second. But you can see 1 frames dulicate in video file which have 30 frames per second with your naked eyes. Superman![]()
Just trying to address every possible factor that could be contributing to the problem, and given that it's been two cameras that have been sent to me, I really want to make sure it's nothing on my end causing the problem; I'd feel like a right muppet if that was the case. Hence why I want to see if opening someone else's normal file on my computer somehow "corrupts" the file into frame duplication (though I honestly doubt it, the scientist in me always keeps an open mind to all possibilities!).It won't be a problem with your computer, engineers are looking at your samples already
Fair enough, if you're sure that's the case. Let's see how it all goes.It will be a firmware bug, we're looking at it already, we haven't changed any code that would affect it so it's more likely it's in the SDK, will put an update out for it as soon as it's sorted, our firmware is always being worked on, we have constant development cycles anyway so it's just something to add to the current list, things like this are always first priority so the kind of thing we would release an update for first
It will be a firmware bug