1 Topic by Rezobyte (edited by Rezobyte 05-04-2020 00:21:57)

Topic: Last update broke H.265/HEVC transcoding for me.

After updating my SVP Pro client this afternoon to v4.3.0.190 (using the auto-updater/installer), I can no longer transcode any videos to HEVC. Any transcoding instantly fails. I have attempted to cleanly reinstall SVP and change any and all options that may help, with no success to get HEVC transcoding working again. Everything was working fine a few hours ago before the update.

I get the following error in the output log when attempting to transcode any videos to HEVC after the update today:
I don't use custom settings for HEVC trancoding in SVP, just the basic software encoder at CRF 18.

19:00:32.013: [ffmpeg] libx265: Cannot open libx265 encoder.
19:00:32.013: [vo/lavc] Could not initialize encoder.
19:00:32.013: Could not initialize video chain.
19:00:32.208: x265 [info]: HEVC encoder version 3.3+1-gdf2ac51
19:00:32.208: x265 [info]: build info [Windows][GCC 9.3.1][64 bit] 8bit+10bit
19:00:32.208: x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
19:00:32.208: x265 [error]: frameNumThreads (--frame-threads) must be [0 .. X265_MAX_FRAME_THREADS)
19:00:32.241: Video: no video
19:00:32.241: [encode] no data written to target file
19:00:32.241: Exiting... (Interrupted by error)

System specs reference:
CPU: 24C/48T Intel Xeon E5-2670 v3
GPU: GTX 1070 Katana
RAM: 128GB

Any assistance with this would be appreciated!

  • Thanks: 1622
  • Thanks for the post: 1

Re: Last update broke H.265/HEVC transcoding for me.

it appears it doesn't work if the "threads" parameter is >16
right now what you can do is move the "cpu usage" slider to the left to the point where it work

Re: Last update broke H.265/HEVC transcoding for me.

Chainik wrote:

it appears it doesn't work if the "threads" parameter is >16
right now what you can do is move the "cpu usage" slider to the left to the point where it work

Thanks! That'll work for now.
Looks like it was trying to use 31 threads by default. Hopefully the thread count will be increased in the future.

  • Thanks: 1622
  • Thanks for the post: 1

Re: Last update broke H.265/HEVC transcoding for me.

it's x265 limitation
there're a few more x265-specific options - "pools" and "numa-pools", you can specify them on your own in Advanced mode
https://x265.readthedocs.io/en/default/ … tion-pools