On Sun, 12 Jun 2016, Nicolas George wrote:
Le quartidi 24 prairial, an CCXXIV, Marton Balint a écrit :
Maybe I am missing something, but as far as I see the alloc is due to the
alloc in ff_bsf_get_packet. We could create a similar function
ff_bsf_get_packet2(AVBSFContext *ctx, AVPacket *pkt)
Le quartidi 24 prairial, an CCXXIV, Marton Balint a écrit :
> Maybe I am missing something, but as far as I see the alloc is due to the
> alloc in ff_bsf_get_packet. We could create a similar function
> ff_bsf_get_packet2(AVBSFContext *ctx, AVPacket *pkt) which does not allocate
> a packet but
On Sat, 11 Jun 2016, Nicolas George wrote:
Instead of adding a totally new API, I suggest to use a "container"
bitstream filter called 'list', which will instantiate the "child" bitstream
filters and pump the packets through them.
Thanks to the N:M nature of the new BSF api, this should be
Le primidi 21 prairial, an CCXXIV, Marton Balint a écrit :
> My GSOC student Jan is working on improving the tee muxer, and as a side
> project he is also working on converting the tee muxer to the new BSF API.
>
> I have checked his WIP patches, and it seems to me that developing some API
>
On 08/06/2016 06:34 p.m., Marton Balint wrote:
Hi All,
Please comment, thanks,
Be careful that : in Windows do not currently parse well if you need to
use them in a path, like F:/filter/ or Z:/movie. They are parsed as F
and /filter/ and Z and /movie/ respectively.
Hi All,
My GSOC student Jan is working on improving the tee muxer, and as a side
project he is also working on converting the tee muxer to the new BSF API.
I have checked his WIP patches, and it seems to me that developing some
API which we can use for BSF chains would be really useful not
