>
> Can't you instead create a new reference for the frame buffer? Or will
> making it non writable break things further into the process? It would
> save you a memcpy per frame.
Great idea. It works. Making it non-writable should be enough. I'm
submitting v3. Please take a look.
_
On 1/2/2018 12:03 PM, zhangjiejun1...@gmail.com wrote:
> From: Jiejun Zhang
>
> This fixes #6940
>
> Although undocumented, AudioToolbox seems to require the data supplied
> by the callback (i.e. ffat_encode_callback) being unchanged until the
> next time the callback is called. In the old imple
From: Jiejun Zhang
This fixes #6940
Although undocumented, AudioToolbox seems to require the data supplied
by the callback (i.e. ffat_encode_callback) being unchanged until the
next time the callback is called. In the old implementation, the
AVBuffer backing the frame is recycled after the frame
