I think so... but do you know if a version for avisynth 2.5 exists? And if not, how is it possible to make the same luma corrections using other filters? Thanks Lucio P.S. Is there an Huffyuv version for YV12? I did read the thread but find nothing...
RE: Is mjpegcorrect() still needed in Avisynth 2.5?
One of the last questions in the YV12 faq!
--------------------- 7/ 95 Daytona Violet Lux M3 l B&B Triflow l AA Track Pipe l 540i HFM l #24 Inj l Conforti Chip l Cosmos CAI l ZKW w/ 6000k l ZKW FOG's w/ 6000k l Smoked Euro l Sunbelt Cam's coming soon...
RE: Is mjpegcorrect() still needed in Avisynth 2.5?
- MjpegCorrect seem to be a luma-scaling filter - this should not be necessary at any time. Use historgram to check your color ranges - if you run it in YV12 mode it should not enter the "brown/yellow" areas, but black should lie at the bottom of this range. See the capture guide on the main doom9 page for more info. - Using MJPEG it doesn't matter what format you capture in - this will have no impact on the speed you get, when decoding it.
RE: Is mjpegcorrect() still needed in Avisynth 2.5?
I think the issue is that some mjpeg codecs improperly/inconsistently clip the luma range to 16-235 when encoding/decoding yuy2. is fairly informative. I use the pixel_type parameter in avisource to force rgb decoding and then convert to yuy2 or yv12. Presumably it's slower than mjpegcorrect, but perhaps more accurate? For completeness, decoding picvideo in yuy2 then converting to yv12 does run into the "brown/yellow" areas of histogram. Decoding in rgb then converting to yv12 does not. The morgan codec seems to have the same problem. Edit: coloryuv(levels="pc->tv") should do the same thing as mjpegcorrect, but decoding to rgb seems more accurate to me.
RE: Is mjpegcorrect() still needed in Avisynth 2.5?
@waka: Luma range SHOULD be limited to 16-235. RGB->YUV convertion also produces 16-235 as defined by CCIR 601. When you do this you get overbrighted video.
RE: Is mjpegcorrect() still needed in Avisynth 2.5?
I phrased that poorly, what I should of said is that on decoding 16-235 is scaled to 0-255(!?!). On encoding 0-255 is clipped to 16-235. At least thats how it seems to work on my system. Decoding in yuy2 using avisynth and resaving in vdub causes the video to get more and more clipped with each iteration.