View Full Version : TMPGEnc Plus v2.520 and YUY2 and/or YV12 support?
tim254
22nd July 2003, 03:09
TMPGEnc Plus v2.520 (2.520.54.163) Release Notes:
Added the MPEG decoder CRI Sofdec. Now, input of MPEG-2 files is a standard feature. Plus, the picture quality (brightness, color) shown on your pc display will be close to the one on your TV. So the editing will be easier.
*when using CRI sofdec:
remove the check on [ Output YUV data as Basic YCbCr not CCIR601 ]
[ Setting ] => [ Quantize matrix ] => [Output YUV data as...]
Does this mean that TMPGEnc Plus v2.520 now supports YUY2 and/or YV12?
If this is true, then I guess I can stop using ConvertToRGB24() in my AVISynth scripts as long as I make sure CRI Sofdec is set to the highest priority (correct me if I'm wrong).
Happygolucky
25th July 2003, 18:56
The CRI decoder only decodes MPEG 1 and 2 files. AVI files would still be handled the same way as always, I would assume.
tim254
25th July 2003, 23:17
Here's a response to this question that I posted on TMPGEnc's BBS...
ashy 07/23
Yes you are wrong.
The setting is not referring to the format of the input files, but is related to the output colour space. What it is referring to is the the colour and luma range values of the output.
For instance TV luma ranges are 8-235(CCIR601) and PC is 0-255(basic YCbCr)
If you have a source such as DV which has a range of 0-255 and wish to view this on a display that has the same range then you would use this option if you want the values to remain the same in the output.
However for most sources and output to TV 8-235(CCIR601) would be more appropiate as these values are identical to your TV's luma range. Use the wrong setting and it can affect the brightness and contrast of the output.
>Does this mean that TMPGEnc Plus v2.520 now supports YUY2 and/or YV12?
TMPG has always supported YUY2 and YV12 as input but it will convert it to it's native RGB format first.
However TMPG outputs to YV12 which is the native colour space for MPEG and is what the settings above relate to.
In conclusion you should still use the RGB command in your scripts.
--------------------------------------------------------------------
Tim254 07/24
Thanks for your quick and detailed response. So, does this just mean that the new version does a better conversion to RGB as an input, which should result in a higher quality output file (better output color)?
--------------------------------------------------------------------
ashy 07/24
I think what it means is that the codec uses the CCIR601 colour space as imput, which of course most MPEG2 material does therefore to maintain the same luma levels you need to set the output to CCIR601 also hence removing the check.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.