image 'risked' in x265 compress

[rafacharkman]

when I compress the image, in motion scenes the frames look like the one below. How can I fix this?

Before
https://dg6chg.ch.files.1drv.com/y4mD8UZj4ft-BGQV5zIfsSWPz9yaUS0qkl3ZGISGokrsY3TphA2j_RsE9_YTR1KiQgSzkN5_ZqVMAngu6ezgCnK7Ll-z0fUfIQOKON3CDej6oWhk9_XIqr6bn3qoJ5nyEabpwZlYVl1LfS9UimywOMTOMSQtC2dbktkfGIZ6s5805j9L26vDXxM91pORkkiXC-EAjcv29GLKj_lLZ2h7OeNIg/Captura%20de%20Tela%20%2867%29.png?psid=1

After
https://sz4wpq.ch.files.1drv.com/y4mniE7nALTbtuAwKYVB5MQDJUsU58ow0ayV7UdP7jZiyq96BKcHu_pRvSvUaTrCXYwoqGx9pru0isGmS6k6i0kvQmvt32UOKcu3iFo6Ioa5CbWd-mlRxZHataT0HO3vNIQvjSKwdtyBih8CsD2H4-nhTzrkkoseJw1as1G9xKzWv7dc62WAHyXbcebmBz9M4EdmRIZ28liuOS-FfwvNzadwA/Captura%20de%20Tela%20%2866%29.png?psid=1

[benwaggoner]

when I compress the image, in motion scenes the frames look like the one below. How can I fix this?

Before
https://ch3301files.storage.live.com/y4pm-oMqZZ3SvIr_qOL3SccP66Psl84gYVwnYOLqy504d8lV2yF0XGY3rrfhRNYKUqVC94NsGlpeJlCIdCQ9D_Ep4yHUWjOkeU6f1nrVzJCm9IU39k_R3PoGkZUpkGAdrFDj3C-P0ZXbjDsoSskb_ShLT4Cx52xYQ8v9t5224yaALFlgKPA7-8o41I0CBz_0uKZ/Captura%20de%20Tela%20%2867%29.png?psid=1&width=982&height=552

After
https://ch3301files.storage.live.com/y4p11l0SAYn-cL6YuXO0l9FQZuAVlmPw8qi3XxCZnRtY16MOlpHnVDFKYVWQeohJenV_84Ah7ft_q6SvJCfdbLy3UXyI4Y5-1amgumQKzxx7WtiFM6_3Qzvd9IYfvqTLDAiw-AVvVyPmWH22FttbKVP0tCxL22qg2h5MwCW-Qip2TKhaa5HnTNIoQqMfbN9Apyf/Captura%20de%20Tela%20%2866%29.png?psid=1&width=954&height=536
Your image URLs don't work.

[rafacharkman]

Sorry for that. I corrected the links

[Emulgator]

Post your script, please.

[rafacharkman]

Post your script, please.

IFME Options:
Encoder: H.265 (GCC 7.2.0)
Preset: medium
Tune: zerolatency

[poisondeathray]

Is your source interlaced?

Maybe your video player or screenshot taking method is deinterlacing the source ?

[MeteorRain]

You can learn how to deinterlace and ivtc.

[rafacharkman]

I fixed the problem with '--interlace tff ' (or bff) but interlaced scenes don't look good (reduces frames which cause slowness in scenes) and the rest ends up blurring.
Conclusion: x265 support is weak compared to x264.

[RanmaCanada]

I fixed the problem with '--interlace tff ' (or bff) but interlaced scenes don't look good (reduces frames which cause slowness in scenes) and the rest ends up blurring.
Conclusion: x265 support is weak compared to x264.

Sorry, but you are wrong. You just don't know how to properly create an avs script to fix your interlacing. Encoding interlaced material is difficult, slow, and should be avoided at all costs (just remux it). You're also using a one click encoder, which has very limited options. I would suggest that you stick with having Initial D as a remux, as this is SD content, and you don't need to shrink it even further. X265 is for HD material. If you are going to shrink it, use x264 as you will actually get worse visual quality with x265 due to it's nature of handling high grain/noisy/old material(at least in my experience with encoding anime dvd's)

https://forum.doom9.org/showthread.php?t=172286&highlight=interlace

https://forum.videohelp.com/threads/390403-newbie-to-AVISynth-VirtualDub-need-help-with-IVTC-deinterlace-via-QTGMC

[rafacharkman]

Sorry, but you are wrong. You just don't know how to properly create an avs script to fix your interlacing. Encoding interlaced material is difficult, slow, and should be avoided at all costs (just remux it). You're also using a one click encoder, which has very limited options. I would suggest that you stick with having Initial D as a remux, as this is SD content, and you don't need to shrink it even further. X265 is for HD material. If you are going to shrink it, use x264 as you will actually get worse visual quality with x265 due to it's nature of handling high grain/noisy/old material(at least in my experience with encoding anime dvd's)

https://forum.doom9.org/showthread.php?t=172286&highlight=interlace

https://forum.videohelp.com/threads/390403-newbie-to-AVISynth-VirtualDub-need-help-with-IVTC-deinterlace-via-QTGMC

I do not mean the ability of the script to solve the problem, but the functionality, where in x264 it does it automatically and in x265 will have to do it manually.

[sneaker_ger]

Last time I looked ffmpeg didn't really support interlaced HEVC. That's why the x265 results look different than the x264 ones in ffmpeg based players like e.g. MPC-HC/LAV Filters. It's not the fault of x265. Also note that HEVC has less refined tools for interlacing compared to AVC (no MBAFF). For these two reasons it is recommended to either deinterlace before encoding (e.g. using QTGMC as suggested by RanmaCanada) or to stick to x264 for interlaced encoding.

[Blue_MiSfit]

I definitely suggest using qtgmc, outputting in double rate (e.g. 59.94 or 50 fps depending on your source). This will give you very clean results.