I cant get my video to render with the same colour depth as in preview

amir-k wrote on 4/28/2020, 7:55 PM

Vegas Pro 17 (build 421)

I have been editing my videos with 8-bit pixel format (in project properties) and when I render, the video always looks like 32-bit (full range, 2.222 gamma correction). The video looks too dark which makes my desired colour correction/effects to be very off.

(my render settings)

Strangely, MediaInfo states that the rendered video is in 8-bit depth AND 4:2:0 colour:

I have read the ways to tackle this: adding the Levels and changing it to 'Computer RGB to Studio RGB'. I've even altered the colour correction, whilst previewing in 32-bit to be as close as it was before. I will also choose the 32-bit colour option when editing my future projects from scratch. (even though I personally prefer 8-bit for my type of projects)

The reason why I'm really bothered is now the plugin effects on this project look very different, and it is nearly impossible to make it look similar to the 8-bit preview, which I desire.

My question: Is it possible to render the video in the 8-bit format exactly like the preview displays, without altering the effects?

Comments

john_dennis wrote on 4/28/2020, 8:09 PM

Yes

fifonik wrote on 4/28/2020, 8:15 PM

From FAQ:

https://www.vegascreativesoftware.info/us/forum/faq-why-does-my-video-have-more-contrast-than-the-vegas-preview--104567/

It is not possible to have preview in one monitor setup to display the same as in render without 3rd party extensions. However, you can follow FAQ and download/install free SemW extensions (thanks again to author) that makes your life easier.

UPDATE:

If you made your corrections based on preview (and it is now in 0-255 based on Scopes), your easiest solution would be to add to Output FX filter "Levels" with "Computer RGB to Studio RGB" preset.

In future, if you prefer to use preview (single monitor setup) you should install the extension and select PC in dropdown. Unfortunately, you will not be able to have scopes and preview displayed correctly at the same time in this case.

amir-k wrote on 4/28/2020, 9:02 PM

Yes

I simply cannot find a way to do it. Could you tell me how to do this?

amir-k wrote on 4/28/2020, 9:08 PM

If you made your corrections based on preview, your easiest solution would be to add to Output FX Levels with Computer RGB to Studio RGB preset.

I understand this. I have tried this and it does slightly make the video looks similar to the preview when rendered. However, the effects I have used, such as S_GlowDist, still look completely different from the way it's presented in preview.

Is it possible to render the video in the 8-bit format exactly like the preview displays?

Musicvid wrote on 4/28/2020, 9:20 PM

Yes, by adding the Computer RGB -> Studio RGB levels filter to the OUTPUT, assuming YUV. No exceptions are possible, unless you've not done something right. If you have Dynamic Contrast enabled on your monitor or viewing set enabled, don't do that. Post back once uouve got It figured out.

amir-k wrote on 4/28/2020, 9:38 PM

Yes, by adding the Computer RGB -> Studio RGB levels filter to the OUTPUT, assuming YUV. No exceptions are possible, unless you've not done something right.

What do you mean by 'output'?

If you mean the final video, should I render it, then put it into sony vegas and add the Computer RGB > Studio RGB levels filter?

Musicvid wrote on 4/28/2020, 9:49 PM

HERE IS THE OUTPUT EFFECTS BUSS.

Effects are available at the Media, Track, Event, and Output Level. They are abundantely explained in your program's Help, Interactive Tutorial, What's This?, and of course, downloadable User Manual.

Consult your in-program resources first, whenever possible, please. You are one of several hundred new users just this month, and we are your volunteer peers, not paid support staff. Thanks for understanding.

https://www.vegascreativesoftware.info/us/forum/new-users-consult-the-tutorials-first-please--118014/

fifonik wrote on 4/28/2020, 9:51 PM

What do you mean by 'output'?

In VP FX could be applied to Media, Event, Track and Output. You should add the mentioned filter as Output FX (button to do this could be found just above your preview)

lan-mLMC wrote on 4/28/2020, 10:27 PM

Hope VEGAS team to adopt ComputerRGB so that these problems can be cured rootly

These problems are because vegas preview window shows incorrect color because of StudioRGB

Musicvid wrote on 4/28/2020, 10:58 PM

The Vegas preview is RGB. If what you mean is clip or clamp levels to YUV, preventing the editor from viewing the full source dynamic range in the Preview, I think you will face an uphill battle here. SEMW extension works perfectly well for what you want, and Premiere attempts to.

adis-a3097 wrote on 4/29/2020, 12:36 AM

Absolutely no need to dumb Vegas down just because some of it's user don't know what they're doing, it's a pro software and I hope it stays pro. :)

