On Mon, Mar 2, 2015 at 6:56 PM, Mark Reid mindm...@gmail.com wrote:
On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger krue...@lesspain.de wrote:
On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid mindm...@gmail.com wrote:
On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger krue...@lesspain.de
wrote:
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 mindm...@gmail.com wrote:
On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger krue...@lesspain.de wrote:
On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid mindm...@gmail.com wrote:
On Sun,
On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid mindm...@gmail.com wrote:
On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger krue...@lesspain.de 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
On Mon, Mar 2, 2015 at 1:46 AM, Robert Krüger krue...@lesspain.de wrote:
On Sun, Mar 1, 2015 at 10:43 PM, Mark Reid mindm...@gmail.com wrote:
On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger krue...@lesspain.de
wrote:
Currently the product name that ends up in mxf files muxed using the
On Sun, Mar 1, 2015 at 4:06 AM, Robert Krüger krue...@lesspain.de 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
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
