Pixel Format: 8 vs. 32 bit, any difference

Rich Parry wrote on 8/13/2017, 7:16 PM

I am not a professional, my video work is for my own personal use (friends and family). My cameras provide 8 bit video only (Sony FDR-AX100, GoPro Hero 3, DJI Phantom 4 Pro, DJI OSMO, etc.). Is there any reason to use anything other than 8 bit pixel format in VP Project Properties?

Thanks in advance,

Rich in San Diego

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

Comments

Kinvermark wrote on 8/13/2017, 7:42 PM

Practically, No. In theory, if you were doing a LOT of post color work, etc., Maybe.

Musicvid wrote on 8/13/2017, 9:35 PM

Kinvermark's response is spot on.

The theoretical advantage of grading in 32 bit is insignificant when impressed on 8 bit source, even when rendered >8 bit.

karma17 wrote on 8/13/2017, 9:36 PM

Just asked the same question on the Logarist thread. Yes, it is supposed to provide more precision when color correcting. I don't know all the math, but apparently even when converting 8 bit codec, rounding errors are possible and something can be lost. However, you can always try some tests to see if you notice anything.

Musicvid wrote on 8/13/2017, 9:44 PM

Yes, I've heard that too; never seen QUANTIFIED tests, however...

The other thing I've noticed is that promoters of those theories universally forget to factor in the effect of quantization and dither noise on the video shadow detail. Even when I show them they disregard it.

Marco. wrote on 8/14/2017, 6:44 AM

I think in most cases your pretty fine using 8 bit projects.