lan-mLMC wrote on 4/29/2020, 2:16 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

amir-k wrote on 4/29/2020, 2:21 AM

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

As a new 'editor', I myself can admit that I've run into many problems so far and have struggled to fix these problems. This problem alone has demotivated me to even finish the project, as there's really not much I can do. Explaining this would cause drama and I really don't want more people assuming that I am just here to hate on the VEGAS software. I chose Vegas Pro out of all the possible options. However, I will consider premiere pro to render this one project at 8-bit colour depth.

Thank you for your help.

adis-a3097 wrote on 4/29/2020, 3:28 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

lan-mLMC wrote on 4/29/2020, 3:52 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

Hello, it is not a user error, because all other more pro or more intuitional softwares don't have such a problem. By comparison of all NLEs, we can summarize that it's not a user error.

Softwares and Tools' goal is for better work, but not for wasting more working time to resolve this tools' own unique defect which other tools don't have.

adis-a3097 wrote on 4/29/2020, 3:58 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

Hello, it is not a user error, because all other more pro or more intuitional softwares don't have such a problem. By comparison of all NLEs, we can know it's not a user error.

Excuse me, what problem? Is Rec.709 a problem? Is sRGB a problem? Those are all valid choices.

And wth is intuitional software? :)

Reyfox wrote on 4/29/2020, 4:00 AM

I have the SEMW extensions installed and would not have known about it unless I read about it the forums.

New users come for help in very complex software for editing. Not to be belittled, told to RTFM, etc... especially if they are new to video editing and terminology both for video and specific for Vegas.

What may seem simple to those that know the software is not necessarily simple for new users. Talking down to them serves no purpose but make them think they've made the wrong choice in editors.

lan-mLMC wrote on 4/29/2020, 4:11 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

Hello, it is not a user error, because all other more pro or more intuitional softwares don't have such a problem. By comparison of all NLEs, we can know it's not a user error.

Excuse me, what problem? Is Rec.709 a problem? Is sRGB a problem? Those are all valid choices.

And wth is intuitional software? :)

Hello, the problem is that: in the most common 8-bit project, original clip's color ≠ Vegas preview ≠ rendered video because of StudioRGB(16—235).

And most users are using 8-bit projects because 32-bit project is not common and not necessary and not widely used, it will occupy more resources, increase render time and so on.

And a part of plugins don't support 32-bit project such as VEGAS rays and so on. If using such plugins in 32-bit project it may cause crashing or no-response.

Hi, "more pro or more intuitional" I mean "more pro or more not pro" in a mild tone.

adis-a3097 wrote on 4/29/2020, 4:40 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

Hello, it is not a user error, because all other more pro or more intuitional softwares don't have such a problem. By comparison of all NLEs, we can know it's not a user error.

Excuse me, what problem? Is Rec.709 a problem? Is sRGB a problem? Those are all valid choices.

And wth is intuitional software? :)

Hello, the problem is that: in the most common 8-bit project, original clip's color ≠ Vegas preview ≠ rendered video because of StudioRGB(16—235).

If that's a problem, then make it so it isn't. It wont make itself - by itself now, will it? :)

And most users are using 8-bit projects because 32-bit project is not common and not necessary and not widely used, it will occupy more resources, increase render time and so on.

Good.

And a part of plugins don't support 32-bit project such as VEGAS rays and so on. If using such plugins in 32-bit project it may cause crashing or no-response.

The only question here is: do you know how to use Vegas? If not: don't use it, you'll hurt yourself!

If yes, well...more power to you. Go get them, Tiger! 👍

Hi, "more pro or more intuitional" I mean "more pro or more not pro" in a mild tone.

If it's intuitive what you meant by intuitional, then let me ask you this: is Vegas somehow supposed to read your mind? Feel what you feel? Is Vegas supposed to be some kind of AI or something?

How old are you? :)

lan-mLMC wrote on 4/29/2020, 5:13 AM

Now, almost all video editors use ComputerRGB(0-255) more more than StudioRGB(16—235),

and almost all players, websites, or other multi-media companys use ComputerRGB(0-255) too.

I have seen that many new Vegas users or newbies were puzzled why: original clip's color ≠ Vegas preview ≠ rendered video. They have ever encountered such error only in Vegas pro.

For many new vegas users, Color shifting among "original-preview-rendered" is one of the two most important problems. Another is crashing.

They don't know why they need wasting time to solve the problem which shouldn't occur in such a "pro" software. And they don't know SeMW or Voukoder can temporarily solve such problem at all.

So, "they" not knowing and being puzzled by is somehow Vegas's fault? Think not, user error is user error. "They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

