Quote:
Originally Posted by Sagekilla
@Dark: Regarding the change that would bork interlacing: Would it really be that bad if you created two code paths, one designed solely for progressive video, and another for field based?
I'm sure there's a very good reason why not to, and the only reasons I could think of where because of massive code duplication and messy code.
|
CoreAVC already does this. I don't really feel like doing it with x264. It'd be ugly, and hardly worth it for ~1% speed or whatever we'd get.