[FFmpeg-devel] [PATCH 2/2] avisynth: Use av_packet_from_data instead of av_new_packet

Stephen Hutchinson qyot27 at gmail.com
Thu Jan 9 12:08:02 CET 2014

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.

More information about the ffmpeg-devel mailing list