[Libav-user] [FFmpeg-user] RTMP issue

william keeling williamkeeling at hotmail.com
Sat Oct 31 00:54:01 EET 2020

I think the stream is ok -- I have used the same program to write to protocol file: and then uploaded that to youtube with no issue.

Is that a good enough test the the stream format?
From: Libav-user <libav-user-bounces at ffmpeg.org> on behalf of Devin Heitmueller <dheitmueller at kernellabs.com>
Sent: Friday, October 30, 2020 10:33 AM
To: This list is about using libavcodec, libavformat, libavutil, libavdevice and libavfilter. <libav-user at ffmpeg.org>
Cc: FFmpeg user questions <ffmpeg-user at ffmpeg.org>
Subject: Re: [Libav-user] [FFmpeg-user] RTMP issue

On Thu, Oct 29, 2020 at 5:54 PM william keeling <williamkeeling at hotmail.com<mailto:williamkeeling at hotmail.com>> wrote:
> I still have not found a solution for this issue.  I wonder if I need to use avio_open2 (not avio_open).  Avio_open2 takes AVDictionary of options as a parameter.  Does anyone know how to find any documentation of the options that an available for the RTMP protocol?

Have you confirmed that the H.264 stream produced by the hardware encoder can actually be decoded by Youtube?  Some of these hardware encoders use non-standard/less-common options that might cause problems with a streaming service.  Since you're using "-vcodec copy" you're essentially just passing through the NAL stream from the hardware encoder unmodified.

I would suggest trying it with an H.264 stream that isn't the output of the hardware encoder, just to see if this is really a problem with the RTMP as opposed to the H.264 stream contained within it.


Devin J. Heitmueller - Kernel Labs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ffmpeg.org/pipermail/libav-user/attachments/20201030/35d32953/attachment.html>

More information about the Libav-user mailing list