Re: [FFmpeg-user] Help in improving the documentation is always welcome? [was: write output of find_rect to a file?]

On 2020-07-12 14:07, Carl Eugen Hoyos wrote: …The size of such a change [to the documentation] often gives a good indication of its usefulness. That rule of thumb might apply in some cases, especially where the current documentation is so close to the peak of perfection that any step is

Re: [FFmpeg-user] Documentation of chromanr filter

Am Sa., 11. Juli 2020 um 19:58 Uhr schrieb Carl Zwanzig : > > On 7/11/2020 1:39 AM, Paul B Mahol wrote: > > Can you elaborate what you tried and what failed? > > Why does it matter??? I believe you misunderstand that the only limiting factor of FFmpeg development is time, therefore reacting

Re: [FFmpeg-user] Help in improving the documentation is always welcome? [was: write output of find_rect to a file?]

Am So., 12. Juli 2020 um 22:14 Uhr schrieb Jim DeLaHunt : > > On 2020-07-12 05:21, Moritz Barsnick wrote: > > > …(Help in improving the documentation is always welcome…. Useful help in improving the documentation is welcome. The size of such a change often gives a good indication of its

Re: [FFmpeg-user] Help in improving the documentation is always welcome? [was: write output of find_rect to a file?]

On 2020-07-12 05:21, Moritz Barsnick wrote: …(Help in improving the documentation is always welcome…. I wish it were so, Moritz. But in my experience, improving the documentation is not always welcome. For example: and

[FFmpeg-user] Transcode udp stream

I am with a volunteer emergency service organization and a novice ffmpeg user. We would like to transcode & stream real time udp ts mpeg2 video (no audio) from a LAN IP address to my PC localhost via rtsp mp4. From the localhost I will re-stream via another application. Can someone help me get

Re: [FFmpeg-user] write output of find_rect to a file?

On Sat, Jul 11, 2020 at 14:52:43 -0700, Hans Carlson wrote: > > The above command works fine, but is it possible to print the number of > > the frame instead of the timestamp? > I might be wrong, but I believe you need to infer the frame number based > on where it appears in the output. Given