You need to use a float point project in Vegas Pro though if you want to process a 10 bit pipeline from input to output (assumed you use 10 footage which Vegas Pro is capable to process as 10 bit, unfortunately Vegas Pro doesn't support that many 10 bit file types).

To me the biggest advantage of using a float point project over using an 8 bit project is for certain compositing and color correction/grading tasks where clipping may occur, then transfers and might add and also kind of ping-pong effect of clipping and compressing may happen.
In float point projects you will also see such clipping in the preview but internally (because of the technical math behind float point processing) there is no such thing as clipping and thus enables to withdraw clipping and to avoid such ping-pong effects.

Wolfgang S. wrote on 8/14/2017, 8:54 AM

Just asked the same question on the Logarist thread. Yes, it is supposed to provide more precision when color correcting. I don't know all the math, but apparently even when converting 8 bit codec, rounding errors are possible and something can be lost. However, you can always try some tests to see if you notice anything.


The Logarist is - similar to ACES - a Color Management System. Means, that it will do much more then one could do with the typical color correction Tools in Vegas - for example Transfer footage to the correct color space as decided. And here it is not about simple "rounding Errors" - but it is about to get the Colors right.

It is quite clear that with 10bit or higher footage such a System has some clear Advantages since it offers that. But there are now a lot of cameras that shoot slog with 8bit. Here you can ask if a simple LUT would not be enough - can be applied with external Tools also in Vegas. What would you do here.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Musicvid wrote on 8/14/2017, 9:25 AM

You need to use a float point project in Vegas Pro though if you want to process a 10 bit pipeline from input to output.

Right - - but with 8 bit source its a little like putting mascara on a pig.

(because of the technical math behind float point processing) there is no such thing as clipping

Well, I suppose there is a theoretical bit saturation level but I don't know how one would go about filling it.

OldSmoke wrote on 8/14/2017, 11:26 AM

I am not a professional, my video work is for my own personal use (friends and family). My cameras provide 8 bit video only (Sony FDR-AX100, GoPro Hero 3, DJI Phantom 4 Pro, DJI OSMO, etc.). Is there any reason to use anything other than 8 bit pixel format in VP Project Properties?

Thanks in advance,

Rich in San Diego


Rich, are you shooting and delivering in 1080p or 4K? You could convert the AX100 4K files from 8bit to 1080p 10bit, Catalyst Browse does a good job, by transcoding it to XAVC-I 1080p. Not sure how well the DJI Phantom 4, OSMO and other 4K footage would hold up during transcoding to 1080p 10bit but the AX100 files do very well.

Now, is that all worth the trouble? From personal experience I tell you no, stick with 8bit. Not only is it much easier to edit you also loose the ability to "reframe" once you are down to 1080p. As they say... "been there done that".

One more thing I learned from this forum. Working with 10 bit in and out of Vegas and previewing requires 10bit capable hardware too.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Rich Parry wrote on 8/14/2017, 1:00 PM

OldSmoke,

I deliver in 1080P exclusively. I also shoot in 1080P with all cameras except the DJI Phantom 4 Pro where I shoot 4K so that I can crop.

I've played with transcoding to other formats based on discussions on this forum, but at the end of the day it seems a lot of extra work and I don't see a difference. This is not to say there is no difference, only that I don't see it. I wouldn't be surprised that if someone showed me the difference it would be obvious. Reminds me of "artifacts", once I knew what to look for, they are easily spotted and wonder how I ever missed them.

Rich

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

Musicvid wrote on 8/15/2017, 9:38 PM

Rich, you've answered your own question.

Shoot an open blue sky scene in 8 bit. You will see banding.

Color correct and grade in 32 bit float.

You will see the same banding.

That's all anyone should need to know.

Robert W wrote on 8/16/2017, 2:52 AM

If you are just making straight cuts with no crossfades or any other fade fades, and no colour correction then working in 8 bit should produce a similar (but not necessarily the same) output as 32 bit. However, if you want to use crossfades and colour correction, no matter what the input or output format you will get possibly different (arguably better) results working in 32 bit. I say this as someone that only ever works with Vegas in 8 bit mode as I have found everything apart from that mode to be problematic, unpredictable, glitchy and woefully slow. But that does not detract from the simple fact that modes that work in higher than 8 bit should provide superior output through higher precision and reducing clipping. If I remember correctly, when the 32 bit mode was introduced in Vegas 8, it was the only way to do optically correct crossfades in the application, and they did look vastly superior to the crossfades in 8 bit mode.

Wolfgang S. wrote on 8/16/2017, 8:22 AM

Rich, you've answered your own question.

Shoot an open blue sky scene in 8 bit. You will see banding.

Color correct and grade in 32 bit float.

You will see the same banding.

That's all anyone should need to know.

Shot your sky in 10bit. Grade in 10bit. Render to 10bit.

You will see no banding.

That is the first point anyone should know.

The second one is that all the now available HDR displays come near to DCI P3 - typically 98% or so. And if you shoot with log you are ready for that, but 10bit or more are a must. The 32bit floating point method together with Color management approches like ACES or Logarist are the best path to be fit for the future. And the future will not be 8bit rec709 420 any more.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Musicvid wrote on 8/17/2017, 7:43 PM

And the future will not be 8bit rec709 420 any more.

Need to qualify that a bit. Streaming ability for universal delivery is going to remain just there (720p) for some time. Remember that China only very recently reached 5Mbps connection capabilities, still less than needed for reliable 1080p Internet streams...

astar wrote on 8/18/2017, 4:44 PM

I really feel like it's one of those questions where if you have to ask, don't change the setting. You either need it or you don't, and if you need it, you will know you need it.

Most people that buy new drones and low end camera gear do not know what codec they are shooting in, much less the color depth.

GJeffrey wrote on 8/18/2017, 5:45 PM

Remember that China only very recently reached 5Mbps connection capabilities,

Completely wrong. You are assuming things you don't know.

Musicvid wrote on 8/18/2017, 6:08 PM

My source is Akamai.

Your weak attempt at a personal attack has been reported as inappropriate.

GJeffrey wrote on 8/18/2017, 6:27 PM

My source is Akamai.

Your attack has been reported as abuse.


Thank you Musicvid. My source is I'm living in China for several years.

OldSmoke wrote on 8/18/2017, 6:35 PM

Your weak attempt at a personal personal attack has been reported as inappropriate.

Seriously????

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Musicvid wrote on 8/18/2017, 6:51 PM

And I bet you have really great connectivity!

 

ushere wrote on 8/18/2017, 7:21 PM

if you live in a metropolitan area almost anywhere in the (developed) world you're more than likely going to have a reasonable to good, if not excellent internet connection.

for the vast majority of people living OUTSIDE of metro areas, it's another story entirely. on a 'good' day i get 2.5mbs, i have friends around the world who, like myself, live 'rurally', who share the same lackluster connections.

as for china, my wife often visits there, going to more remote areas where there's NO internet at all.

it all depends on where YOU are.

Musicvid wrote on 8/18/2017, 8:26 PM

Data through Q1 2017. Source:Akamai.net

bitman wrote on 8/19/2017, 2:50 AM

Rich, you've answered your own question.

Shoot an open blue sky scene in 8 bit. You will see banding.

Color correct and grade in 32 bit float.

You will see the same banding.

That's all anyone should need to know.


I live in Belgium, when will there ever be an open blue sky?

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

bitman wrote on 8/19/2017, 2:57 AM

You need to use a float point project in Vegas Pro though if you want to process a 10 bit pipeline from input to output.

Right - - but with 8 bit source its a little like putting mascara on a pig.

(because of the technical math behind float point processing) there is no such thing as clipping

Well, I suppose there is a theoretical bit saturation level but I don't know how one would go about filling it.

Some artists like the famous Wim Delvoye (Belgian neo-conceptual artist) go further than mascara on a pig:

https://wimdelvoye.be/work/tattoo-works/tattooed-pigs/

 

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

fifonik wrote on 1/30/2018, 5:08 PM

Sorry for adding this to quite old thread...

I DO my home video editing in 32-bits video levels not to avoid colour banding (in reality I've never seen huge banding in my resulting videos even with sky gradients or sunsets, compression artifacts on these areas could be much worse). The reason is slightly different: if you do editing in 8-bits levels pixel format that if levels modified by a filter moved outside of 0-255 range are truncated before they passed to another filter in chain (example: Colour Corrections -> Levels -> Sharpen).

It is possible to minimize or completely avoid the issue but you have to be very careful when you using multiple filters in chain that modify colours (scopes are extremely helpful for this). If you switch your workflow to 32-bit video level it would be not an issue any longer. Unfortunately, everything will be slower and at this stage you cannot use some encoders (XDCAM-EX, Sony AVC) because of Vegas 15 bugs (build 261, no issue in VP13 with Sony AVC, know nothing about XDCAM-EX).

Blog article with explanation (sorry for the link to adobe web site). The idea behind 32-video levels in Vegas is the same.

I posted a way to reproduce it. You can do the same with real footage, not media generated one.

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 5700X, RAM: G'Skill 32 GB DDR4@3200, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer