I have been experimenting with the various picture profiles. The clips (no PP or PP1 or PP4 for example) are recorded by the A7111 in BT709 color space. I use MediInfo to examine the atributes of clips. If I bring this into Vegas Pro, and then render, there is no color space other than YUV. It seems to loose the bt709 space. I tried for example in the customize template to set the project color space to 709 as well as assigning the clip 709.
Any thoughts on this?
No, Vegas previews in RGB space.
Pay no attention.
If you truly shot at 709 levels (with zebras, not just flagged as such), you should need no correction on the output.
Histogram is your best friend here. Preview image is not, unless you temporarily correct, then remove the correction.
A little vocabulary -- B.T. 709 and YUV are different names for the same HD color space. Another name is Y'CbCr, but it doesn't exactly roll off the tongue. Vegas' pipeline is 4:4:4 RGB.
Do not change render colorspace -- they are correct to the format.
Thank you. I have looked at YUV and understand it to be a color encoding system, but can be used for BT.601, BT. 70 as well as BT.2020. understand. But in the clip info it does say YUV and BT 709 color space (in two lines of text) for the clips right out of the camera. After rendering the BT 709 color space is removed and only the YUV is left. When I render in HDR the rendered clips show YUV as well as BT.2020 in two lines of text. So I am not sure how it is specifically BT709.
Thanks for your help on this.
It's not like "profiles" for print production; you can't lose a rec 709 colour space. If your clips were shot that way, then that's what they are.
If I bring this into Vegas Pro, and then render, there is no color space other than YUV. It seems to loose the bt709 space.
No it didn't. Tags are not consistent across writing libraries, and that's all they are.
If you saw an unexpected shift in preview levels, that is a different issue.
Yes, YUV can have different color spaces. YOUR YUV COLORSPACE IS B.T.709. At least that's what you said. Did you deliberately misflag 4k as 709? (If you did, it's probably ok this time.)
Now, here's the definition:
SD is 601..
HD is 709
4k is 2020
I don't get the question? It's not something you can change without causing small errors in decoding. Color space is not a user setting, because it is governed by standards.
Welcome to the forum, and please post full MediaInfo and Vegas file properties if you have more concerns.
Honestly, I simplified my first reply to deter you from overthinking. Don't overthink.
After rendering the BT 709 color space is removed and only the YUV is left. When I render in HDR the rendered clips show YUV as well as BT.2020 in two lines of text. So I am not sure how it is specifically BT709.
1. You cannot shoot in 709 and render 10 bit HDR. The tail does not wag the dog.
2. How it was shot is how it is. You can't unbake the cake by changing a line of text.
3. Don't tinker with your parents' plumbing.
Again, welcome to the forums.
The clips out of the A7111 are 8 bit BT.709. I am not trying to render that has HDR. I am on the other hand rendering the S-Log2 and HLG as HDR. Hopefully I am a little clearer on this. Sorry for any confusion. As for over thinking (which I do not think I was) and why not if you are trying to learn. There is nothing to "break" and exploration is part of the fun. And, sometimes you have to tinker with your parents plumbing (I assume you mean like their home :)) to make sure all is well and make the fixes.
Thank you for the welcome!
dave
The clips out of the A7111 are 8 bit BT.709.
And without those source properties and unadulterated source sample, I doubt we'll ever get to the bottom of your experience. However, inconsistent and missing metadata (just a line of text really) is very common across encoders. Good luck with your experimenting.
Are your source clips HD? Are your source levels conformed to 16-235? Is your project pixel format set to 8 bit, as it should be?
Is the plumbing really broken?