As far as the naysayers who would have me convert to 8-bit first, that's not going to work. I've tried it. It looks like garbage for my video

Unfortunately Vegas Pro can't read any 16-bit still image format correctly. I've tried them all, and not one works. Vegas applies an inexplicable s-curve. You can use some external tool to convert your images to 8 bits first, in which case everything works perfectly fine. An 8-bit still image, depending on the pixel format, will meet or exceed the color precision of your output video, so no information is lost and the quality is good.

You're being intentionally vague about what camera and format you're using, so I won't answer any more questions here.

Hmm, but that would be a case where the new ACES workflow adds some value. So if one works for example in v-gamut, because he uses a Varicam LT or even the new EVA1, then he will use an ACES workflow, set the Event properties to v-gamut, and will transform the gamut to whatever is required.

As Long as we do not engage ACES, I agree that Vegas will not care about the color space. But why should it be decided by the Monitor? So if I use v-gamut, and use a rec709 monitor, I will not have a Transformation to the gamma and gamut rec709. The Monitor will not be able to deliver an appropriate preview for vlog v-gamut.

You can't work *in* V-Log/V-Gamut with ACES. In ACES, the working color spaces include ACES and ACEScc. V-Log/V-Gamut is one of the input color spaces that ACES supports. Yes, ACES has value and can perform color space conversion. But Adobe RGB is not one of the color spaces it supports.

As Long as we do not engage ACES, I agree that Vegas will not care about the color space. But why should it be decided by the Monitor?

When you're working without color management, you are working in the color space of your monitor, because the working color space is the same as the display color space: there is no transformation between them. Sure, if you bring in media in a different color space and you don't apply some color space transformation, the colors will be wrong.

Though not an integer format, but OpenEXR works fine for me. Within a floatpoint project it would preserve the 16 bit data range as well as over- and underexposed floatpoint data and gamma.

Oops, I just see the gamma would only be preserved in 8 bit projects. But this only happens for EXR exported by PhotoDesigner while Vegas Pro reads its own EXP exports without touching the luma curve.

 

You can't work *in* V-Log/V-Gamut with ACES. In ACES, the working color spaces include ACES and ACEScc. V-Log/V-Gamut is one of the input color spaces that ACES supports. Yes, ACES has value and can perform color space conversion. But Adobe RGB is not one of the color spaces it supports.

As Long as we do not engage ACES, I agree that Vegas will not care about the color space. But why should it be decided by the Monitor?

When you're working without color management, you are working in the color space of your monitor, because the working color space is the same as the display color space: there is no transformation between them. Sure, if you bring in media in a different color space and you don't apply some color space transformation, the colors will be wrong.

The separation what is "in" and "out" is artificical. Only because you transform something into a color space for a new calculation does not mean that this is not part of the signal chain.

If your Monitor would decide about the working color space, then it would be possible to exchange the rec709 monitor by an HDR Monitor. Then we would have HDR grading capabilities simply by an exchange of a monitor. That is absurd.

I don't think that it is absurd at all. It's not "deciding" or changing anything; it is simply what you actually see in a case where there is no underlying difference in the data. Obviously this wouldn't be the case if there was a data difference.

Jacob Balazer's use of the language is precise and careful, which is clearly very important when discussing this topic. It is easy to get confused. I think that given the body of work he has produced, it is fair to say he is an expert.

As far as the naysayers who would have me convert to 8-bit first, that's not going to work. I've tried it. It looks like garbage for my video

Unfortunately Vegas Pro can't read any 16-bit still image format correctly. I've tried them all, and not one works. Vegas applies an inexplicable s-curve. You can use some external tool to convert your images to 8 bits first, in which case everything works perfectly fine. An 8-bit still image, depending on the pixel format, will meet or exceed the color precision of your output video, so no information is lost and the quality is good.

This is mostly true unless one wants to do any correcting within Vegas. In which case they'd be working with much less information. "Good" is not what I am after. I already have "unchanged" option available and been using it. I've merely been watching Vegas to see when I'm going to upgrade. You see, I reeeally like Vegas' interface. I really like working in Vegas compared to my other options. I'm about to run a trial of version 15, just in case of some miracle and just to see it. I'll continue to watch the versions and see when the capability is there. If I find a feature request page, I'll request it.

You're being intentionally vague about what camera and format you're using, so I won't answer any more questions here.

Ya, I am because it does not matter and what you need to know is my native format, which I've described thoroughly. What ultimately matters is importing 16 bit images from .psd format without a desaturating banded look.

I think you've answered my question though, thank you. It does not import 16 bit image correctly.

Here are a couple reference articles that (in my mind) clearly addresses the issues surrounding Camera Raw, Adobe RGB & sRGB.

http://www.earthboundlight.com/phototips/in-camera-color-space-for-raw-shooters.html

And the following video (note: 04:30 that specifically addresses video).

...Jerry

Remember, it's all extinct in a couple of years, when true hdr monitors are the norm.