Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 [root@node228 ffmpeg]# git bisect log
 git bisect start
 # bad: [a0e4c41d086bbc32dfefef0b81ed0f59fe04d4ab] avfilter/vf_pseudocolor:
 add support for more formats
 git bisect bad a0e4c41d086bbc32dfefef0b81ed0f59fe04d4ab
 # good: [80154b1b3a0a9e83a9cbaff8b922440f60998128] Bump version for master
 after 3.4 branchpoint
 git bisect good 80154b1b3a0a9e83a9cbaff8b922440f60998128
 # bad: [ec703910af668b8deb8432d2953222385b821b2c] Merge commit
 '0f5ad12ba2b538cb329c507ecc914e06bfa70194'
 git bisect bad ec703910af668b8deb8432d2953222385b821b2c

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 don't know what number is a good reference
 0f5ad12ba2b538cb329c507ecc914e06bfa70194

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 this one ec703910af668b8deb8432d2953222385b821b2c

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 f...ck, same results... but I confused myself, it's the second revision
 after the 80154b1b
 not the first

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 anyhow I restarted a bisect again...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 I regressed the minor versions of all the 9 changes made on this revision

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Replying to [comment:52 zermok]:
 > I tested all 9 successfully, no issue when I regressed the minor
 versions :(
 I don't understand: Which unchanged version did you test first?
 And what did you change and what was the effect?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 a top -c shows
 28392 nobody20   0 1502412  91980  19280 R''' 100.0'''  0.3   2:35.52
 /usr/local/bin/ffmpeg -fflags +genpts -analyzeduration 0 -r 10 -threads 0
 -rtmp_conn S:pass Z: Z: Z:

 100% cpu for ever and no second pass to write the moov container

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 I tested all 9 successfully, no issue when I regressed the minor versions
 :(
 to be sure I recreated a new last git clone but the issue is there
 What a frustration :

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 ok I started to modify every change

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6521(avformat:open): HEIF support

[FFmpeg]

#6521: HEIF support
-+
 Reporter:  mateo|Owner:  mateo
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mov heif |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+
Changes (by james-vidmob):

 * cc: james@… (added)


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6521(avformat:open): HEIF support

[FFmpeg]

#6521: HEIF support
-+
 Reporter:  mateo|Owner:  mateo
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mov heif |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+

Comment (by james-vidmob):

 Cc

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 but... it only shows headers changed on this commit.
 does it mean thant maybe the next version of these libraries
 introduced the issue?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 If you click on the link that you posted in comment:39 you can see the
 nine trivial changes. Test if reverting some of them makes the bug go
 away.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6491(avfilter:open): interlace filter crash (was: FFMPEG crashes when trying to crop 1080p60 video to 1440x1080 and interlace)

[FFmpeg]

#6491: interlace filter crash
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avfilter
  Version:  git-master   |   Resolution:
 Keywords:  crash|   Blocked By:
  SIGSEGV interlace regression   |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 well, I'm absolutely not a C programmer, I'm at work for now too...
 what I suspect to see and where? which file?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 If you want to help, you can find out which of the changes in 80154b1b
 introduced the regression.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by zermok):

 bah, me too :)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Replying to [comment:8 oromit]:
 > Sorry, but nvenc is not x264, and the option works slightly differently,
 but similar enough to name it the same, as it does the same thing.
 And this is exactly the issue here.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:open): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  librtmp mov  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:   => librtmp mov regression
 * priority:  normal => important
 * status:  reopened => open


