On Thu, 9 Mar 2017 12:51:30 +0100
Michael Niedermayer wrote:
> On Thu, Mar 09, 2017 at 10:22:39AM +0100, wm4 wrote:
> > On Wed, 8 Mar 2017 15:44:36 +0100
> > Michael Niedermayer wrote:
> >
> > > On Wed, Mar 08, 2017 at 01:40:12PM +0100, wm4 wrote:
> > > > Side data are separate AVPacket fie
On Thu, Mar 09, 2017 at 10:22:39AM +0100, wm4 wrote:
> On Wed, 8 Mar 2017 15:44:36 +0100
> Michael Niedermayer wrote:
>
> > On Wed, Mar 08, 2017 at 01:40:12PM +0100, wm4 wrote:
> > > Side data are separate AVPacket fields for a reason. Merging side data
> > > requires reallocating all packets, is
On Wed, 8 Mar 2017 15:44:36 +0100
Michael Niedermayer wrote:
> On Wed, Mar 08, 2017 at 01:40:12PM +0100, wm4 wrote:
> > Side data are separate AVPacket fields for a reason. Merging side data
> > requires reallocating all packets, is complex, potentially clashes with
> > "actual" packet data (you
On Wed, 8 Mar 2017 15:44:36 +0100
Michael Niedermayer wrote:
> On Wed, Mar 08, 2017 at 01:40:12PM +0100, wm4 wrote:
> > Side data are separate AVPacket fields for a reason. Merging side data
> > requires reallocating all packets, is complex, potentially clashes with
> > "actual" packet data (you
On Wed, Mar 08, 2017 at 01:40:12PM +0100, wm4 wrote:
> Side data are separate AVPacket fields for a reason. Merging side data
> requires reallocating all packets, is complex, potentially clashes with
> "actual" packet data (you could probably come up with PCM data that
> looks like merged side dat
Side data are separate AVPacket fields for a reason. Merging side data
requires reallocating all packets, is complex, potentially clashes with
"actual" packet data (you could probably come up with PCM data that
looks like merged side data, or such), and could for example cause
trouble to people try
