[Libav-user] [FFmpeg-user] RTMP issue
David Ibbitson
david.ibbitson at gmail.com
Fri Oct 30 00:12:27 EET 2020
Also to set rtmp options I think you can just use av_dict_set on an
AVDictionary and pass that to avformat_write_header.
David
On Thu, Oct 29, 2020 at 2:54 PM william keeling <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?
> Thanks,
> William
> ------------------------------
> *From:* william keeling <williamkeeling at hotmail.com>
> *Sent:* Monday, August 24, 2020 6:33 PM
> *To:* FFmpeg user questions <ffmpeg-user at ffmpeg.org>;
> libav-user at ffmpeg.org <libav-user at ffmpeg.org>
> *Subject:* Re: [FFmpeg-user] RTMP issue
>
> I had avformat_network_init() in the code before and have found no
> difference with or without it. I added back and reran the test again with
> the verbose logging and received the same results and same log.
>
> pi at pi2cam:/userland/build/bin $ ./rcam -D dmic_sv -d 180 -q 30 -w 1920
> -h 1080 rtmp://a.rtmp.youtube.com/live2/<KEY>
> [tcp @ 0x199bb70] Starting connection attempt to 2607:f8b0:401a:26::8 port
> 1935
> [tcp @ 0x199bb70] Successfully connected to 2607:f8b0:401a:26::8 port 1935
>
> [aac @ 0x19a9620] Qavg: 116.588
> [AVIOContext @ 0x199dfd0] Statistics: 0 seeks, 12400 writeouts
>
> Thanks please keep the ideas coming,
> William
> ------------------------------
> *From:* ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> on behalf of Chris
> Miceli <chris at miceli.net.au>
> *Sent:* Monday, August 24, 2020 6:05 PM
> *To:* FFmpeg user questions <ffmpeg-user at ffmpeg.org>
> *Subject:* Re: [FFmpeg-user] RTMP issue
>
> Hi William,
>
> I'm by no means an expert on the matter but I tried having a look for you.
> At least one issue would be that you are not calling
> avformat_network_init() which
> is a requirement for any protocol which needs network [1]
>
> I would have tested and tried this for you, however I do not have the
> hardware laying around.
>
> I wish you the best of luck and let me know how it goes.
>
> [1] - libavformat/libavformat.h lines 40-41
>
> *Chris Miceli*
>
> On Mon, Aug 24, 2020 at 10:17 AM william keeling <
> williamkeeling at hotmail.com>
> wrote:
>
> > I added the AV_LOG_VERBOSE and got the following output:
> >
> > pi at pi2cam:/userland/build/bin $ ./rcam -D dmic_sv -d 5 -q 30 -w 1920 -h
> > 1080 rtmp://a.rtmp.youtube.com/live2/<KEY>
> > [tcp @ 0x18acb70] Starting connection attempt to 2607:f8b0:401a:7::8 port
> > 1935
> > [tcp @ 0x18acb70] Successfully connected to 2607:f8b0:401a:7::8 port 1935
> >
> > [aac @ 0x18ba620] Qavg: 118.451
> > [AVIOContext @ 0x18aefd0] Statistics: 0 seeks, 341 writeouts
> >
> >
> > If you can point me to an example of logging callback I will try and add
> > it if you think it will yield more useful information.
> >
> > Thanks in advance for your ideas and help,
> > William
> >
> > ________________________________
> > From: ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> on behalf of Moritz
> > Barsnick <barsnick at gmx.net>
> > Sent: Monday, August 24, 2020 9:25 AM
> > To: FFmpeg user discussions <ffmpeg-user at ffmpeg.org>
> > Subject: Re: [FFmpeg-user] RTMP issue
> >
> > Hi William
> >
> > On Mon, Aug 24, 2020 at 00:40:04 +0000, william keeling wrote:
> >
> > > My question is an issue with a program written to live stream to
> > > YouTube working is all modes other than rtmp live stream.
> >
> > For programming with the ffmpeg libav* libraries, you should usually
> > turn to the libav-user mailing list, But perhaps we can help.
> >
> > > finishes the stream is never processed by YouTube. When the stream is
> > > piped (pipe:1 URL) thru FFMPEG (demuxed and muxed only -- ffmpeg -i -
> > > -vcodec copy -acodec copy -f flv rtmp:<URL>) the live stream works
> > > without issues.
> >
> > At least that means that your content encoding, bit rate, number of
> > audio channels, and so on, are correct for YouTube. It's just the
> > muxing, or perhaps something like a flag or metadata.
> >
> > > So, I need to understand what FFMPEG command line is doing with rtmp:
> > URL that I am not doing with the FFMPEG API.
> > > My source code is at github.com/wkeeling63/rcam. Any ideas you have I
> > > would love to hear as I am stumped.
> >
> > Too bad ths only compiles on Raspberry Pi, so there's no way to
> > reproduce your muxing issue.
> >
> > Since you didn't provide a log callback using av_log_set_callback(),
> > shouldn't your application show all the usual ffmpeg/libav* log output
> > on stdout? Can you provide us with that ouptut? Raise the log level
> > with e.g. av_log_set_level(AV_LOG_VERBOSE), if required.
> >
> > Thanks,
> > Moritz
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/libav-user
>
> To unsubscribe, visit link above, or email
> libav-user-request at ffmpeg.org with subject "unsubscribe".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ffmpeg.org/pipermail/libav-user/attachments/20201029/f55158cb/attachment.html>
More information about the Libav-user
mailing list