#9811: filter 'zscale=transfer=linear' fails with "code 2050: active window must
be positive"
-------------------------------------+------------------------------------
             Reporter:  rminnema     |                    Owner:  (none)
                 Type:  defect       |                   Status:  reopened
             Priority:  normal       |                Component:  avfilter
              Version:  git-master   |               Resolution:
             Keywords:  zimg,zscale  |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------
Changes (by BoKK):

 * keywords:  zimg,zscale,transfer => zimg,zscale
 * status:  closed => reopened
 * resolution:  fixed =>

Comment:

 It seems something is happening again, or at least something that seems
 related to zscale and threads used, somehow.
 I'm reopening this because I am guessing it's related so I see no point in
 opening a separate report for now.

 {{{
 ffmpeg -i test.mkv -vf zscale=size=1920x1080 -c:0 libx265 test_out.mkv  >>
 ffmpeg.exe crash
 ffmpeg -i test.mkv                           -c:0 libx265 test_out.mkv  >>
 OK
 ffmpeg -i test.mkv -vf scale=1920:1080       -c:0 libx265 test_out.mkv  >>
 OK

 Crash error is 'Exception Processing Message 0xc0000005 – Unexpected
 parameters'
 }}}

 What makes it weirder this time is... it doesn't always happen.
 This would point to a software or hardware error but then it should also
 happen when zscale is not used and that's not happening.

 - Using zscale=scale > Error ''most of the times''.
 - NOT using zscale > No error, ever.

 To make it weirder, what mitigated the problem before, setting ''-threads
 2'', achieves just the opposite -- error now appear always.

 - Using zscale=scale  >  Error ~90% of the times.
 - Using zscale=scale + -threads 2  >  Error 100% of the times.


 If I had to guess, I'd say this behaviour looks like some floating point
 rounding error... but I'm no programmer so that's just what it is, a
 guess.



 I'm uploading a test file, 'test_file_BOKK_20220701.mkv'.
 I suppose few people will be able to reproduce the issue... but it is
 happening nonetheless.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9811#comment:17>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to