08.05.2024, 14:01
Hi
I'm having an issue with the current Hybrid version (2024.05.05.1) but first started experiencing it with the previous version (2024.04.06.1) where encoding with RIFE (using my NVIDIA card) is causing encoding to fail part way through.
The debug output from one clip is here:
https://pastebin.com/ej4rrK2L
The point where the encoding suddenly stops is here in the log (lines 1762-1769):
This seems to happen across all different input videos - it definitely seems to be triggered solely by using RIFE. This seems to occur regardless of the RIFE model chosen (I've tried the 4.14 full, 4.15 lite and 4.16 lite models. The original clip encodes just fine if RIFE is switched off. This error occurs regardless of output codec chosen (have tried with x264, x265, NVEnc AV1). Other RIFE settings are default with a factor of 2 (i.e. doubling FPS).
The issue only seems to appear when using my NVIDIA RTX 4060 (laptop). If I force RIFE to use the internal AMD 780M GPU (otherwise using the same settings), the issue doesn't occur.
The failure point is not consistent, but usually tends to happen after 40-60 seconds of video have been encoded.
The input clip is here (but have tried with multiple clips and experienced the same issue):
https://1fichier.com/?oi4jgshyqwvfdxefmwbj
I have updated the drivers, that has not made a difference. I was not always experiencing this issue in the previous version but something seems to have brought it on. Curious if anyone else has experienced anything similar or has any insight.
I'm having an issue with the current Hybrid version (2024.05.05.1) but first started experiencing it with the previous version (2024.04.06.1) where encoding with RIFE (using my NVIDIA card) is causing encoding to fail part way through.
The debug output from one clip is here:
https://pastebin.com/ej4rrK2L
The point where the encoding suddenly stops is here in the log (lines 1762-1769):
2024.05.08 - 21:40:50_Windows 11 Version 22H2 (64bit)_2024.05.05.1 - level 9: x264 output: 1967 frames: 151.46 fps, 3758.85 kb/s
2024.05.08 - 21:40:50_Windows 11 Version 22H2 (64bit)_2024.05.05.1 - level 9: x264 output: 2007 frames: 151.52 fps, 3762.99 kb/s
2024.05.08 - 21:40:50_Windows 11 Version 22H2 (64bit)_2024.05.05.1 - level 9: x264 output: y4m [error]: bad frame header length
2059 frames: 152.54 fps, 3744.08 kb/s
2024.05.08 - 21:40:50_Windows 11 Version 22H2 (64bit)_2024.05.05.1 - level 9: Ignored: y4m [error]: bad frame header length
2024.05.08 - 21:40:51_Windows 11 Version 22H2 (64bit)_2024.05.05.1 - level 9: x264 output: x264 [info]: frame I:11 Avg QP:19.30 size: 54527
x264 [info]: frame P:687 Avg QP:22.16 size: 17122
x264 [info]: frame B:1422 Avg QP:25.66 size: 5398This seems to happen across all different input videos - it definitely seems to be triggered solely by using RIFE. This seems to occur regardless of the RIFE model chosen (I've tried the 4.14 full, 4.15 lite and 4.16 lite models. The original clip encodes just fine if RIFE is switched off. This error occurs regardless of output codec chosen (have tried with x264, x265, NVEnc AV1). Other RIFE settings are default with a factor of 2 (i.e. doubling FPS).
The issue only seems to appear when using my NVIDIA RTX 4060 (laptop). If I force RIFE to use the internal AMD 780M GPU (otherwise using the same settings), the issue doesn't occur.
The failure point is not consistent, but usually tends to happen after 40-60 seconds of video have been encoded.
The input clip is here (but have tried with multiple clips and experienced the same issue):
https://1fichier.com/?oi4jgshyqwvfdxefmwbj
I have updated the drivers, that has not made a difference. I was not always experiencing this issue in the previous version but something seems to have brought it on. Curious if anyone else has experienced anything similar or has any insight.