Hi,
There two version of decode video function with exactly same interface, one
defined as a function pointer in AVCodec struct, and avcodec_decode_video2.
What is the difference? is there any reason to use one over the other?
Thanks.
___
Libav-user
Hi Tim,
I've also been using intra-refresh to stream h264 video. The encoder
expects NAL units and, after encoding, the data is streamed in packets. Your
frame may or may not fit your encoded frame into a single packet, depending on
its size. At the receiving end, you should wait until
Hi Tim,
You should set aside enough buffer space to hold your data AND the
extra padding to it and ensure that the extra padding is set to zero. Something
like this would suffice :-
If you have copied the incoming data to your buffer, e.g memcpy(mPkt-data,
data, dataSize);
Then you
Found it, of course the problem is memory management.
It would seem that avfilter_copy_buf_props reuses the buffer, allocating
it to the target frame rather than copying it. Unfortunately if you then
call avfilter_unref_buffer before encoding frame the front of the buffer
gets trampled on,
While using the relatively new feature of source-specific multicast (patched
with
http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=75d339e044f9b87dd9aa4bdaee73b1a8323d4a15)
I tried giving 2 sources, instead of a single source. e.g.
You probably recognize that for IPv4 SSM your multicast must use a destination
address like 232.x.y.z
Per RFC4607
The benefits of source-specific multicast include:
Elimination of cross-delivery of traffic when two sources
simultaneously use the same source-specific destination
In data martedì 23 ottobre 2012 22:26:10, Stefano Sabatini ha scritto:
Does muxing.c work well?
I tried:
a.mpg
a.avi
a.mpeg
a.ogg
but nothing.
Can't reproduce here.
ffmpeg 1.0 works well.
--
www.denisgottardello.it
Skype: mrdebug
Videosurveillance and home automation!
Thanks Tony
On Wed, Oct 24, 2012 at 2:53 AM, Tony Glover t.glo...@nottingham.ac.uk wrote:
Hi Tim,
You should set aside enough buffer space to hold your data AND the
extra padding to it and ensure that the extra padding is set to zero.
Something like this would suffice :-
If you
Yeah I finally got the decoder working on a frame to frame basis and
got rid of the constant errors, at least as long as the stream is
good.
I'm confused what you mean by The encoder expects NAL units. I'm
piping raw video data (via ffmpeg using yuv4mpegpipe format) into x264
which seems to work.
Tony Glover T.Glover@... writes:
You should set aside enough buffer space to hold
your data AND the extra padding to it and ensure that
the extra padding is set to zero. Something like this
would suffice :-
If you have copied the incoming data to your buffer,
e.g memcpy(mPkt-data,
I'm using avcodec_decode_video2() to decode h264 frames encoded by
x264 one frame at a time. The stream is being transmitted over a lossy
physical layer wireless channel prior to decoding. I'm trying to
implement logic to re-display the last good picture if the current
picture fails to decode for
Tim Pitman tapitman11@... writes:
Is there a way to do what I'm trying to accomplish?
If you believe that FFmpeg's error concealment is not
optimal (it isn't for h264), you should try to improve
it, not work-around it.
And without knowing the theory, I am quite sure that
repeating the
12 matches
Mail list logo