Export with HEVC Main Profile

vers 23.05.07 Windows 10, 24 Go Ram, Effet GPU actives

I usually use HEVC output format which compresses a lot.
I have a very small 7 sec file with two tracks, the export stops immediately (failed), I compared the settings of this module with version 22.12.21 and they are identical.


In the “Advanced” export settings, if you have enabled “Hardware Encoder”, I suggest to try a test with it turned off.

After a job fails, right click on the job, select “View Log” and post the log here for us to see.

Thank you Brian,
I had this option checked, by disabling it the export is carried out without problem.

[producer avformat] audio: total_streams 1 max_stream 1 total_channels 2 max_channels 2
[AVIOContext @ 000001d06eb20380] Statistics: 65536 bytes read, 0 seeks
[hevc_qsv @ 000001d06f3888c0] Encoder: input is system memory surface
[hevc_qsv @ 000001d06f3888c0] Use Intel(R) oneVPL to create MFX session, the required implementation version is 1.1
[chain avformat-novalidate] E:/ShotCut/invisible.mp4
checking VFR: pkt.duration 823367
[hevc_qsv @ 000001d06f3888c0] Initialized an internal MFX session using hardware accelerated implementation
[hevc_qsv @ 000001d06f3888c0] Using the constant quantization parameter (CQP) ratecontrol method
[hevc_qsv @ 000001d06f3888c0] Selected ratecontrol mode is unsupported
[hevc_qsv @ 000001d06f3888c0] Current frame rate is unsupported
[hevc_qsv @ 000001d06f3888c0] Current picture structure is unsupported
[hevc_qsv @ 000001d06f3888c0] Current resolution is unsupported
[hevc_qsv @ 000001d06f3888c0] Current pixel format is unsupported
[hevc_qsv @ 000001d06f3888c0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
Failed with exit code -1073741819
Failed with exit code -1073741819

I am also experiencing problems with the hardware encoder in the new version, and so far, for some unknown reason, it does not work properly for me.

I tested this (Windows 10, i7 with Intel Iris Plus 655 GPU), and it is working fine for me on a system from 2018, and it is working for me. Maybe your hardware fell out of support when I upgraded the QSV library to support newer hardware.

Good evening,
version 23.05.14 no longer poses this problem :wink: