On 17.10.2017 20:12, Nicolas George wrote:
Le sextidi 26 vendémiaire, an CCXXVI, Tobias Rapp a écrit :
This commit seems to break transcoding of some input files on machines with
a lot of CPU cores. See attached script that reproduces the problem
("-threads 32" is used to simulate the situation
Le sextidi 26 vendémiaire, an CCXXVI, Tobias Rapp a écrit :
> This commit seems to break transcoding of some input files on machines with
> a lot of CPU cores. See attached script that reproduces the problem
> ("-threads 32" is used to simulate the situation of a multi-core CPU).
>
> Sorry for
On 17.07.2017 16:19, Nicolas George wrote:
This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8.
The fate-ffm change is caused by field_order now being set
on the output format because the first frame arrives earlier.
The fate-mxf change is assumed to be the same.
Signed-off-by:
On 7/18/2017 3:48 PM, Nicolas George wrote:
> The reasons are exactly the same as the commit that it restores. I will
> include that and the other comments you request once I can access my
> work tree comfortably.
OK.
- Derek
___
ffmpeg-devel mailing
Le decadi 30 messidor, an CCXXV, Derek Buitenhuis a écrit :
> Doesn't say /why/ it's being reverted. Please update
> the commit message to do so.
The reasons are exactly the same as the commit that it restores. I will
include that and the other comments you request once I can access my
work tree
On 7/17/2017 3:19 PM, Nicolas George wrote:
> This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8.
>
> The fate-ffm change is caused by field_order now being set
> on the output format because the first frame arrives earlier.
> The fate-mxf change is assumed to be the same.
>
>
On 17.07.2017 16:19, Nicolas George wrote:
This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8.
The fate-ffm change is caused by field_order now being set
on the output format because the first frame arrives earlier.
The fate-mxf change is assumed to be the same.
Signed-off-by:
Le nonidi 29 messidor, an CCXXV, James Almer a écrit :
> You could mention this is also reverting
> e5bce8b4ce7b1f3a83998febdfa86a3771df96ce.
I had not noticed that the FATE changes were introduced in a separate
commit. I added this:
It also reverts e5bce8b4ce7b1f3a83998febdfa86a3771df96ce that
On 7/17/2017 11:19 AM, Nicolas George wrote:
> This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8.
You could mention this is also reverting
e5bce8b4ce7b1f3a83998febdfa86a3771df96ce.
>
> The fate-ffm change is caused by field_order now being set
> on the output format because the first
This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8.
The fate-ffm change is caused by field_order now being set
on the output format because the first frame arrives earlier.
The fate-mxf change is assumed to be the same.
Signed-off-by: Nicolas George
---
10 matches
Mail list logo