Re: [FFmpeg-trac] #8766(documentation:new): find_rect documentation

[FFmpeg]

#8766: find_rect documentation
-+-
 Reporter:  mkoch|Owner:
 Type:  defect   |   Status:  new
 Priority:  minor|Component:
 |  documentation
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by mkoch):

 Replying to [comment:2 cehoyos]:
 > Please send your patch - made with `git format-patch` - to the FFmpeg
 development mailing list.
 > As you probably found out by now, suggestions for patches on this bug
 tracker are mostly ignored.

 That won't happen soon, because I haven't yet figured out how git works. I
 have seen the instructions at https://www.ffmpeg.org/git-howto.html but I
 understand almost nothing of it.

--
Ticket URL: 
FFmpeg 
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".

Re: [FFmpeg-trac] #8766(documentation:new): find_rect documentation

[FFmpeg]

#8766: find_rect documentation
-+-
 Reporter:  mkoch|Owner:
 Type:  defect   |   Status:  new
 Priority:  minor|Component:
 |  documentation
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * priority:  normal => minor
 * type:  enhancement => defect


Comment:

 Please send your patch - made with `git format-patch` - to the FFmpeg
 development mailing list.
 As you probably found out by now, suggestions for patches on this bug
 tracker are mostly ignored.

--
Ticket URL: 
FFmpeg 
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".

Re: [FFmpeg-trac] #8766(documentation:new): find_rect documentation

[FFmpeg]

#8766: find_rect documentation
-+-
 Reporter:  mkoch|Owner:
 Type:  enhancement  |   Status:  new
 Priority:  normal   |Component:
 |  documentation
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by mkoch):

 Also the meaning of the ‘xmin, ymin, xmax, ymax’ options is unclear and a
 better documentation is required. Does it mean the top left corner of the
 object image must be in the specified area, or does it mean the full
 object image must be in this area?

--
Ticket URL: 
FFmpeg 
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".

[FFmpeg-trac] #8766(documentation:new): find_rect documentation

[FFmpeg]

#8766: find_rect documentation
-+-
 Reporter:  mkoch| Type:
 |  enhancement
   Status:  new  | Priority:  normal
Component:   |  Version:  git-
  documentation  |  master
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 I suggest to add the following to the documentation of the find_rect video
 filter:

 -- If the input video contains multiple instances of the object, find_rect
 will find only one of them.
 -- threshold = 0.01 means only exact matches, threshold = 0.99 means
 almost everything matches
 -- find_rect writes the result to these internal variables:
lavfi.rect.wwidth of object
lavfi.rect.hheight of object
lavfi.rect.xx position of object
lavfi.rect.yy position of object
 -- If the threshold value isn't met, then these variables aren't written
 to.
 -- It is possible to write these variables to a file with ffprobe and
 -show_entries

 Examples section:

 Find the position of an object in each frame and write it to a log file:
 ffprobe -f lavfi movie=test.mp4,find_rect=object=object.pgm:threshold=0.3
 -show_entries
 frame=pkt_pts_time:frame_tags=lavfi.rect.x,lavfi.rect.y -of csv 1> log.csv


 Suggestion for improvement:

 Please make also the internal variable "best_score" available, so that it
 can be written to the log file as well.

--
Ticket URL: 
FFmpeg 
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".