videoh

We're reading what you write. You seem to think this option specifies the range of the input video. No! It defines the range you want for the RGB conversion. Consider...

> * Am I correct in saying all YUV videos are Y(16,235) UV(16,240) (TV/limited range) input? Meaning no matter what, I would want to use -color_range tv on ffmpeg? If...

> Setting aside the issue of whether it's flipped, I'm more concerned with whether this value even matters in the first place. It appears that x264/5 have their own explicit...

Yes, it is expected. Please do the right thing and close this issue.

The difference in dubhater's example is obvious. You are the only person doubting that. How you correctly encode a video that lies between TV and PC range is not relevant...

"And to further confuse everyone" We're not confused, you are. You claimed a specific issue with d2vsource. We have shown that there is no issue. Now you want to use...

Thanks for closing. Hope to see you follow-up at Doom9. There's one more point I'd like to make here. In the DGIndex tools the YUVRGB_Scale option only affects the YUV->RGB...

OK, d2vsource sets the Vapoursynth frame property _ColorRange based on the YUVRGB_Scale value. However, the tools subsequently used (e.g., encoder) must be coded to actually use that frame property, or...

Ha ha! Turns out you were right. d2vsource maps directly YUVRGB_Scale to _ColorRange. But _ColorRange is defined as: 0=full range, 1=limited range, while YUVRGB_Scale is defined as 0=limited, 1=full range....

Yes, but d2vsource does copy YUVRGB_Scale to _ColorRange, and they have different definitions. Easy fix.