8 bit or 32 bit (Vegas) vs 16 bit (vpx)

bitman wrote on 8/16/2018, 4:14 AM

I am just wondering why Vegas does not use 16 bit deep color (I suppose per color channel) like Magix introduced in their other NLE VPX (video Pro X). We are now stuck in using 8 bit Integer (OK if your source is 8 bit and do not do much color correction) or the more pro (but more system taxing) 32 bit in 2 flavors. 16 bits would seem like a good compromise between computational speed and quality. Although I am not sure if VPX' 16 bit color calculations are integer or float (I could not find info on that).

As a side note I found the latest VPX (e.g. 10 years anniversary) edition time line editing stuttering vs Vegas Pro 15 on the same machine and using the same sourcefile under certain preview window layouts. It could be a bug, but it could also be the that 16 bit is more taxing …

Comments

Kinvermark wrote on 8/16/2018, 8:26 AM

Good question, but I would point out that Premiere and DanVinci Resolve both use 32 bit float, with no 16 bit option (AFAIK). (I can only think of After Effects as having a 16 bit project option). Maybe, as you imply, there is no speed benefit, otherwise I would say "10 bit" calculation (not just support) would be good enough for 90% of uses, but I suspect internally it just doesn't work this way.

Musicvid wrote on 8/16/2018, 9:17 AM

16 bit is mostly an Adobe implementation, that's why.

bitman wrote on 8/16/2018, 11:19 AM

Maybe the upcoming Vegas 16 hints to 16 bit 😆

Musicvid wrote on 8/16/2018, 1:42 PM

To the extent the implementations are proprietary, we will have to rely on converters and AE. Adobe has no interest in licensing their formats to Magix.

Red Prince wrote on 8/16/2018, 2:20 PM

Maybe the upcoming Vegas 16 hints to 16 bit 😆

God, I hope not!