Upgrade to Gopro 13 + AOI UWL-O3 video underwater settings

[bghazzal]

The left-side clip looks more balanced - seeing this, I'm wondering what would happen if you were to reset the white balance to the sand in the foreground, see how it handles the green hue. Might be too much of a stretch though.
Otherwise did you try shooting this in flat WB/colours as well?
Also it's not clear to me, is there artificial light in the foreground, or is this ambient?

[Nando Diver]

@bghazzal Just artificial light. No ambient light It was a cloudy day

To use flat color, its better to use Native WB also, and do all the grading.

 

After seeing the HLG HDR filming, i think its gone be my Preset of choice...

Edited October 27 by Nando Diver

[Nando Diver]

 

Gopro 13

AIO UWL-03

Divevolk LS50

 

Left Standart SDR - 4K60 Wide 10bit WB AUTO ISO 1600 Natural color

Right HLG HDR - 4K60 Wide 10bit WB AUTO ISO 1600 Natural color

 

No color grading 

 

 

[Nando Diver]

Gopro 13

AIO UWL-03

Divevolk LS50

Left Standart SDR - 5.3K60 Wide 10bit WB 5500K ISO 1600 Natural color

Right HLG HDR - 4K60 Wide 10bit WB 5500K ISO 1600 Natural color

 

No color grading

 

 

[Nando Diver]

The Gopro13 White Balance makes a good job getting the right colors depending of the information captured by the sensor. 

In my opinion, If theres light reflected to the sensor, the colors can be accurate, if theres no lights reflected the Algorithm works with what he has..

 

When theres a change in Temperature/kelvin (light reflected ) the Gopro sensor acts accordingly to his algorithm.

 

See the exemple below with no color grading 

 

The water is Blue in the background when im close to some object

The water is Green when there no light reflect to the sensor 

The water is Blue in the background when im close to some object again.

 

 

 

 

 

 

 

 

 

Edited October 27 by Nando Diver

[Davide DB]

14 hours ago, Nando Diver said:

 

See the exemple below with no color grading

 

This is exactly what everyone want to avoid with video.

 

The solution is already here since a CMOS sensor was invented, from a Gopro to an Alexa 35, and it's called Manual White Balance. That translated In Gopro terms is Native WB or fixed (Kelvin) WB along with flat colors.

Unfortunately for us, there's no free meal.

 

[Nando Diver]

It seems using HLG HDR some Presets don't change, like ISO to 800 (ISO 1600 is mandatory).

ive select WIDE=1 because it seems is using a wider gamut according with what the sensor captures, even using AUTO WB.

 

Gopro Labs Settings for the 13

Video 

Mode preset HDR 

4K 60FPS

Lens WIDE

EIS Autoboost

PROTUNE

depth  10-bit 

bit rate high

shutter Auto 

0EV

Auto WB 

ISO min 100 

ISO max 1600

sharpness medium

color natural

PREFS  

Auto off never 

lcd off never 

 

QR CODE 

 

• DIVE=1 - optimizing the Hypersmooth stabilization for underwater.
• WIDE=1 This offers a color gamut like setting white balance to Native (wider gamut), while enabling auto whitebalance, or user controlled whitebalance. With WIDE off (0 - the default), the camera saturates color to the Rec709 gamut (basically sRGB), so some extreme real-world color saturations are clipped by the gamut. With WIDE=1, the gamut is sensor native, not Rec709, not Rec2020, just what the sensor sees.
•  
• BITR=150 - set the compression in Mb/s for the Protune High Bitrate setting (HEVC only). Normally this would be around 100Mb/s, however higher (or lower) rates may be achieved with newer SD Cards. No guaranteed capture reliability using this feature. Input range in Mb/s from 2 to 200. Counterintuitively, lower frame rates like 24/25/30fps can use higher bitrates than faster frame rates. e.g. A camera that is reliable doing 180Mb/s at 24fps, will likely need to drop to 150Mb/s for 120fps. Most GP2 cameras can do 150Mb/s for all video modes, but your testing is still required. Use at your own risk.

 

 

Edited November 2 by Nando Diver

[Nando Diver]

Gopro labs (optional testing)

 

yesterday ive tried this settings 

 

WBLK=1 don't really lock the white balance, its noticeable a change from blue to green/blue

 

Warm=x i set red to 60….it was too much

 

Cool=x i set the blue to 20, doesn’t make a big difference from using Auto WB…but could be handy to reduce the excess of blue at red sea for example.

 

• WBLK=1 This is an auto lock for balance, it auto white balances until the capture starts. The feature was added for scuba users, as fixed white balance are computed for above water, and while the auto works great in dive scenarios, some prefer a fix white balance per clip.

 

• WARM=x - WARM maybe useful with DIVE, so you can improve the red respond for deeper dives. x range -50 to 100. Reducing or increasing red signal only.
• COOL=x - COOL maybe useful with DIVE, so you can decrease the blue respond for deeper dives. x range -50 to 100. Reducing or increasing blue signal only.

 

[Nando Diver]

Here's two videos comparing the Profile HLG HDR left  VS QRcode Generated right (NO GRADING) 

 

Hypersmooth - Autoboost video LEFT seems more stable than ON video RIGHT

 

Generating a QR code with same settings and applying  Dive=1 + Wide =1 + BITR= 150 it seems it also affects the other profiles.

Dont see any differences in color, and the Bit rate jump for 120Mbit/s (stock FW)  to 144Mbit/s (Gopro labs FW in all profiles including the GP-LOG profile 

 

The profile GP-LOG is 8-bit, SDR and the color space BT.709 

 

 

 

 

 

Edited November 3 by Nando Diver

[Nando Diver]

23 hours ago, Nando Diver said:

Gopro labs (optional testing)

 

yesterday ive tried this settings 

 

WBLK=1 don't really lock the white balance, its noticeable a change from blue to green/blue

 

Warm=x i set red to 60….it was too much

 

Cool=x i set the blue to 20, doesn’t make a big difference from using Auto WB…but could be handy to reduce the excess of blue at red sea for example.

 

 

• WBLK=1 This is an auto lock for balance, it auto white balances until the capture starts. The feature was added for scuba users, as fixed white balance are computed for above water, and while the auto works great in dive scenarios, some prefer a fix white balance per clip.

 

 

• WARM=x - WARM maybe useful with DIVE, so you can improve the red respond for deeper dives. x range -50 to 100. Reducing or increasing red signal only.
• COOL=x - COOL maybe useful with DIVE, so you can decrease the blue respond for deeper dives. x range -50 to 100. Reducing or increasing blue signal only.

 

 

Ignore the above comments (can't edit anymore)  ive had some help in GitHub forum and looks like ive messed up the QRCODE. 

 

Need to try WBLK=1 in the next Dive.

[Nando Diver]

thread moved

 

 

Edited November 4 by Nando Diver