On Fri, Feb 13, 2015 at 02:43:13PM +, Kevin Wheatley wrote:
Hi,
currently when writing ACLR atoms to .mov's there is a 'corruption'
caused by the function mov_write_avid_tag() writing an additional 4
bytes of zero's. this is potentially then followed by other atoms colr
and pasp.
Hi,
currently when writing ACLR atoms to .mov's there is a 'corruption'
caused by the function mov_write_avid_tag() writing an additional 4
bytes of zero's. this is potentially then followed by other atoms colr
and pasp. Looking at the specifications it appears this 4 bytes is
supposed to occur
OK I'll proceed with that.
Thanks
Kevin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Fri, Feb 13, 2015 at 04:34:37PM +, Kevin Wheatley wrote:
On Fri, Feb 13, 2015 at 3:06 PM, Michael Niedermayer michae...@gmx.at wrote:
On Fri, Feb 13, 2015 at 02:43:13PM +, Kevin Wheatley wrote:
what difference does the terminator make ?
does it improve compatibility with other
On Fri, Feb 13, 2015 at 3:06 PM, Michael Niedermayer michae...@gmx.at wrote:
On Fri, Feb 13, 2015 at 02:43:13PM +, Kevin Wheatley wrote:
what difference does the terminator make ?
does it improve compatibility with other software ?
I believe there are some versions of Apple's Final Cut
I've rebased the patch against current master, it is a lot of FATE
changes due to the extra 4 bytes...
It should now merge appropriately, see https://github.com/FFmpeg/FFmpeg/pull/110
Please let me know if anything needs tweaking
Thanks
Kevin
___
