


Also the Pluto transmit parameters I used ("PCR/PTS" and "PAT period" ar not really clear for me). The OBS settings can be found at the attachments.

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) 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.
#Obs what is ffmpeg 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.
#Obs what is ffmpeg windows#
FFMPEG 4.2.2 Windows 64-bit Static (the shared libs version will work too).

#Obs what is ffmpeg windows 10#
