[FFmpeg-devel] [PATCH 2/2] avisynth: Use av_packet_from_data instead of av_new_packet
michaelni at gmx.at
Thu Jan 9 18:38:14 CET 2014
On Thu, Jan 09, 2014 at 06:08:02AM -0500, Stephen Hutchinson wrote:
> On Wed, Jan 8, 2014 at 1:38 PM, wm4 <nfxjfg at googlemail.com> wrote:
> > Oh, nevermind my previous mail. I was reading the code wrong. So, as
> > said on the libav ML, apparently the problem is that av_new_packet()
> > overwrites other packet fields? Then why not set the fields after this
> > function, instead of using more complicated code? Anyway, nevermind me,
> > since there is no actual problem.
> The only reason I went with the solution I did was that I tried messing around
> with the stream_index stuff but it always ended in crashes. The issue with
> stream_index is that it shows up in avisynth_next_stream, and it also shows
> up in avisynth_read_seek (avisynth_read_packet calls avisynth_next_stream).
> My attempts to modify it in read_packet or read_seek just didn't work, and if it
> was supposed to be done individually in read_packet_video and
> read_packet_audio after the call to av_new_packet, I wasn't sure how to
> actually do that.
See/please review : [FFmpeg-devel] [PATCH] avformat/avisynth simplify packet allocation
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing more to fear from them, then he is always stirring up
some war or other, in order that the people may require a leader. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the ffmpeg-devel