Git2 settings?

[Alexeliasson]

Hi,

This is my first actioncam so I would love some advice.

I'm gonna spin it in 1080/60 and disable awd.

Will Gyro impact the performance/picture in any way, if so - how? I wonder why gyro is a option really, if it doesn't have any drawbacks.

Bitrate High

Any other things I should choose?

 

[Nigel]

Hi,

This is my first actioncam so I would love some advice.

I'm gonna spin it in 1080/60 and disable awd.

Will Gyro impact the performance/picture in any way, if so - how? I wonder why gyro is a option really, if it doesn't have any drawbacks.

Bitrate High

Any other things I should choose?

1080/60 is the best mode for the Git2.

Gyro doesn't have much impact other than to reduce the field of view a bit and remove the shaking. Sometimes you don't want it, maybe if using it as a dashcam, mounted on a musical instrument or if using it for FPV where you want instant feedback to your flight controls so that you don't crash.

What is "awd" ?

 

[Alexeliasson]

Thanks Should i disable it for regular usage with a stable stick then?

Sorry, meant wdr not awd.

 

[Nigel]

Thanks Should i disable it for regular usage with a stable stick then?

I would leave gyro stabilisation on when used on a gimbal stabiliser, but if you prefer the wider field of view then turn it off since it wont make much difference.

 

[jauling]

Bitrate always high. if you're worried about space, get a 64GB card or higher. I also backup my footage ASAP, which frees card space of course.

I personally always shoot at 1440p, which is 1920 x 1440 @ 30fps. This gives me some room to either crop up or down when I convert to 1920 x 1080 in post. This inherently means that I can't do 60fps, but its a small price to pay. Gosh, if only the git2 could shoot at 1440p @ 60fps

Also, if you are planning on shooting in low light or poor light conditions, stick with 30fps. Latest firmware might do some auto frame rate assistance if you're at 60fps, but I guess you'd need to test it to confirm. I've also heard that the gyro doesn't perform well in poor light, so maybe consider turning it off in those situations. You'll also recover some of the cropping that comes with using the gyro then. Personally, I've been too lazy to turn off the gyro, and I always keep it on, even when I use it with my gimbal... So yea, a bit of personal preference, optimal settings, and laziness

 

[Deleted member 37895]

Bitrate always high. if you're worried about space, get a 64GB card or higher. I also backup my footage ASAP, which frees card space of course.

I personally always shoot at 1440p, which is 1920 x 1440 @ 30fps. This gives me some room to either crop up or down when I convert to 1920 x 1080 in post. This inherently means that I can't do 60fps, but its a small price to pay. Gosh, if only the git2 could shoot at 1440p @ 60fps

Also, if you are planning on shooting in low light or poor light conditions, stick with 30fps. Latest firmware might do some auto frame rate assistance if you're at 60fps, but I guess you'd need to test it to confirm. I've also heard that the gyro doesn't perform well in poor light, so maybe consider turning it off in those situations. You'll also recover some of the cropping that comes with using the gyro then. Personally, I've been too lazy to turn off the gyro, and I always keep it on, even when I use it with my gimbal... So yea, a bit of personal preference, optimal settings, and laziness

Why not 2560x1440?

 

[jauling]

Why not 2560x1440?

1920x1440 is the highest resolution that Git2 can do at 4:3 at a minimum of 30fps. 2560x1440 isn't 4:3, and Git2 can only do 2880x2160 at 24fps. I prefer to shoot in 4:3, so I can adjust the cropping later when I change the aspect ratio to 16:9 or 1920x1080. This way, I can either pan up or down or center, depending on what's more interesting. Also means I don't have to worry too much if my Git2 is up/down centered since the 4:3 framing captures a bit more. Hope this makes sense?

Too bad Git2 doesn't have built-in superview...

 

[Deleted member 37895]

1920x1440 is the highest resolution that Git2 can do at 4:3 at a minimum of 30fps. 2560x1440 isn't 4:3, and Git2 can only do 2880x2160 at 24fps. I prefer to shoot in 4:3, so I can adjust the cropping later when I change the aspect ratio to 16:9 or 1920x1080. This way, I can either pan up or down or center, depending on what's more interesting. Also means I don't have to worry too much if my Git2 is up/down centered since the 4:3 framing captures a bit more. Hope this makes sense?

Too bad Git2 doesn't have built-in superview...

Are you sure about that? Maybe my GIT2P is different and I've only had it a few days but what I've figured out is that 1920x1440 is not actually 4:3, it's 16:9 compressed horizontally to be more square so the pixels are rectangular. 2560x1440 is a 16:9 frame that captures the same area but with square pixels

 

[jauling]

You made me doubt what I wrote.. so I tested it just now

I can confirm that my git2 crops pixels when switching from 4:3 to 16:9.

Tested with these 6 resolutions:
1440x1080, 4:3
1920x1080, 16:9
1920x1440, 4:3
2560x1440, 16:9
2880x2160, 4:3
3840x2160, 16:9

Its most apparent when you compare 1920x1440 and 1920x1080 since the horizontal resolution is constant.

 

[Deleted member 37895]

You made me doubt what I wrote.. so I tested it just now

I can confirm that my git2 crops pixels when switching from 4:3 to 16:9.

Tested with these 6 resolutions:
1440x1080, 4:3
1920x1080, 16:9
1920x1440, 4:3
2560x1440, 16:9
2880x2160, 4:3
3840x2160, 16:9

Its most apparent when you compare 1920x1440 and 1920x1080 since the horizontal resolution is constant.
View attachment 37281
View attachment 37282

Interesting, it must be because of the Panasonic sensor. I guess it reads out differently