Hello, it is not a user error, because all other more pro or more intuitional softwares don't have such a problem. By comparison of all NLEs, we can know it's not a user error.

Excuse me, what problem? Is Rec.709 a problem? Is sRGB a problem? Those are all valid choices.

And wth is intuitional software? :)

Hello, the problem is that: in the most common 8-bit project, original clip's color ≠ Vegas preview ≠ rendered video because of StudioRGB(16—235).

If that's a problem, then make it so it isn't. It wont make itself - by itself now, will it? :)

And most users are using 8-bit projects because 32-bit project is not common and not necessary and not widely used, it will occupy more resources, increase render time and so on.

Good.

And a part of plugins don't support 32-bit project such as VEGAS rays and so on. If using such plugins in 32-bit project it may cause crashing or no-response.

The only question here is: do you know how to use Vegas? If not: don't use it, you'll hurt yourself!

If yes, well...more power to you. Go get them, Tiger! 👍

Hi, "more pro or more intuitional" I mean "more pro or more not pro" in a mild tone.

If it's intuitive what you meant by intuitional, then let me ask you this: is Vegas somehow supposed to read your mind? Feel what you feel? Is Vegas supposed to be some kind of AI or something?

How old are you? :)

Hello, by comparison of all NLEs, it's a really serious problem for new users and newbies.

Almost new users and newbies will use a 8-bit project, and the stupid mistake "original clip's color ≠ Vegas preview ≠ rendered video" will make them abandon Vegas Pro.

And then Vegas Pro will not able to absorb more new users steadily. This is very disadvantageous for Vegas Pro's development and progress.

And "more pro or more intuitional softwares" means that , the problem: "in the most common 8-bit project, original clip's color ≠ Vegas preview ≠ rendered video" is almost only occur in Vegas Pro, other more advanced or more not-advanced softwares will not have this problem. So Vegas Pro should resolve it so that vegas can absorb more new users steadily. If you don't understand it , I'm sorry for my not-first-English.

amir-k wrote on 4/29/2020, 5:47 AM

How old are you? :)

says the one comparing vegas to a toy.

"They" all should learn the software first, Vegas ain't toy. It's a tool. And tools can hurt if misused, unlike toys which are mostly idiot-proof. :)

If that's a problem, then make it so it isn't. It wont make itself - by itself now, will it? :)

The only question here is: do you know how to use Vegas? If not: don't use it, you'll hurt yourself!

If it's intuitive what you meant by intuitional, then let me ask you this: is Vegas somehow supposed to read your mind? Feel what you feel? Is Vegas supposed to be some kind of AI or something?

What is your point adis-a3097? One purpose of this forum is to help people, especially new people like me, that are experiencing issues and also teach about something specific to said new people's problems.

Everything you are saying does not colorate and makes absolutely no sense. How can a person 'learn the software' without even using it? Everyone has started as a newbie even you. Your ignorant logic is that only certain people born with genetic features can use Vegas. Which planet are you from?

vkmast wrote on 4/29/2020, 5:51 AM

The contributors here are reminded of this Post by a VEGAS team member. Please note. Thank you.

amir-k wrote on 4/29/2020, 5:59 AM

If you don't understand it , I'm sorry for my not-first-English.

I have understood everything you've said and you are correct.

The vegas software is not entirely welcoming as other ones and this is mainly because of issues that make the user experience less satisfying. I've never seen anyone talk about this issue on YouTube, which is where most new people learn to use VEGAS. I have almost given up entirely because I've wasted A LOT of time/effort.

fifonik wrote on 4/29/2020, 6:01 AM

most users are using 8-bit projects because 32-bit project is not common and not necessary and not widely used, it will occupy more resources, increase render time and so on.

And a part of plugins don't support 32-bit project such as VEGAS rays and so on. If using such plugins in 32-bit project it may cause crashing or no-response.

Looks like you do not know VP good enough. 32-bit pixel format in VP could be in 2 different flavours. One on them (video levels) behaves exactly as 8-bit pixel format project (in terms discussed in the topic). I use it all the time and I have not noticed any specific crashes or no-responsibleness. So you should not mentioned it just "32-bit project". Use "32-bit project full range" instead.

I agree that having one additional checkbox in preferences (I suggested that to Sony long time ago) would solve the issue for people who using single monitor setup (like myself). However, I do not see this as major issue because this can easily be solved almost completely by using mentioned extension during editing phase or adding single filter if it was done already in "Computer RGB".

I have almost given up entirely because I've wasted A LOT of time/effort.

Wasted? The issue could be solved by adding single filter with pre-defined preset to Output FX! And this is described in FAQ long time ago.