Comment:

 Sorry, I was hoping the resulting commit would show something useful.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 7bec3f78 looks good, no issue...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by oromit):

 Sorry, but nvenc is not x264, and the option works slightly differently,
 but similar enough to name it the same, as it does the same thing.
 If you use the names, like you should, the options are already compatible.
 Even on the x264 side of things the numerical values are not documented,
 only the values "ac" and "vlc" are, which are supported by nvenc to
 achieve the same thing.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Simply translate the values or rename the option.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 ok I try it now
 > (Sorry, but again, you point to a commit that is an unlikely candidate.)
 sorry I cannot help you ;), maybe a typo or a mistake happened.. who knows

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:closed): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by alexpigment):

 I confirmed the issue no longer occurs after updating to the newest macOS
 and building with --HEAD via brew. I'm not sure which of these two factors
 was at play, but I'm guessing this was addressed very recently. Apologies
 for the unnecessary opening/closing of an issue.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by oromit):

 The value 0 comes directly from the nvidia header.
 It's not part of the documented ffmpeg API or ABI. Only the names are.

 The only direct value ffmpeg makes up here is -1, which translates to "do
 not set this setting at all and leave it on whatever is in there by
 default".
 This option is similar do what x264 has, but not the same. I picked the
 const names for it to be compatible in most cases of normal usage.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 And 7bec3f78 also works fine? (Sorry, but again, you point to a commit
 that is an unlikely candidate.)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Replying to [comment:4 oromit]:
 > I don't see how this is a bug.
 > The option is called "coder", coder 0 has no specific meaning.

 I don't know how you come to this conclusion (and it contradicts the first
 comment): `0` is defined as auto for nvenc and as `cavlc` for everything
 (?) else, at least for x264, where the option-name originated. Please use
 the unstable-api period to fix this.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 sorry the log of the bad revision is  28MB, but I guess you already have
 it.
 yes, the version 3.4 works perfectly, I use it for now in production mode
 as I said the issue is if the rtmp live stream stops while ffmpeg is
 encoding
 so ffmpeg wait until the rtmp timeout and block for ever with 100% cpu
 after the last red message "Cannot read RTMP header".
 the version 3.4 release just write the 2pass moov and quit correctly.
 I attached the full console log of the version 3.4

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6491(avfilter:open): FFMPEG crashes when trying to crop 1080p60 video to 1440x1080 and interlace

[FFmpeg]

#6491: FFMPEG crashes when trying to crop 1080p60 video to 1440x1080 and 
interlace
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avfilter
  Version:  git-master   |   Resolution:
 Keywords:  crash|   Blocked By:
  SIGSEGV interlace regression   |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  crash SIGSEGV interlace => crash SIGSEGV interlace regression
 * priority:  normal => important


Comment:

 Can be considered a regression since 6f373d75 / 2e170405

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by oromit):

 I don't see how this is a bug.
 The option is called "coder", coder 0 has no specific meaning. You are
 supposed to select one by name.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(avcodec:reopened): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by cehoyos):

 * status:  closed => reopened
 * resolution:  invalid =>
 * version:  unspecified => git-master
 * component:  undetermined => avcodec


Comment:

 Yes, this is indeed a bug.
 How on earth can such things happen?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(undetermined:closed): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  nvenc|   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by jkqxz):

 Replying to [comment:1 cehoyos]:
 > No warning can be shown for unused output options.

 The option isn't unused, but the behaviour is exactly as expected.

 "-coder 0" indicates that the encoder should choose the mode
 automatically:
 

 


 The encoder then chooses to use CABAC, since it is more efficient and you
 haven't indicated any other constraint (e.g. profile) which would force it
 to use CAVLC instead.

 (It is generally recommended that you use named options rather than
 integer values where they are available.  See {{{ffmpeg -h
 encoder=nvenc_h264}}}.)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Then please also confirm that 3.4 works for you (and provide the command
 line including console output):
 http://ffmpeg.org/releases/ffmpeg-3.4.tar.bz2

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 I confirm that the last good one was the version 3.4
 version 80154b1b3a0a9e83a9cbaff8b922440f60998128
 I made git log to the first bad after this revision
 maybe it helps

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6477(undetermined:closed): NVENC: Warn explicitly when specific bit rate is out of range

[FFmpeg]

#6477: NVENC: Warn explicitly when specific bit rate is out of range
-+-
 Reporter:  alexpigment  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  nvenc|   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  nvenc, bitrate, failure => nvenc
 * status:  new => closed
 * resolution:   => needs_more_info


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6475(undetermined:closed): NVENC: -coder 0 parameter produces no error, but does not disable CABAC

[FFmpeg]

#6475: NVENC: -coder 0 parameter produces no error, but does not disable CABAC
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  nvenc|   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  nvenc, cabac, coder, intra => nvenc
 * status:  new => closed
 * resolution:   => invalid


