.

[DennisOlof]

gitup, that is nice, for me not so much of a issue, but it is always a good thing to have more options in the software. The hardware
is good enough, and even gopro has its limitations and problems. But the hardware is just one side, the other side is having
a well working firmware, fixing bugs and other things.

But that takes time, everyone knows that. It is nice that you are working on making the firmware better, some products get released
and then nothing, no bug fixing or anything after that. At least gitup has proved that they do care and want to make the product better.

I have seen enough videos of how good the gitup2 is and will probably order it soon. The deal is that I can not be without gyro stabilization or a LCD screen. And the gopro is to expensive for how much I will use it, and I do hope that gitup team will continue to improve the firmware, make small changes and put in new features of just make it better 🙂

 

[daoust]

24p & 1/48 are OK i believe because is needed for manual exposure and i've seen other people needing it also.

But asking for a histogram is too much for a little action cam IMO, this is not a Sony A6000.

We have to be realistic or developers won't take our suggestions seriously, of course it would be good but i think is too much. Plus, the fastest shutter speed on the Git2 will not allow you to expose properly in the majority of situations, so a histogram would be irrelevant/useless.

well , I don t really know how hard it is to put histogram on this action cam (maybe imposible , I m far from a programmer ) but it is still a valuable tool to use when you have it . There is alot of sugestion that have been ask by some and other don t like it and they ask to remove or modify those upgrade , most of them are more for there personal comodity. A histogram if possible , is a tool that can be use everytime you try to set the good exposure not a personal option like frame rate , special beep sound , led on or off . . .

It is a well know fact that the git2 is not the best for low ligth. . . most of the user for the action cam will always put in 60p mode even if 24p or 30p is more than enougth. By using a 24p mode with the proper shutter speed of 1/48 or 1/50 , the git2 will perform way better than at 60p with 1/120 shutter speed in low ligth situation. With the help of a histograme , it will be easyer to choose the good ISO . That is why the request of 24p mode, the shutter speed option and the Histogram. If Histogram is overkill for the action cam , leave @gitup make the decision by himself no need to tell me I m not realistic in my suggestion , that is the job of @gitup , not YOUR job! I have read your post and you make good coments and for shure you know alot more than me in camera I belive what I ask is a valuable tool that even you would like to have.

 

[Jde]

(copied from general support discussion; seems like it might belong here as it is a firmware enhancement)
@gitup

Duration & Record Interval Firmware Enhancement

In camera-photo mode: Specify duration along with time lapse.
---For instance, take a photo every 1 minute (time lapse) for a total of 30 mins (duration).

Duration might also work with camera-video mode: start recording every 60 mins (time lapse) then record for 5 mins (record interval) for a total of 8 hours (duration).
---This results in 40 mins of video captured over 8 hours! ; well within battery and storage parameters. Think how useful this might be in unattended mode on a tripod or other mount.

With this kind of programming, it might reduce the frustration which sometimes occurs with mounts such as helmet since action could be pre-programmed.
It would be great if this could be added to firmware.

 

[Nigel]

well , I don t really know how hard it is to put histogram on this action cam...

Maybe the software is already there and just needs turning on, but I think that is unlikely. Certainly no harm in asking if you think it would be useful.

I can see a problem though, the screen is not big enough to display a histogram without hiding most of the image and you need to see them both for it to be useful.

 

[daoust]

yes the screen is not really big , but there is alot of way to fix that . one way will be a series of didgits value that replace the graphic from lest to rigth in the black strip at the bottom of the screen. At the far left you have the shadow and far rigth you have the highligth ex: 10-8-6-4-1-1-0-0-0 will be too much shadow , 3-4-2-6-7-6-4-3-1 will be more balanced picture , not to much shadow , not to much highligth , 0-0-1-2-3-4-6-9-10 will be to much highligth. Anyway , there is alot of way to do it IF IT IS A EASY UPGRADE!!!

 

[Nigel]

yes the screen is not really big , but there is alot of way to fix that . one way will be a series of didgits value that replace the graphic from lest to rigth in the black strip at the bottom of the screen. At the far left you have the shadow and far rigth you have the highligth ex: 10-8-6-4-1-1-0-0-0 will be too much shadow , 3-4-2-6-7-6-4-3-1 will be more balanced picture , not to much shadow , not to much highligth , 0-0-1-2-3-4-6-9-10 will be to much highligth. Anyway , there is alot of way to do it IF IT IS A EASY UPGRADE!!!

Nice suggestion, but those of us that use 4:3 aspect ratio may not like that particular idea so much!

 

[gitup]

Just a little report.

I tested FW 1.5 Beta yesterday and "Strong" color is looking great, far better than VIVID. It looks intense but realistic at the same time. I didn't see many differences in other settings, contrast is still "strong", a little overexposed image in general, "too" deep shadows, etc.

New FW looks very promising.

Thanks.

New Beta firmware with contrast option will be released in 2 days.

 

[noisette]

There is the possibility to implement 25p/50p in the future?
And the contrast options can compete with the protune of gopro?

 

[Nigel]

And the contrast options can compete with the protune of gopro?

