It's a mystery to me too.

According to Johnnyroy

Broadcast black 0.06, 0.06, 0.06, 1.0
Broadcast white 0.92, 0.92, 0.92, 1.0

Dave T2

Thanks guys. Strange move on Sony's part.

Here's a cheat sheet that's always right there in Vegas.

Open the Sony Levels FX and open cRGB to sRGB drop down. The end point values are right there.

What happens though when a client asks me for a certain blue and gives me the RGB values?

You should find free RGB to decimal converters online.
Or you could build a very simple Excel formula to do it for you.
Disregarding the 1-bit output shift (and most people do), 0 RGB maps to .000, and 255 RGB maps to 1.000

I'm speechless. I use Photoshop and have become quite accustomed to clicking on a color, reading the numbers and entering the characters into other panels in other applications.

I don't know how to work in the new number system. For that matter, I don't speak Russian, either. Since I've never traveled to Russia, it's never been a problem for me. Now, it looks as if dealing with a new number system is a problem whether I go to Russia or not. I thought that all the smart people in the world were clamoring for the change to the new number system and I was just too ignorant or amatuerish to understand the true value in it.

I wonder...

Hmm. In my twenty+ years before Photoshop, we used decimal (densitometer) units, and the military used percentages (which was really confusing). When we finally got our first film recorder I was dumfounded by what RGB values even meant.

"What happens though when a client asks me for a certain blue and gives me the RGB values?"

Here's an ultra-simple RGB<->Decimal converter I whipped up over a vodka.
Free, of course ;?)
https://dl.dropbox.com/u/20519276/RGB-Decimal%20Converter.xls

Could this possibly be a prelude to an all-YUV flow, the way Premiere does things?

Or is it just Sony being...Sony ?

I noticed this change in Vegas 11 and thought it was so counterproductive but then again, never really used V11 and relied on V10.......but I had completely forgot about it.

I am thinking about upgrading to V12 but this change in values doesn't make me happy at all. Often I need to punch in RGB values, why did Sony change this? If at least they had kept the RGB values stand beside these new values. This is really sad.

Yeah, didn't we determine before that the percentages were not excactly right? And who expresses percentages as .06, wouldn't it be 6%.

I don't know what the reasoning for changing it was, but there was a loss in accuracy.

Dave T2

+1

Glad to know I'm not the only one feeling mentally challenged on this one. Seems like they should at least be able to give us the option of the way it's always been handled for RGB.

I hadn't heard about this until today. Definitely seems like a backwards step to me.

(Edit: After reading this thread, there is further discussion on this thread)

Is there any reason why this has come about? Industry standards? Move away from graphics<>video - in either direction? Is there something in "another" market that would require SCS to do this?

An option to flick between the 2 methods, the "other" numbers somehow sharing space, while there is any industry "transition", would appear to be an acceptable interim approach. We have it with the Legacy Text and the Colour Corrector, it should also be available here.

If yah downt ask . . . . . . !

Grazie

If I were to guess I would say it has somehing to do with bit depth. Also with moving to ofx.

0-255 in absolute terms only applies to 8bit. Anything else will have different numbers. 0-1 is universal and can be applied to any bit depth . If we use 32bit, I know it still references 8bit material, then basically 0-1 makes more sense, unless 0-255 becomes something of a representitive value like 0-1 (meaning some conversion needs to happen in the background).

My biggest problem is if there is a mix in the same system - it needs to be one or the other.

It is however a real pain when over the years we learned to use 0-255 effectively.

Just my 1.5c.

Willem.

I can enter values into other apps using a choice of methods include actual RGB values. Zero to one is totally obscure, nothing in the industry uses such values and for good reasons. It is not a human friendly system. From my days in process control many things were normalise into the range 0 to 100 where zero is it's not doing anything and 100 means it's running at the maximum typical level or fully open. Many things can be pushed to 110 though but that give a clear indication to a human to take care.

Bob.

What is so difficult to understand? Just use a calculator and multiply all those numbers between 0 and 1 by 255 if you prefer the 0-255 system. Or alternately, divide the 0-255 values by 255 to get the 0-1 result, so 235 becomes 235/255=0.92 etc.

Red Prince, you are correct, but if you look at your scopes, you will see there is an error. Black is not exactly where it is supposed to be at what used to be 16RGB. Plus, I already know the numbers as RGB numbers, why should I have to do math for preset numbers?

16 caculates to .0627450980392......

and you can only enter .06

Dave T2

The decimal scale for luminosity has been around since the beginning of time as we know it -- the epoch of photometry around 1929 iirc. Taken in time (and usage) context, RGB 8-bit scale is a relative youngster, although their numerical relationship is linear (log base 2, I think).

However, that is not the issue. The lack of three significant digit granularity and an RGB scale option in newer Vegas is incomprehensible from a front-end perspective, imo.

Since everyone's in agreement let's all send a feature request to Sony to get the option of actual 0-255 RGB values back in Vegas. "Squeaky wheel gets the grease"