I am using av1an to transcode 59.94i MPEG-2 to H.264 using the following command: av1an -i input.ts --vmaf --target-quality 99 -e x264. The expected output field rate is 59.94i; however, the produced file is instead weaved 29.97p.
Figure 1: mediainfo for original (left) and encoded (right) files
Figure 2: Screenshot of improperly weaved output
As expected when trying to encode such video, the compression ratio is terrible (in fact, the output is larger than the input), and VMAF is...nonsense. 🙃
Figure 3: VMAF trace
Given x264 supports encoding interlaced video and no deinterlacing was explicitly specified, correct output should be 59.94i. (AV1 is another question since it doesn't support interlacing at all - in that case, should av1an error or implicitly apply de-interlacing?)
Behavior was tested on av1an v0.5.0; currently building v0.5.2 to verify issue persists. I don't think there's an existing issue covering this problem.
I am using av1an to transcode 59.94i MPEG-2 to H.264 using the following command:
av1an -i input.ts --vmaf --target-quality 99 -e x264. The expected output field rate is 59.94i; however, the produced file is instead weaved 29.97p.Figure 1: mediainfo for original (left) and encoded (right) files
Figure 2: Screenshot of improperly weaved output
As expected when trying to encode such video, the compression ratio is terrible (in fact, the output is larger than the input), and VMAF is...nonsense. 🙃
Figure 3: VMAF trace
Given x264 supports encoding interlaced video and no deinterlacing was explicitly specified, correct output should be 59.94i. (AV1 is another question since it doesn't support interlacing at all - in that case, should av1an error or implicitly apply de-interlacing?)
Behavior was tested on av1an v0.5.0; currently building v0.5.2 to verify issue persists. I don't think there's an existing issue covering this problem.