GoPro Protune does not provide a contrast setting, only:
White Balance,
Colour Profile,
ISO Limit,
Sharpness,
EV compensation.
https://gopro.com/support/articles/advanced-protune-controls-explained

The Git2 has a more advanced custom white balance control giving full RGB adjustment, a similar sharpness adjustment and similar EV setting. The ISO setting is a bit different because it is a manual setting on the Git2 rather than a limit.

That just leaves the "Flat" colour profile which the Git2 does not have, but that is intended for professional film makers who want to mix their GoPro footage in with footage from professional film and video cameras which don't use standard consumer colour profiles. The Git2 always uses standard sRGB colour which is the best way to store detail for display on a standard sRGB monitor or TV unless you intend to make big changes during editing but big changes will inevitably loose detail so are best avoided anyway.

The Git2 contrast setting is not a "flat" colour profile and does not change the colour or saturation. The contrast setting provides High, Normal and Low contrast options, in addition there is a saturation setting with Normal, Strong, Vivid saturation values and the WDR setting which I think effectively gives a gamma boost.

So you seem to have more control on the Git2 than on the GoPro and getting the output as close as possible to the end result in camera should always give the best end result because otherwise detail that you want will get lost during the H264 encoding which they both use, there is not much spare detail stored in H264 so if you store your video with the wrong colour profile then you will loose detail when you convert back to sRGB so that it can be displayed correctly on a standard monitor/TV.

 

[Nigel]

Contrast settings don't show much difference when there is not much contrast!

The animation is a gif and gif files don't have good colour detail even though they are good for showing differences. Here is a full colour jpg version, but not animated since jpg files don't support animations:

 

[Nigel]

Nice!!

Are you reffering to the next beta firmware? I don't have those options.

You posted "I tested FW 1.5 Beta", so you should know if they are in FW 1.5 😕

Everyone has the custom white balance where you set the relative amounts of red, green and blue. The contrast setting is new for V1.5, as is the Colourful (Strong) saturation value.

 

[daoust]

Nice suggestion, but those of us that use 4:3 aspect ratio may not like that particular idea so much!

OSD (on screen display ) when setting the exposure !!! remove after 😉

 

[Nigel]

Firmware 1.5 Beta (GIT2_V1.5B_0422):

• Theres is no full RGB adjustment (Red and Blue channels can be moved/tweaked. Not adjustment for Green yet).
• Theres is no contrast adjustment (No option on the Menu to adjust or choose from).

Hopefully the next Beta has this options. 😉

The red, green and blue are relative, so if you increase both red and blue then you are actually decreasing green while the overall exposure remains constant. At least that is the idea behind an rgb adjustment with only 2 values adjustable. If you have all 3 adjustable then you end up with either incorrect exposure or a system where it is hard to understand what is happening.

When the FW 1.5 beta is released in a day or two, it will have a contrast adjustment. It will get complicated if you discuss pre-release beta versions of the beta too much! Even discussing the "Strong" colour option may become confusing to some people since that option will not exist when they download the new FW and go looking for it!

 

[Nigel]

With the new public beta 1.5 firmware - https://dashcamtalk.com/forum/threads/gitup-git2-support-faq-review.14625/page-88#post-247763

And an image with a lot of contrast- Low, Normal, High in a gif file:

And a jpg version of the High:

 

[nutsey]

FW 1.5 beta 2. WDR ON + Low Contrast vs WDR ON + Normal Contrast (looks darker):

 

[Nigel]

FW 1.5 beta 2. WDR ON + Low Contrast vs WDR ON + Normal Contrast (looks darker):

View attachment 23028

WDR + Low contrast looks good for dashcam use, more testing required...

So is it better than GoPro ProTune?

 

[nutsey]

WDR + Low contrast looks good for dashcam use, more testing required...

Yes, the histogram is not stretched anymore and there are more possibilities for futher video processing.

Don't know about protune, but now it looks almost like my YiMax script for Yi 😉

 

[gitup]

New idea/improvement for the next firmware or the future:

As battery life is not that good, i believe that any measures to save battery is good. For instance, in "Quick Capture" mode, the screen turns ON at starting the recording and it turns OFF after 1 minute (as minimun). When the camera is mounted in a way that the screen is not visible (helmets, chesty, etc.) is not neccesary to have the screen ON for that minute.

I believe that a "10 seconds" auto-sleep mode (to give at OSD a quick view when the screen is visible) or a "screen off" quick capture mode (when the screen is not visible/or it's mounted in a blind spot) would be useful to save that minute of battery.

Just an idea.

Saludos.

I don't think this will make much difference between 10s and 1 min screen off options.
As we tested before, it seems the screen doesn't need much battery even you always keep the screen on.

Anyway, we are making new battery now, wish it will be better than the old one.

 

[actiondan]

Is it possible to add a higher bitrate option to the next firmware release? Even at the highest setting (35mbps) there is still a lot of blocking and artifacts at 1080/60 outdoors. Thanks!

 

[gitup]

I believe that too 🙁 ...as battery life is poor i can not think another way to save some battery. (Maybe i was expecting too much...a guy told that battery life was 131 minutes at 1080@30fps.

The new battery is for the Git2 or the next Git camera?

For Git1/Git2, it can use the new battery.
For next Git camera, it will use different better battery, design is different.