[FFmpeg-user] ffmpeg read from UDP/Port

Alex Lin op1031 at gmail.com
Tue Sep 23 01:33:14 CEST 2014


Hi Maziar,

>> I'm a bit confused here, first you said RTP and then you're using UDP in
your commands. Can you explain it to me?
The packets I am getting is H264 over RTP. Since RTP is a subset of UDP, so
I thought it would be okay to just let ffmpeg read the UDP packets.

>> Try playing directly from the stream with ffplay and see what will
happen. ffplay udp://192.168.1.200:50002/stream_name
I tried it and no luck either. When I try that, I get a lot of errors such
as:

[aac @ 0000000002ad5120] get_buffer() failed
[aac @ 0000000002ad5120] Inconsistent channel configuration.
[aac @ 0000000002ad5120] get_buffer() failed
[aac @ 0000000002ad5120] Inconsistent channel configuration.
[aac @ 0000000002ad5120] get_buffer() failed
[aac @ 0000000002ad5120] Inconsistent channel configuration.
[aac @ 0000000002ad5120] get_buffer() failed
[aac @ 0000000002ad5120] channel element 3.8 is not allocated
[aac @ 0000000002ad5120] Number of bands (31) exceeds limit (13).
[aac @ 0000000002ad5120] channel element 1.15 is not allocated
[aac @ 0000000002ad5120] Reserved bit set.
[aac @ 0000000002ad5120] channel element 3.9 is not allocated
[aac @ 0000000002ad5120] Reserved bit set.
    Last message repeated 1 times
[aac @ 0000000002ad5120] SBR was found before the first channel element.
[aac @ 0000000002ad5120] Sample rate index in program config element does
not ma
tch the sample rate index configured by the container.
[aac @ 0000000002ad5120] decode_pce: Input buffer exhausted before END
element f
ound
[aac @ 0000000002ad5120] Reserved bit set.
[aac @ 0000000002ad5120] channel element 2.15 is not allocated
[aac @ 0000000002ad5120] Reserved bit set.
    Last message repeated 1 times
[aac @ 0000000002ad5120] channel element 2.13 is not allocated
[aac @ 0000000002ad5120] Sample rate index in program config element does
not ma
tch the sample rate index configured by the container.
[aac @ 0000000002ad5120] Inconsistent channel configuration.
[aac @ 0000000002ad5120] get_buffer() failed
[aac @ 0000000002ad5120] channel element 3.1 is not allocated
[aac @ 0000000002ad5120] Dependent coupling is not supported together with
LTP
    Last message repeated 40 times
[aac @ 0000000002ad5120] Reserved bit set.
[aac @ 0000000002ad5120] Assuming an incorrectly encoded 7.1 channel layout
inst
ead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according
to t
he specification instead.
[aac @ 0000000002ad5120] channel element 1.11 is not allocated
[aac @ 0000000002ad5120] channel element 2.10 is not allocated
[aac @ 0000000002ad5120] channel element 3.11 is not allocated
[aac @ 0000000002ad5120] channel element 2.15 is not allocated
[aac @ 0000000002ad5120] channel element 1.3 is not allocated
[aac @ 0000000002ad5120] invalid band type
[aac @ 0000000002ad5120] SSR is not implemented. Update your FFmpeg version
to t
he newest one from Git. If the problem still occurs, it means that your
file has
 a feature which has not been implemented.
[aac @ 0000000002ad5120] If you want to help, upload a sample of this file
to ft
p://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list.
(ffmp
eg-devel at ffmpeg.org)
[aac @ 0000000002ad5120] channel element 2.3 is not allocated
[aac @ 0000000002ad5120] Number of scalefactor bands in group (14) exceeds
limit
 (12).

I am starting to think the packets which I am trying to record is not
supported by ffmpeg. Would like to get your opinion on that.

Thank you,
AL


On Wed, Sep 17, 2014 at 10:23 PM, Maziar Mehrabi <mmehrabi at abo.fi> wrote:

> Hi,
>
> I'm a bit confused here, first you said RTP and then you're using UDP in
> your commands. Can you explain it to me?
> Try playing directly from the stream with ffplay and see what will happen.
> ffplay udp://192.168.1.200:50002/stream_name
> I can capture and save from udp but the result is very noisy and faulty.
> Http seems to be better though.
> I also didn't use the -f mp4 options in my command. I think you also didn't
> mention the stream name in input for ffmpeg.
>
> BR,
> Maziar
>
>
> --
> Hälsningar,
> Maziar Mehrabi
>
> On Thu, Sep 18, 2014 at 2:26 AM, Alex Lin <op1031 at gmail.com> wrote:
>
> > Hi all,
> >
> > I am using Windows 7 64 bit, and I downloaded the 64 bit version of
> > ffmpeg: ffmpeg-20140916-git-b76d613-win64-static.7z
> >
> > I have spent the entire day experimenting with ffmpeg today but I haven't
> > quite figure out if ffmpeg is the right solution to my problem yet, so I
> > would like to get some opinions.
> >
> > I am receiving H264 encoded packets through RTP with sample rate of
> 90,000,
> > and I need to record these packets. The file format doesn't really matter
> > at this point.
> >
> > Currently, I have a server sending the H264 packets to port 50002 of my
> > machine (192.168.1.200), so I run the following ffmpeg command on my
> > machine:
> >
> > ffmpeg -i udp://192.168.1.200:50002 -f mp4 hello.mp4
> >
> > Then the following shows
> >
> > ffmpeg version N-66289-gb76d613 Copyright (c) 2000-2014 the FFmpeg
> > developers
> >   built on Sep 15 2014 22:11:04 with gcc 4.8.3 (GCC)
> >   configuration: --enable-gpl --enable-version3 --disable-w32threads
> > --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r
> > --enable-gnutls --enable-iconv --enable-libass --enable-libbluray
> > --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme
> > --enable-libgsm --enable-
> > libilbc --enable-libmodplug --enable-libmp3lame
> --enable-libopencore-amrnb
> > --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus
> > --enable-librtmp --enable-libschroedinger --enable-libsoxr
> > --enable-libspeex --enable-libtheora --enable-libtwolame
> > --enable-libvidstab --enable-libvo-aacenc --
> > enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx
> > --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265
> > --enable-libxavs --enable-libxvid --enable-decklink --enable-zlib
> >   libavutil      54.  7.100 / 54.  7.100
> >   libavcodec     56.  1.100 / 56.  1.100
> >   libavformat    56.  4.101 / 56.  4.101
> >   libavdevice    56.  0.100 / 56.  0.100
> >   libavfilter     5.  1.100 /  5.  1.100
> >   libswscale      3.  0.100 /  3.  0.100
> >   libswresample   1.  1.100 /  1.  1.100
> >   libpostproc    53.  0.100 / 53.  0.100
> >
> > The server starts sending video packets, and nothing happens on the
> command
> > prompt with the ffmpeg command.
> > The server stops sending video packets, and nothing happens still (I
> waited
> > for at least 5 minutes), so I pressed Ctrl+C, then I see this
> >
> > udp://192.168.1.200:50002: Invalid data found when processing input
> > Received signal 2: terminating.
> >
> > am I using ffmpeg correctly? and are the H264 packets I am receiving not
> > supported?
> > I have looked around and did not see any debug log generated by ffmpeg,
> so
> > I don't really know where else to look.
> > If it is necessary, I can provide a packet capture with the H264 packets.
> >
> > Thanks in advance.
> > AL
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>


More information about the ffmpeg-user mailing list