On Tue, Mar 03, 2015 at 10:28:26AM +0100, Robert Krüger wrote:
> On Mon, Mar 2, 2015 at 6:56 PM, Mark Reid wrote:
>
> > On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger wrote:
> >
> > > On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid wrote:
> > >
> > > > On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger
>
On Mon, Mar 2, 2015 at 6:56 PM, Mark Reid wrote:
> On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger wrote:
>
> > On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid wrote:
> >
> > > On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger
> > wrote:
> > >
> > > > Currently the product name that ends up in mxf files
On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger wrote:
> On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid wrote:
>
> > On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger
> wrote:
> >
> > > Currently the product name that ends up in mxf files muxed using the
> new
> > op
> > > atom muxer is "OP1A muxer" whic
On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid wrote:
> On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger wrote:
>
> > Currently the product name that ends up in mxf files muxed using the new
> op
> > atom muxer is "OP1A muxer" which is misleading. Attached patch changes
> > that.
> >
> > __
On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger wrote:
> Currently the product name that ends up in mxf files muxed using the new op
> atom muxer is "OP1A muxer" which is misleading. Attached patch changes
> that.
>
> ___
> ffmpeg-devel mailing list
> ffm
Currently the product name that ends up in mxf files muxed using the new op
atom muxer is "OP1A muxer" which is misleading. Attached patch changes that.
mxf_opatom_product_name.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
