I have a tape full of shakey footage where I had to hand my Z1 camera to a relative. The footage is really important, so I thank the stars that we all have the Deshaker plugin for VirtualDub and John Meyer's tutorial.
I ran into something that made me want to adjust my workflow for better (IMO) results, and it's in VirtualDub itself. When vdub processes video in the 4:2:2 color space (which is what CFDI uses), according to the vdub help file:
This format, as do all other YCbCr formats listed below, encodes luminance (Y) with a range of [16, 235] and chroma (Cb/Cr, or U/V), with a range of [16, 240].
The Z1 camera extends the whites beyond luminance of 235, providing more detail in the highlights. I saw the results: running my CFDIs through vdub got all the whites beyond 235 clipped off.
I do of course make my outputs broadcast legal, but I prefer to do it with Vegas's levels FX, which compacts the whole contrast range of your captured video to fit within broadcast legal ranges. Doing it this way preserves levels of detail in the highlights that would otherwise get cut off and thrown away if you send the raw footage directly to vdub.
So I found it necessary to add a "prepare for deshaker" step to my workflow. I load the converted CFDIs into Vegas, add and use the levels FX to make then broadcast legal, then render them out to CFDI (again). These adjusted CFDIs will then be run in deshaker which won't clip the highlights (because they are already within broadcast legal ranges).
Has anyone else run into this? Any thoughts on the workflow that would best handle the colors issue?
I ran into something that made me want to adjust my workflow for better (IMO) results, and it's in VirtualDub itself. When vdub processes video in the 4:2:2 color space (which is what CFDI uses), according to the vdub help file:
This format, as do all other YCbCr formats listed below, encodes luminance (Y) with a range of [16, 235] and chroma (Cb/Cr, or U/V), with a range of [16, 240].
The Z1 camera extends the whites beyond luminance of 235, providing more detail in the highlights. I saw the results: running my CFDIs through vdub got all the whites beyond 235 clipped off.
I do of course make my outputs broadcast legal, but I prefer to do it with Vegas's levels FX, which compacts the whole contrast range of your captured video to fit within broadcast legal ranges. Doing it this way preserves levels of detail in the highlights that would otherwise get cut off and thrown away if you send the raw footage directly to vdub.
So I found it necessary to add a "prepare for deshaker" step to my workflow. I load the converted CFDIs into Vegas, add and use the levels FX to make then broadcast legal, then render them out to CFDI (again). These adjusted CFDIs will then be run in deshaker which won't clip the highlights (because they are already within broadcast legal ranges).
Has anyone else run into this? Any thoughts on the workflow that would best handle the colors issue?