<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Is that a good enough test the the stream format?</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Libav-user <libav-user-bounces@ffmpeg.org> on behalf of Devin Heitmueller <dheitmueller@kernellabs.com><br>
<b>Sent:</b> Friday, October 30, 2020 10:33 AM<br>
<b>To:</b> This list is about using libavcodec, libavformat, libavutil, libavdevice and libavfilter. <libav-user@ffmpeg.org><br>
<b>Cc:</b> FFmpeg user questions <ffmpeg-user@ffmpeg.org><br>
<b>Subject:</b> Re: [Libav-user] [FFmpeg-user] RTMP issue</font>
<div> </div>
</div>
<div>
<div dir="ltr">On Thu, Oct 29, 2020 at 5:54 PM william keeling <<a href="mailto:williamkeeling@hotmail.com">williamkeeling@hotmail.com</a>> wrote:<br>
><br>
> 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? <br>
<br>
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.
<div><br>
</div>
<div>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.<br>
<br>
Devin<br>
<br>
-- <br>
Devin J. Heitmueller - Kernel Labs<br>
<a href="http://www.kernellabs.com">http://www.kernellabs.com</a></div>
</div>
</div>
</body>
</html>