![mediacoder x64 nvenc h.265 settings mediacoder x64 nvenc h.265 settings](https://user-images.githubusercontent.com/14805663/55078705-1c6ddf80-5071-11e9-858d-ea81ee7bef08.png)
- MEDIACODER X64 NVENC H.265 SETTINGS WINDOWS 10
- MEDIACODER X64 NVENC H.265 SETTINGS SOFTWARE
- MEDIACODER X64 NVENC H.265 SETTINGS WINDOWS
I tried a lot of parameters for FFMPEG and also for OBS to get a good result and it wasn't always clear for me, why some combinations work and some not. Send the output as UDP to IP:PORT with given packet size (copied from Robert ) Use "MPEGTS" as output streaming container Scale down the image to width 384 pixel, height is chosen automatically according to a parameter "n", use the "Lanczos" scaling filter (sharp)
![mediacoder x64 nvenc h.265 settings mediacoder x64 nvenc h.265 settings](http://blog.mediacoderhq.com/wp-content/uploads/2014/02/h265_720p_screenshot.jpg)
Set the audio sample rate (corresponds to the bitrate) Seems to be needed for the AC3 encoder (don't know exactly why) Selects the AC3 audio encoder (more downscaling possibilities than AAC) Selects the compression (the faster, the less delay, but the higher bitrate) Selects the "Constant Rate Factor" for quality (the lower the better) The FFMPEG instance runs in a console window here with the following parameters:įfmpeg -i "udp://localhost:7272" -vcodec libx265 -crf 33 -preset superfast -b:v 40k -acodec ac3_fixed -strict experimental -b:a 12k -ar 12000 -vf scale=384:-2:flags=lanczos -r 12 -f mpegts "udp://192.168.0.199:8282?pkt_size=1316"įFMPEG listens locally at port 7272 for UDP input To work around this, the UDP stream is not sent to the Pluto directly, but to a local FFMPEG instance running which transcodes the stream from H.264 to H.265, downscales audio (thanks to G0MJW for the hint) and send another UDP stream to the Pluto.
MEDIACODER X64 NVENC H.265 SETTINGS SOFTWARE
Unfortunately software encoding is only possible with H.264, but not with H.265. This UDP stream can be created in OBS by recording to an URL instead of a file. The FIRM2201RC gives the possibility to feed the Pluto with UDP packets (thanks to DD4YR for that hint) instead of the common RTMP streaming described on the Pluto documentation page. ADALM-PLUTO with F5OEO firmware "FIRM2201RC" (beta-for-the-brave).
MEDIACODER X64 NVENC H.265 SETTINGS WINDOWS
MEDIACODER X64 NVENC H.265 SETTINGS WINDOWS 10
OBS Studio 24.0.3 (64 bit) at Windows 10.This solution works fine for me with SR125, a 384x306 image size with 12 FPS and 12kHz mono audio and i would say the quality is some kind of "crispy clear" compared to the same conditions encoded with H.264. But it doesn't and OBS doesn't show a "libx265" selection in the dropdown (like the "libx264").Ī inquiry at the OBS forum wasn't succesfull, those guys live in their "4K-Twtich-Youtube" world and claimed, that H.265 software encoding will not work because of the CPU load (although i explained the background and that i want to use very low bitrates).Īnyway, until my HDMI/H.265 encoder arrives from China, i searched and found a solution to create a H.265 encoded stream for the Pluto with software encoding. My expectation was, that in case of no HW support this encoder uses software encoding through "libx265" which FFMPEG should support.
![mediacoder x64 nvenc h.265 settings mediacoder x64 nvenc h.265 settings](https://www.mediacoderhq.com/images/sl_ktv_vod.png)
Now that i saw what H.265 can do, I tried to get the "nvenc_hevc" encoder working in OBS, but it seems, that this set needs hardware support, which my NVIDIA GT650M can't offer. Because of my limitations of RF power (about 20W) and dish size (about 73cm) I am bound to lower DATV bitrates (<=125kBit/s), but it works so far to send moving images via QO-100. The last weeks I played around with OBS, H.264 encoding and streaming via RTMP to my Pluto.