Comment:

 No warning can be shown for unused output options.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:closed): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [comment:2 alexpigment]:
 > I followed the pre-defined guide for logging this issue

 This does not sound correct to me.

 > and spent quite a bit of time narrowing down the issue for you.

 Experience shows that this is not a good idea: Either you understand the
 issue, in this case send a patch fixing the bug to the FFmpeg development
 mailing list, do not open a ticket. Or you are unable to fix the issue,
 then please provide (only) the necessary information, don't try to narrow
 down the issue.

 > I'm not sure why you would take the time to respond to me that my ticket
 is not valid, when you could have spent less time simply copying and
 pasting the code under "How to reproduce" and verified that all relevant
 details have been included.

 You forgot the tenth commandment...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:closed): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  videotoolbox =>
 * status:  new => closed
 * version:  3.4 => unspecified
 * resolution:   => invalid


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [comment:37 zermok]:
 > It's what I noticed Cehoyos,
 > just compiled the next revision after the 3.4 release

 Not sure what you mean with "next revision": You have to test until git
 bisect tells you the change introducing the regression.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6877(undetermined:closed): Audio distortion with MP2 audio on HLS-streams. LAV splitter issue.

[FFmpeg]

#6877: Audio distortion with MP2 audio on HLS-streams. LAV splitter issue.
-+-
 Reporter:  max79|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * status:  reopened => closed
 * resolution:   => invalid


Comment:

 Sorry, this is the FFmpeg bug tracker, there is also a bug tracker for LAV
 Splitter.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:new): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  3.4  |  undetermined
 Keywords:   |   Resolution:
  videotoolbox   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by tmm1):

 * cc: ffmpeg@… (added)


Comment:

 I just tried ffmpeg master from the git repo and don't see this warning.
 So I believe this issue has already been fixed.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:new): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  3.4  |  undetermined
 Keywords:   |   Resolution:
  videotoolbox   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by alexpigment):

 I followed the pre-defined guide for logging this issue, and spent quite a
 bit of time narrowing down the issue for you. I'm not sure why you would
 take the time to respond to me that my ticket is not valid, when you could
 have spent less time simply copying and pasting the code under "How to
 reproduce" and verified that all relevant details have been included.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6877(undetermined:reopened): Audio distortion with MP2 audio on HLS-streams. LAV splitter issue.

[FFmpeg]

#6877: Audio distortion with MP2 audio on HLS-streams. LAV splitter issue.
-+-
 Reporter:  max79|Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by max79):

 * status:  closed => reopened
 * resolution:  needs_more_info =>


