On 25.11.2014, at 10:01, Daniel Oberhoff wrote:
>> Am 24.11.2014 um 17:16 schrieb Reimar Döffinger :
>>
>>> On Mon, Nov 24, 2014 at 12:35:58PM +0100, Daniel Oberhoff wrote:
>>> inout -> filter1 -> filter2 -> output
>>>
>>> some threads processing frame n in the output (i.e. encoding), other
>>>
Von meinem iPhone gesendet
> Am 24.11.2014 um 17:16 schrieb Reimar Döffinger :
>
>> On Mon, Nov 24, 2014 at 12:35:58PM +0100, Daniel Oberhoff wrote:
>> inout -> filter1 -> filter2 -> output
>>
>> some threads processing frame n in the output (i.e. encoding), other threads
>> procesing frame n
On Mon, Nov 24, 2014 at 12:35:58PM +0100, Daniel Oberhoff wrote:
> inout -> filter1 -> filter2 -> output
>
> some threads processing frame n in the output (i.e. encoding), other threads
> procesing frame n+1 in filter2, others processing frame n+2 in filter1, and
> yet others processing frame n+
On Mon, Nov 24, 2014 at 3:35 AM, Daniel Oberhoff
wrote:
> Hi,
>
> From what I gather the filter graph is utilizing modern multicores by
> “striping” where filters support it, i.e. an image is divided in stripes
> and the filter gets called in separate threads for separate stripes.
In FFmpeg we ca
Hi,
>From what I gather the filter graph is utilizing modern multicores by
>“striping” where filters support it, i.e. an image is divided in stripes and
>the filter gets called in separate threads for separate stripes. I was
>wondering if there is or will be pipeline multuthreading, i.e. with a
