MP4 rendering too dark/wrong colors

[Graham Bernard]

_______________________________________________________________

[Jeremy Rodgers] “So I’ve been fighting with this issue for days. I’m working on a project that requires exact colors to show the difference between color filters for a game mod.”
_______________________________________________________________

Jeremy, I hear you.

I’ve lifted a “small” selection from Glenn Chan’s website. Glenn is a most excellent fellow and will go to great lengths to assist others. Please read below and then also take in and absorb what he says regarding the way Vegas Previews, especially with regard to 32bit Floating Point FULL RANGE versus VIDEO LEVELS

Here’s the quote:-

“Example workflow – 32-bit project with mostly video clips

*Life is simpler if you simply use an 8-bit project instead.

For 32-bit projects, I would recommend using the 32-bit floating point (video levels) mode and not (full range). This is the simplest approach and avoids dangerous behaviours such as forgetting to switch compositing gamma to 2.222, forgetting that the color bars decode to studio RGB, defaults into accurate previews over DV/firewire, works well with Cineform files, etc. etc. The sections on compositing gamma and levels differences between 8-bit and 32-bit projects explain why these two areas can be dangerous.

So when using “32-bit floating point (video levels)” and a compositing gamma of 2.222:

Still images decode to computer RGB levels so we should apply a “computer RGB to studio RGB” levels FX onto them to convert them to studio RGB (also referred to as “video levels” in Vegas).
HDV and AVC HD clips will decode to studio RGB levels. We do not necessarily have to do anything to these media. However, almost all DV and HDV cameras will record illegal superwhite values above 235 RGB. You may wish to apply color correction to these clips to deal with these illegal values.
DV and Cineform clips also decode to studio RGB levels and can be left alone.

We can use a DV device as the preview device. If using a Windows Secondary Display as the preview device, make sure that the studio RGB checkbox under color management is checked under Options -> Preferences -> Preview Device.

Here’s Glenn’s website. Read it carefully and apply his advice.

Cheers

Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Jeremy Rodgers]

I’ve tried rendering with each of those settings changed. 8 bit, both 32 bit options and both compositing gamma options.

The end result is always different than my original video file. When I say original, I mean the original file that I recorded, not the preview window.

To be honest I don’t think there is anything more I can try. I’ve tried changing every setting and rendering again. I’ve rendered 20+ different files, not a single one of them had identical color.

[Graham Bernard]

Jeremy, could you add a JPG of your Vegas Scopes that will reflect the best match you are wanting. At the moment you are in a world of variables that will take too much to unfathom.

So here is BEFORE I apply the Sony Computer RGB to Studio RGB Levels – I’m using 32bit Video Levels throughout.

Picture:

Scopes:

And AFTER I apply the Sony Computer RGB to Studio RGB Levels:

Now, could you use my approach here to show us what you are getting AND what you are wanting to achieve? Until I can see we are both using the same reference points we’d be “floating” about too much for this to be helpful.

OK, I initially thought you;d need to toggle the CtoS RGB to get what you were wanting, but I believe you have another variable that needs to be confirmed or denied so we can get a suitable and sensible resolution.

Yes you are correct there is a minute change between your FIRST and SECOND JPG. I understand that. What I’m inviting you to do is to provide some actual SCOPE info for us to work with – otherwise we’re into comparisons and those comparisons are minute. What ISN’T minute is the stretch into the super BLACKS and WHITES that Vegas has “performed”. My idea is that this is that this is two fold:

1] It’s the non-intuitive way Vegas deals with CtoS Previewing – much discussed elsewhere, and here you are using non-Video files, they’re graphics.

and . .

2] Your use of 32bit Full Range as opposed to Video Levels.

But until we can all see that your RealWorld, meaning Scopes of before and after outcomes are, I’m guessing as to exactly what your issue/s are.

HTHs?

Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Graham Bernard]

Post a MedInfo of your ORIGINAL File.

G

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Jeremy Rodgers]

I’m not exactly a vegas pro, so I’ll be surprised if I can do what you want on my first try.

I’m not sure how I’m supposed to show you what I want to achieve, because I’m unable to get vegas to do what I want. The most I can do is give you scopes of the original video, if that will help.

Scopes are new to me, can you describe what you need me to do with a little more detail.

[Jeremy Rodgers]

Here you go. Hopefully this is what you wanted.

General
Complete name : C:\movies\Rome2 2013-10-17 21-41-48-625 VR0.avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 732 MiB
Duration : 7s 234ms
Overall bit rate : 849 Mbps
Original source form/Distributed by : Video:Lagarith Lossless Codec Audio:Speakers (Plantronics GameCom 780)
Writing application : DxtoryCore ver2.0.0.119

Video
ID : 0
Format : Lagarith
Codec ID : LAGS
Duration : 7s 233ms
Bit rate : 848 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 30.000 fps
Color space : RGB
Bit depth : 8 bits
Bits/(Pixel*Frame) : 13.639
Stream size : 732 MiB (100%)

Audio
ID : 1
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Mode : Joint stereo
Mode extension : MS Stereo
Codec ID : 55
Codec ID/Hint : MP3
Duration : 7s 234ms
Bit rate mode : Constant
Bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 113 KiB (0%)
Alignment : Split accross interleaves
Interleave, duration : 904 ms (27.13 video frames)

[Graham Bernard]

I’ll have a go!

What version of Vegas are you using?

G

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Graham Bernard]

Actually, Jeremy, can you say if my treatment is what you were after?

G

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Jeremy Rodgers]

Here is the scope thing for the first frame of my original video. Wasn’t sure how to upload so it looks like I screwed up.

https://f1.creativecow.net/6651/scope#6652

As for your treatment, it is really hard to tell with small screenshots. Even with 5 MB fullscreen screenshots it can be difficult to see the difference between the original video and the rendered video. But it is there.

If you want to tell me what you actually did, I can try applying it to a render and see if it produces the color quality that I would like.

[Graham Bernard]

2 questions:

1] When you Preview in Vegas does look DARK?

2] When you Preview in “Another” player does it also look DARK or is it correct?

G

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge