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: > > > > > > > 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 > > > > ffmpeg-devel@ffmpeg.org > > > > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > > > > > > > > > > This will change the CRC for > > > make fate-lavf-mxf_opatom > > > So the regression test needs to be updated as well > > > > > > > Ah, thank you. Didn't think of that. Is there any place where I can find > > docs on how to update fate hashes/crcs after a code change? I can see > > nothing at https://ffmpeg.org/fate.html or > > https://ffmpeg.org/developer.html > > > > > https://ffmpeg.org/fate.html#Makefile-variables > > make GEN=1 fate-lavf-mxf_opatom > > Thanks. Updated patch attached.
mxf_opatom_product_name.patch
Description: Binary data
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
