Sorry for being a mathematical purist, but you should be dividing by 255, not by 256. There is no 256 in the standard one-byte-per-channel RGB. Yes, there are 256 possible values a byte can store, but since they start at 0, the highest possible value stored in a byte is 255. Not an earth-shaking difference, except if you divide by 256, you will never reach 1.0 for white (255/256=0.99609375), but a difference nonetheless.
So, the corresponding values to 0, 175, 63 rounded to 3 decimal digits would be 0.000, 0.686, 0.247. Vegas may appear to change that to 0.00, 0.69, 0.25 but it only does so when it is displaying the values in the dialog. Internally, it keeps the values unrounded. 32-bit floats in general can have the precision of somewhere between 5-7 decimal digits (because internally they use binary digits, not decimal digits, but Vegas does not let you enter the binary value). To be safe, I wouldn’t go over 5 decimal digits, so I would use 0, 0.68627, 0.24706 for RGB 0, 175, 63.
wrote on 10/21/2015, 10:45 AM
Yep. You are correct. There are 256 values -- zero to 255 when unsigned, when signed it's -128 to 127. I'm a programmer and I should have known better. Sorry for the confusion...
Another example of how crazy it was for Sony to switch to this model for text colors. I understand that for some people it seems to be a good option but most of us work in the RGB color world and expect it to work like all other editing programs do and Vegas always did until some genius changed it.