Comment:

 Why don't you hear sound effect like reverberation(echo)? Try a few new
 exapmles:
  [http://212.77.128.179:8089/www_mezhdunet/mezhdunet_hd/playlist.m3u8]
  [http://91.149.172.100:80/channel?id=23=demo=demo=.m3u8]
 My Samsung Smart-TV(with ForkPlayer widget) play all these streams without
 any sound issues and work through the same router as my PC!

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 It's what I noticed Cehoyos,
 just compiled the next revision after the 3.4 release
 and the issue happened don't know what to say...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6912(undetermined:new): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  3.4  |  undetermined
 Keywords:   |   Resolution:
  videotoolbox   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  macOS, videotoolbox, warning, quick sync, qsv => videotoolbox
 * component:  ffmpeg => undetermined


Comment:

 Please test current FFmpeg git head and provide the command line you
 tested together with the complete, uncut console output to make this a
 valid ticket.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #6912(ffmpeg:new): macOS - h264_videotoolbox encoder gives "No device available for encoder" warning

[FFmpeg]

#6912: macOS - h264_videotoolbox encoder gives "No device available for encoder"
warning
-+-
 Reporter:  alexpigment  | Type:  defect
   Status:  new  | Priority:  normal
Component:  ffmpeg   |  Version:  3.4
 Keywords:  macOS,   |   Blocked By:
  videotoolbox, warning, quick   |  Reproduced by developer:  0
  sync, qsv  |
 Blocking:   |
Analyzed by developer:  0|
-+-
 Summary of the bug:

 When encoding with the h264_videotoolbox encoder on macOS, a warning is
 given that says "No device available for encoder (device type videotoolbox
 for codec h264_videotoolbox)". Since this message is confusing to users
 and potentially sounds like a software fallback is being used or something
 isn't configured correctly, it should be removed. Issue is similar to
 #6492.

 How to reproduce:
 {{{
 % ffmpeg -f lavfi -i smptebars=size=1280x720:rate=30 -c:v
 h264_videotoolbox -color_range jpeg -pix_fmt nv12 -t 5 output.mp4
 }}}

 Confirmed on Macbook with Intel Core M CPU ; integrated GPU.

 ffmpeg 3.4.1
 built on 2017-12-11

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [comment:33 zermok]:
 > bad one starts at revision 912ceba61b0d45caa8ba8664ddf7b18e2121ddf3
 To elaborate why I am quite certain this is not the relevant commit:
 It is supposed to only change hardware decoding, even if something went
 wrong, it only changes vc1 decoding, which is not used by your command
 line.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [comment:32 zermok]:

 > git bisect start
 > git bisect bad

 In my (very long) experience, this is not a good idea:
 You should first compile current FFmpeg, confirm that your newly built
 binary allows to reproduce the issue you want to bisect, and only then run
 `git bisect bad`.

 > git bisect good 80154b1b

 Then you should compile and test the old version, only after you have
 confirmed that it is a good version, run `git bisect good`.

 So in your case, try something like:
 {{{
 $ make distclean
 $ git bisect reset
 $ git checkout master
 $ ./configure && make ffmpeg
 Test and verify a fail
 $ make distclean && git bisect bad
 $ git checkout 80154b1b
 $ ./configure && make ffmpeg
 Test and verify a success
 $ make distclean && git bisect good
 }}}
 and so on. If the first of above tests does not fail or if the second does
 not succeed, you verified that there is another issue.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 To completely rule out any kind of mistake, please provide command and
 console output for the working version bb4c9d0a

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 Ok I'm lucky (well at least)
 the issue comes just after the 3.4 80154b1b revision

 bad one starts at revision 912ceba61b0d45caa8ba8664ddf7b18e2121ddf3

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6909(avformat:new): vlc play properly, ffmpeg convert failed

[FFmpeg]

#6909: vlc play properly,ffmpeg convert failed
-+-
 Reporter:  tinybug  |Owner:
 Type:  defect   |   Status:  new
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mov edts |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  convert failed => mov edts regression
 * priority:  normal => important
 * component:  undetermined => avformat


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6911(avfilter:new): Drawbox & drawgrid replace source pixels if input or box color has alpha

[FFmpeg]

#6911: Drawbox & drawgrid replace source pixels if input or box color has alpha
+
 Reporter:  Gyan|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avfilter
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by Gyan):

 Patch at https://patchwork.ffmpeg.org/patch/6701/ introduces a new boolean
 option 'replace'. If set to `1`, `yes` or `true`, current behaviour is
 retained. With the default of `0`, `no` or `false`, the behaviour is as
 shown in the 'expected' image.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6910(undetermined:new): Broken audio timestamps with Hikvision recording

[FFmpeg]

#6910: Broken audio timestamps with Hikvision recording
-+-
 Reporter:  cehoyos  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  mpegps dts   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:   => mpegps dts


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6910(undetermined:new): Broken audio timestamps with Hikvision recording

[FFmpeg]

#6910: Broken audio timestamps with Hikvision recording
-+-
 Reporter:  cehoyos  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket6910/

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #6910(undetermined:new): Broken audio timestamps with Hikvision recording

[FFmpeg]

#6910: Broken audio timestamps with Hikvision recording
-+-
   Reporter:  cehoyos|  Owner:
   Type:  defect | Status:  new
   Priority:  normal |  Component:
Version:  git-   |  undetermined
  master |   Keywords:
 Blocked By: |   Blocking:
