To a regular person who doesn't care about the technical difference between lowering the frame rate and frame doubling, the visual effect is the same.some cameras maintain the frame rate so that there is no change in speed but then repeat every frame, different way to tackle the same problem
To a regular person who doesn't care about the technical difference between lowering the frame rate and frame doubling, the visual effect is the same.
But from a technical viewpoint, frame doubling is much easier to do on the fly compared to changing the frame rate on the fly. In fact a lot of video players probably can't handle a file that has a variable frame rate.
If the exposure time drops below 1/60th second then the next frame is simply not ready in time to be recorded so it has to duplicate the previous frame. The only way it can keep 60 fps is to ensure that it never uses an exposure time longer than 1/60th, but if it does then the image will become dark. I think most people think it will only become a little dark because they are used to having auto exposure in both the camera and their eyes, in reality it will quickly become very dark and dropping to 30fps is probably the best option.Older than the black thread.
Does anybody knows why the Git2 can not keep the 60fps stable?
That's what many people has asked and it still unanswered. I can live with the drop to 30 but it would be nice to have that question answered.
ISO is real, I think that article is confusing people by separating the light sensor and amplifier components within the sensor. ISO works in different ways in different sensors and may, or may not affect the light sensors themselves, but in all cases turning the ISO up increases the level of the data coming out of the sensor just as it increased the transparency of analogue film. It is a measure of the sensitivity of the sensor.There isn't a higher ISO equivalent. Since there's no shutter, ISO isn't a real thing in this (or most) digital camera...
People complain about loosing sharpness in low light more than they complain about dropping to 30 fps so while making use of the maximum ISO would solve one problem it would make the overall situation worse.I think this issue would be solved allowing the camera to go as high as needed in the ISO scale. I believe the camera is programmed (FW) to lower the fps rate instead of going to a higher step in ISO to avoid a super grainy 60fps image.
Then, the "problem" is that there isn't a higher iso step on the Git2, or it is available, but is avoided to preserve image quality.
I'm just guessing.
Gyro Stabilisation works fine at night on the Git2: http://www.pinkbike.com/video/445451/I dont even know the IS that seem to work so nice in the daytime, do it still work in low light situations, or do it need to have clearly defined borders of the frame to work ?
Gyro Stabilisation works fine at night on the Git2: http://www.pinkbike.com/video/445451/
I agree with Nigel, even with the lens covered up and you shake the camera you can see it trying to stabilize the image. I saw it when the lens was covered in snow after crashing my quadcopter.I dont even know the IS that seem to work so nice in the daytime, do it still work in low light situations, or do it need to have clearly defined borders of the frame to work ?
This depends on the SDK, I don't think Novatek will change this, we did checking this with them before.Can Gitup reply whether it's possible to have a mode for low light (so frame doubling), and turning it off (constant 60 fps)?
What I find jarring is when you enter a dark area such as a tunnel or forest for a short while and the Git2 already starts to frame double - to me it's very annoying.
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
L | Slow motion effect | Git2 | 0 | |
S | Upgraded to 1.4 - VERY slow boot up | Git2 | 4 |
Similar threads |
---|
Slow motion effect |
Upgraded to 1.4 - VERY slow boot up |