Open vt-idiot opened 2 years ago
I thought it might be due to the AMF mismatch (21.Q4 is the newest Radeon Pro driver) but I got the same exact results when I tried switching back to 6.17 and even 6.13. Enabling either --psnr or --ssim causes an immediate crash with no error.
--psnr
--ssim
G:\VCEEnc>VCEEncC64.exe --avsdll G:\AviSynth\AviSynth.dll --codec hevc --colormatrix bt709 --colorprim bt709 --transfer bt709 --cqp 22:24:27 -i G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default.avs -o G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ VCEEnc (x64) 7.00 (r1066) by rigaya, Apr 30 2022 18:34:01 (VC 1931/Win) OS: Windows Server 2016 x64 (17763) [CP1252] CPU: Intel Xeon(R) E5-2630 v2 @ 2.60GHz [TB: 2.90GHz] (12C/24T) GPU: AMD Radeon Pro WX 2100, AMF Runtime 1.4.23 / SDK 1.4.24 Input Info: AviSynth+ 3.7.2 r3661(yv12)->nv12 [AVX], 1920x1080, 24/1 fps Vpp Filters copyHtoD Output: H.265/HEVC main @ Level 4 (main tier) 1920x1080p 0:0 24.000fps (24/1fps) Quality: balanced CQP: I:22, P:24 VBV Bufsize: 12000 kbps Bframes: 0 frames Pre Analysis: off Ref frames: 2 frames LTR frames: 0 frames Motion Est: Q-pel Slices: 1 GOP Len: 240 frames VUI: matrix:bt709,colorprim:bt709,transfer:bt709 Others: deblock encoded 11708 frames, 149.60 fps, 7096.70 kbps, 412.70 MB encode time 0:01:18, CPU: 23.8%, GPU: 11.8%, VE: 98.8% G:\VCEEnc>VCEEncC64.exe --avsdll G:\AviSynth\AviSynth.dll --codec hevc --colormatrix bt709 --colorprim bt709 --transfer bt709 --cqp 22:24:27 --psnr -i G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default.avs -o G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ VCEEnc (x64) 7.00 (r1066) by rigaya, Apr 30 2022 18:34:01 (VC 1931/Win) OS: Windows Server 2016 x64 (17763) [CP1252] CPU: Intel Xeon(R) E5-2630 v2 @ 2.60GHz [TB: 2.82GHz] (12C/24T) GPU: AMD Radeon Pro WX 2100, AMF Runtime 1.4.23 / SDK 1.4.24 Input Info: AviSynth+ 3.7.2 r3661(yv12)->nv12 [AVX], 1920x1080, 24/1 fps Vpp Filters copyHtoD psnr (yv12) Output: H.265/HEVC main @ Level 4 (main tier) 1920x1080p 0:0 24.000fps (24/1fps) Quality: balanced CQP: I:22, P:24 VBV Bufsize: 12000 kbps Bframes: 0 frames Pre Analysis: off Ref frames: 2 frames LTR frames: 0 frames Motion Est: Q-pel Slices: 1 GOP Len: 240 frames VUI: matrix:bt709,colorprim:bt709,transfer:bt709 Others: deblock G:\VCEEnc>VCEEncC64.exe --avsdll G:\AviSynth\AviSynth.dll --codec hevc --colormatrix bt709 --colorprim bt709 --transfer bt709 --cqp 22:24:27 --ssim -i G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default.avs -o G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ G:\Intel_Demo_Clip2_temp\Intel_Demo_Clip2-Default_out.hevc ------------------------------------------------------------------------------------------ VCEEnc (x64) 7.00 (r1066) by rigaya, Apr 30 2022 18:34:01 (VC 1931/Win) OS: Windows Server 2016 x64 (17763) [CP1252] CPU: Intel Xeon(R) E5-2630 v2 @ 2.60GHz [TB: 2.90GHz] (12C/24T) GPU: AMD Radeon Pro WX 2100, AMF Runtime 1.4.23 / SDK 1.4.24 Input Info: AviSynth+ 3.7.2 r3661(yv12)->nv12 [AVX], 1920x1080, 24/1 fps Vpp Filters copyHtoD ssim (yv12) Output: H.265/HEVC main @ Level 4 (main tier) 1920x1080p 0:0 24.000fps (24/1fps) Quality: balanced CQP: I:22, P:24 VBV Bufsize: 12000 kbps Bframes: 0 frames Pre Analysis: off Ref frames: 2 frames LTR frames: 0 frames Motion Est: Q-pel Slices: 1 GOP Len: 240 frames VUI: matrix:bt709,colorprim:bt709,transfer:bt709 Others: deblock G:\VCEEnc>
VCEEnc 7.09 has some improvement on OpenCL stability, which might solve this issue.
I thought it might be due to the AMF mismatch (21.Q4 is the newest Radeon Pro driver) but I got the same exact results when I tried switching back to 6.17 and even 6.13. Enabling either
--psnr
or--ssim
causes an immediate crash with no error.