Well y262 accepts only raw YUV as input, via file or stdin pipe. Thats because its mostly developed as a library and not an application. Tools like avs2yuv are more flexible than doing some own Avisynth reader implementation anyway.
The limitation last time in this thread was that y262 had no concept of signaling 422 profile and its associated levels. This should work now.
I do not see how some XDCAM-50 file encoded by a different encoder would help with testing y262.
If someone can create a stream with y262 where the configuration set at the encoder API does not match the encoders output - I am interested in that and thats what the Issues page on github is for. Likewise for things currently missing at the y262 configuration API to produce certain Mpeg2 video flavors.
|