On Wed, Feb 05, 2025 at 03:47:19PM +0100, Lynne wrote:
> Fixes 7187eadf8c0f0c640f1d23811c55fad0cba60aa5
>
> The issue is that while avctx->pix_fmt is synchronized between
> threads, f->pix_fmt was not.
>
> Fixes fate-vsynth1-ffv1-2pass10 with THREADS=2.
> ---
> libavcodec/ffv1dec.c | 1 +
> 1 fi
On 05/02/2025 17:26, Lynne wrote:
On 05/02/2025 15:51, James Almer wrote:
On 2/5/2025 11:47 AM, Lynne wrote:
Fixes 7187eadf8c0f0c640f1d23811c55fad0cba60aa5
The issue is that while avctx->pix_fmt is synchronized between
threads, f->pix_fmt was not.
Fixes fate-vsynth1-ffv1-2pass10 with THREADS=
On 05/02/2025 15:51, James Almer wrote:
On 2/5/2025 11:47 AM, Lynne wrote:
Fixes 7187eadf8c0f0c640f1d23811c55fad0cba60aa5
The issue is that while avctx->pix_fmt is synchronized between
threads, f->pix_fmt was not.
Fixes fate-vsynth1-ffv1-2pass10 with THREADS=2.
Can confirm "make fate-vsynth{
On 2/5/2025 11:47 AM, Lynne wrote:
Fixes 7187eadf8c0f0c640f1d23811c55fad0cba60aa5
The issue is that while avctx->pix_fmt is synchronized between
threads, f->pix_fmt was not.
Fixes fate-vsynth1-ffv1-2pass10 with THREADS=2.
Can confirm "make fate-vsynth{1,2,3,_lena} THREADS=2" (as well as highe
