On 03/15/2012 05:20 PM, Luca Barbato wrote: > On 15/03/12 13:04, Anton Khirnov wrote: >> >> On Thu, 15 Mar 2012 07:22:07 -0700, Luca Barbato <lu_z...@gentoo.org> wrote: >>> On 3/15/12 5:40 AM, Anton Khirnov wrote: >>>> There is no reason for it to be public, it's only meant to be used >>>> internally. >>> >>> I'd be careful, I know that sometimes we suggest to use this function >>> directly as a workaround for the issues we have with the standard >>> interleave... >>> >> >> Are you sure you're not confusing it with av_write_frame()? >> > > Justin told me about trying that on irc when I was trying something in > that regard, not sure how often the issue cropped up. > > Surely it shouldn't be used (IF the normal interleave would work properly)
Also, using it now would skip the muxer interleave_packet() override. I don't think that was an issue at the time I suggested you try it out. I think having the choice of av_interleaved_write_frame() or av_write_frame() should be enough. -Justin _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