Reproduced by developer:  0  |  Analyzed by developer:  0
-+-
 http://ffmpeg.org/pipermail/ffmpeg-user/2017-December/038232.html
 A two-minute sample was uploaded, video works correctly, audio has
 completely broken timestamps (plays for exactly two minutes).
 {{{
 $ ffmpeg -i 1.mp4 -vn -f null -
 ffmpeg version N-89467-g0e52602 Copyright (c) 2000-2017 the FFmpeg
 developers
   built with gcc 6.3.0 (GCC)
   configuration: --enable-gpl
   libavutil  56.  5.100 / 56.  5.100
   libavcodec 58.  6.103 / 58.  6.103
   libavformat58.  3.100 / 58.  3.100
   libavdevice58.  0.100 / 58.  0.100
   libavfilter 7.  7.100 /  7.  7.100
   libswscale  5.  0.101 /  5.  0.101
   libswresample   3.  0.101 /  3.  0.101
   libpostproc55.  0.100 / 55.  0.100
 Input #0, mpeg, from '1.mp4':
   Duration: 02:07:57.93, start: 789.820800, bitrate: 9 kb/s
 Stream #0:0[0x1e0]: Video: h264 (Baseline), yuv420p(progressive),
 1920x1080, 25 fps, 25 tbr, 90k tbn, 50 tbc
 Stream #0:1[0x1c0]: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
 Stream mapping:
   Stream #0:1 -> #0:0 (pcm_mulaw (native) -> pcm_s16le (native))
 Press [q] to stop, [?] for help
 Output #0, null, to 'pipe:':
   Metadata:
 encoder : Lavf58.3.100
 Stream #0:0: Audio: pcm_s16le, 8000 Hz, mono, s16, 128 kb/s
 Metadata:
   encoder : Lavc58.6.103 pcm_s16le
 size=N/A time=02:07:57.92 bitrate=N/A speed=2.33e+05x
 video:0kB audio:1875kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: unknown
 }}}

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #6911(avfilter:new): Drawbox & drawgrid replace source pixels if input or box color has alpha

[FFmpeg]

#6911: Drawbox & drawgrid replace source pixels if input or box color has alpha
--+--
 Reporter:  Gyan  | Type:  defect
   Status:  new   | Priority:  normal
Component:  avfilter  |  Version:  git-master
 Keywords:|   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
 If the video input has an alpha component or the user specifies
 transparency in the box/grid-color, the drawbox and drawgrid filters
 replace the source pixels when painting the box or grid. This is almost
 always undesired. The alpha component of the user color is meant for
 blending the box/grid on top of the input. The input alpha should be left
 intact. Essentially, the filters draw a "hole" if alpha is involved. See
 attached `result-drawbox-src-with-no-alpha-existing.jpg`

 Inputs and outputs for

 `ffmpeg -i view.jpg -i window.png -lavfi
 "[1]drawbox=200:0:400:56:c=black@0.5:t=fill[win];[0][win]overlay" result-
 drawbox-src-with-alpha-existing.jpg`

 are attached, along with expected result.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 ok I got it. don't know why it didn't work before
 I did again
 git bisect start
 git bisect bad
 git bisect good 80154b1b
 and then
 git bisect good
 so it jumped to the next step

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 sorry but how to refresh the repository to the right revision
 after git bisect good 80154b1b ??

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6859(undetermined:reopened): 2pass moov not written and block ffmpeg if input live stream stops before

[FFmpeg]

#6859: 2pass moov not written and block ffmpeg if input live stream stops before
-+-
 Reporter:  zermok   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by zermok):

 ok thanks I started to test it now step by step

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6893(avutil:closed): Compile hwcontext_opencl.c: undefined reference to several OpenCL functions

[FFmpeg]

#6893: Compile hwcontext_opencl.c: undefined reference to several OpenCL 
functions
+---
 Reporter:  LigH|Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avutil
  Version:  git-master  |   Resolution:  invalid
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---

Comment (by LigH):

 Following this suggestion, I got a new library installed, but the issue
 persists for me.

 This libOpenCL.a contains symbols clCreateImage3D(@44) and
 clCreateImage2D(@36), but not clCreateImage(@28) alone (one of the symbols
 reported as missing while trying to link avutil-56.dll).

 The OpenCL.def used does not contain this export either. Snippet from the
 header (whole file will be attached):

 {{{
 ;
 ; Definition file of OpenCL.dll
 ; Automatic generated by gendef
 ; written by Kai Tietz 2008
 ;
 }}}

 Is this content specific to my hardware? If so, maybe that's the reason
 why my build is not as hardware independent as expected?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6893(avutil:closed): Compile hwcontext_opencl.c: undefined reference to several OpenCL functions

[FFmpeg]

#6893: Compile hwcontext_opencl.c: undefined reference to several OpenCL 
functions
+---
 Reporter:  LigH|Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avutil
  Version:  git-master  |   Resolution:  invalid
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => invalid


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6893(avutil:new): Compile hwcontext_opencl.c: undefined reference to several OpenCL functions

[FFmpeg]

#6893: Compile hwcontext_opencl.c: undefined reference to several OpenCL 
functions
+--
 Reporter:  LigH|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avutil
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--

Comment (by Gyan):

 I resolved this by deleting libOpenCL.a in local64/lib. This gets the
 script to generate a new static lib.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac