Or is there a trick to get the integrated ffmpeg encode recordings in H. It would be really great to have libx265 selectable at the recording encoders of OBS. The H.264 works fine, but the H.265 saves a lot of precious bandwidth. The bandwidth of the DATV transponder is only 8MHz and the transmit power of a ground station is only some ten watts into a dish, so the transmissions are made with bitrates of 2MBit/s down to 33kBit/s.Įspecially for the lower bitrates over the air, the stream bitrates have to be very efficient. I know, that the generic ffmpeg (latest version) works fine with '-vcodec libx265', because i worked around this issue by recording via UDP to a local instance of a generic ffmpeg to transcode from H.264 to H.265.īackground for that is, that a lot of radio amateurs use OBS to generate video streams to send them as 'Digital Amateur Television' DVBS2 coded to the new geostationary satellite QO-100. Why isn't there the choice for libx265 in OBS? Is the OBS integrated ffmpeg not prepared/compiled for that? MPEG-4 part 2 is disabled by default due to VAAPI limitations (the main Intel driver never implemented it, so it didn't get much testing). It seems, this encoder needs hardware support to work, but my GT650M can't do that, so i expect OBS/ffmpeg to use the software encoder libx265 instead. H.265 support was added with GCN 3 (Volcanic Islands) and H.265 10-bit with GCN 4 (Arctic Islands). Of course, these metrics aren't perfect but you can use them as a rough guide to establish equivalence.Failed to open video codec: Generic error in an external library So, run the command once with the x264 output and once with x265 and compare with different x265 outputs, till you get similar measures. That said, you can try to establish your own calibration between the current versions of the encoding libraries in your ffmpeg by running the following command, which executes two popular video quality metrics: ffmpeg -i encoded-video.mp4 -i reference-video.mp4 -lavfi 'ssim psnr' -f null. But x265 is not yet as mature in its development as x264, so take that CRF equivalence with a pinch of salt. x265 CRF 28 is supposed to be e quivalent to x264 CRF 23. The CRF scales for x264 and x265 do not correspond.

H265 ffmpeg