Re: [FFmpeg-devel] [PATCH] Complete rewrite of the "fps" video filter section. More accurate.

On 2020-04-27 01:04, Marton Balint wrote: On Sun, 26 Apr 2020, list+ffmpeg-...@jdlh.com wrote: From: Jim DeLaHunt This is a complete rewrite of the documentation for the "fps" video filter. It describes the filter's behaviour more clearly and accurately. I based the rewrite

Re: [FFmpeg-devel] [PATCH] Complete rewrite of the "fps" video filter section. More accurate.

On 2020-04-28 07:33, Josh de Kock wrote: On 27/04/2020 07:17, list+ffmpeg-...@jdlh.com wrote: From: Jim DeLaHunt This is a complete rewrite of the documentation for the "fps" video filter. It describes the filter's behaviour more clearly and accurately. I based the rewrite

Re: [FFmpeg-devel] [PATCH] Complete rewrite of the "fps" video filter section. More accurate.

acle for *FFmpeg* users. Traffic on the ffmpeg-users list proves this constantly. What do you have against removing this obstacle? What do you have against documentation which describes what the code actually does? I will go through all these comments and make a revised patch. Let's see

Re: [FFmpeg-devel] [PATCH v2] doc/filters.texi: complete rewrite of fps filter doc, v2.

On 2020-05-01 02:52, Carl Eugen Hoyos wrote: Am Fr., 1. Mai 2020 um 06:05 Uhr schrieb : From: Jim DeLaHunt Fix unclear wording and spelling mistakes based on review. Reduce overall word count by 11%. This is heavily misleading and definitely not ok. Oh, I get it! Are you saying that you

[FFmpeg-devel] Who is the FFmpeg documentation for? [was: Re: [PATCH v2] doc/filters.texi: complete rewrite of fps filter doc, v2.]

tree but built as part of the library, and links like that happen automatically.) Regards, Best regards, —Jim DeLaHunt, software engineer, Vancouver, Canada ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinf

Re: [FFmpeg-devel] [PATCH] lavf/fps: add cmd to force write buf frame

at change, then doesn't the patch cause the code to diverge further from the documentation? And long-term, doesn't that lead to problems? Best regards,    —Jim DeLaHunt, software engineer, Vancouver, Canada ___ ffmpeg-devel mailing lis

[FFmpeg-devel] Must I subscribe to ffmpeg-devel in order to submit a patch?

st archives, I'll have my answer. A clarification of the Submitting Patches documentation may be my second contribution. :-) Thank you for all the work you have put in to make this wonderful tool. I appreciate it. -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://

Re: [FFmpeg-devel] Must I subscribe to ffmpeg-devel in order to submit a patch?

at it is appreciated but not necessary to use a real name for contributing. On 2017-11-06 15:13, Lou Logan wrote: Hi, On Sat, 4 Nov 2017 21:52:28 -0700 Jim DeLaHunt wrote: Hello, ffmpeg developers: I'm gearing up to submit a patch, adding an FAQ to the documentation. According to <http

[FFmpeg-devel] I just ran FATE. Did the tests pass?

do I found out if my FATE tests passed? Thank you,      —Jim DeLaHunt -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada mobil

[FFmpeg-devel] [PATCH] Add FAQs about running in background

attempt to submit a patch. If I have done it wrong, please help me fix it. Thanks! --Jim DeLaHunt) ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] Add FAQs about running in background

Add two FAQs about running FFmpeg in the background. The first explains the use of the -nostdin option in a straightforward way. The second FAQ starts from a confusing error message, and leads to the solution, use of the -nostdin option. The purpose of the second FAQ is to attract web searches fro

Re: [FFmpeg-devel] [PATCH] Add FAQs about running in background

times easier (and more gratifying!) if done as a series of small improvements, rather than as one big change that drags on and on. Best regards,       —Jim DeLaHunt On 2017-11-14 03:25, Moritz Barsnick wrote: On Tue, Nov 14, 2017 at 02:59:34 -0800, Jim DeLaHunt wrote: +To run ffmpeg as a backg

Re: [FFmpeg-devel] FATE on multiple platforms

Thank you in advance for the clarification.     —Jim DeLaHunt -- --Jim DeLaHunt,j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada m

[FFmpeg-devel] [PATCH] Add FAQs about running in background (rev 2)

Add two FAQs about running FFmpeg in the background. The first explains the use of the -nostdin option in a straightforward way. Text revised based on review. The second FAQ starts from a confusing error message, and leads to the solution, use of the -nostdin option. The purpose of the second FAQ

[FFmpeg-devel] [PATCH] Ignore libavcodec/tests/mpeg12framerate, a test program

Add to libavcodec/tests/.gitignore an entry for test program libavcodec/tests/mpeg12framerate . Other similar test programs, e.g. jpeg2000dwt and dct, are ignored in a similar way. On initially checking out master, and doing "./configure" and "make clean", "git status" reports no untracked files.

[FFmpeg-devel] Source for http://ffmpeg.org/contact.html and documentation.html ?

contact.html and documentation.html different? And, are these top-level website pages open to patches from ordinary FFmpeg contributors? I had a look at the documentation.html, the repository, and https://trac.ffmpeg.org/wiki, and didn't find my answer there. Best regards,     --Jim DeL

Re: [FFmpeg-devel] Source for http://ffmpeg.org/contact.html and documentation.html ?

On 2017-11-18 14:53, Mark Thompson wrote: On 18/11/17 22:32, Jim DeLaHunt wrote: Hello, all: From what sources are the web pages http://ffmpeg.org/contact.html and https://ffmpeg.org/documentation.html generated? Sister web pages, like https://ffmpeg.org/ffmpeg.html and http://ffmpeg.org

[FFmpeg-devel] Subscribe to ffmpeg-cvslog for patch discussion? Really?

tion to read "ffmpeg-devel"?  And, to reword the "diffs of all commits are sent there" text to better describe ffmpeg-devel? Thanks in advance for helping me understand,   —Jim DeLaHunt -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/)

Re: [FFmpeg-devel] Subscribe to ffmpeg-cvslog for patch discussion? Really?

On 2017-11-20 05:18, Carl Eugen Hoyos wrote: 2017-11-19 11:27 GMT+01:00 Jim DeLaHunt : Looking in the ffmpeg-cvslog archives <http://ffmpeg.org/pipermail/ffmpeg-cvslog/>, it's clear that diffs of many, possibly all, commits are sent there. But I see no evidence there of discussion

[FFmpeg-devel] How to preserve @subheading directives, and styling, when compiling doc/developer.texi ?

ffmpeg.org. How can I compile /doc/developer.html from the FFmpeg sources so that: 1. the subheadings are included, and 2. the styling matches what is at ffmpeg.org/developer.html Thanks in advance for your help.  Best regards,        —Jim DeLaHunt -- --Jim DeLaHunt, j...@jdlh.com

[FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section

efactoring. However, making those improvements is a much bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt --- doc/developer.texi | 69 +- 1 file changed, 37 insertions(+), 32 deletions(

Re: [FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section

On 2017-11-21 15:40, Carl Eugen Hoyos wrote: 2017-11-21 22:41 GMT+01:00 Jim DeLaHunt: -@subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all commits are sent there and -reviewed by all the other developers. Bugs and possible improvements or

Re: [FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section

On 2017-11-21 16:05, Carl Eugen Hoyos wrote: 2017-11-22 0:59 GMT+01:00 Jim DeLaHunt: On 2017-11-21 15:40, Carl Eugen Hoyos wrote: 2017-11-21 22:41 GMT+01:00 Jim DeLaHunt: -@subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all commits are

Re: [FFmpeg-devel] [PATCH] Add FAQs about running in background (rev 2)

Ping. This patch responds to review comments, and there have been no further comments for a week. Could someone commit it please? Thanks,   —Jim DeLaHunt On 2017-11-15 00:43, Jim DeLaHunt wrote: Add two FAQs about running FFmpeg in the background. The first explains the use of the

Re: [FFmpeg-devel] [PATCH] Add FAQs about running in background (rev 2)

On 2017-11-22 08:54, Michael Niedermayer wrote: On Wed, Nov 15, 2017 at 12:43:30AM -0800, Jim DeLaHunt wrote: Add two FAQs about running FFmpeg in the background. The first explains the use of the -nostdin option in a straightforward way. Text revised based on review. The second FAQ starts

Re: [FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section

ribing subscription to ffmpeg-cvslog as "encouraged for the cited reasons, but not mandatory if you just want to send a patch here and there" as Derek puts it. I won't get to that edit until the weekend. Derek, thank you for your intervention. Best regards,      —Jim DeLaHunt, Vancouv

[FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section (v2)

bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt --- doc/developer.texi | 74 +++--- 1 file changed, 43 insertions(+), 31 deletions(-) diff --git a/doc/developer.texi b/doc/developer.texi in

Re: [FFmpeg-devel] How to preserve @subheading directives, and styling, when compiling doc/developer.texi ?

On 2017-11-21 01:20, Jim DeLaHunt wrote: Hello, doc maintainers: Could I get some help with the Texinfo compilation which produces /developer.html, please? Page <http://ffmpeg.org/developer.html> is a document which has some section headings displayed in green text, and some subhe

Re: [FFmpeg-devel] [PATCH] Refactor Developer Docs, update dev list section (v2)

rd parties". -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada mobile +1-604-376-8953 ___ ffmpeg-devel mailing li

[FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt : -@subsection Documentation/Other +@section Documentation/Other +@subheading Subscribe to the ffmpeg-devel mailing list. +It is important to be subscribed to the Of course it is important but I would much

[FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt : [...] + @subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all commits are sent there and -reviewed by all the other developers. Bugs and possible

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

On 2017-11-27 15:00, Carl Eugen Hoyos wrote: 2017-11-26 22:44 GMT+01:00 Jim DeLaHunt : So, how realistic is this concern about non-subscribers sending patches to ffmpeg-devel? Does it actually happen? This is very realistic afair. OK, and Lou Logan corroborates Carl Eugen: On 2017-11-27 15

Re: [FFmpeg-devel] Accurately describing ffmpeg-cvslog list [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

On 2017-11-27 15:03, Carl Eugen Hoyos wrote: 2017-11-26 22:57 GMT+01:00 Jim DeLaHunt : On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt : [...] + @subheading Subscribe to the ffmpeg-cvslog mailing list. -It is important to do this as the diffs of all

Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]

to the project. Thank you. Best regards,        —Jim DeLaHunt -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada mobile +1-604-376-8953

[FFmpeg-devel] [PATCH] Add doc on ffmpeg-devel, update on -cvslog list (v3)

factoring. However, making those improvements is a much bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt --- doc/developer.texi | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/doc/developer.tex

Re: [FFmpeg-devel] [PATCH] Add doc on ffmpeg-devel, update on -cvslog list (v3)

, I'm going to take this wonderful tool and convert some audio and video content from one format to another. -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada

Re: [FFmpeg-devel] [RFC] Type descriptors

represented as valid text. [1] https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274170.html [2] https://ffmpeg.org/pipermail/ffmpeg-devel/2020-December/274169.html [3] https://docs.python.org/3/howto/unicode.html This is an ambitious project. Good luck with it!    --Jim De

[FFmpeg-devel] Wow! SMPTE specs and journal articles, free (pandemic special)

uments are available. [1] https://www.smpte.org/free-standards-and-publications [2] http://ffmpeg.org/pipermail/ffmpeg-devel/2020-June/264781.html [3] http://ffmpeg.org/pipermail/ffmpeg-devel/2020-June/265336.html Enjoy!     —Jim DeLaHunt, software

Re: [FFmpeg-devel] Project orientation

t from the too little of the right unit tests. And so on. I wish you success as you ask yourself these big questions. I hope it helps you have a more pleasant time in this project. I am confident it will result in a better FFmpeg.   —Jim DeLaHu

Re: [FFmpeg-devel] Bad language on this mailing list

thority to deal with bad behaviour, will improve the situation.    —Jim DeLaHunt, software engineer, Vancouver, Canada ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit

Re: [FFmpeg-devel] [PATCH v1 1/3] doc/developer.texi: Improvements in "Submitting patches" section.

documentation about how to submit patches. Once these changes are accepted, you will have smoothed the way for many other developers.   —Jim DeLaHunt, software engineer, Vancouver, Canada ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https

Re: [FFmpeg-devel] Documentation: proposed changes in the structure

stacle easier or harder? I don't have strong feelings about this specific proposal. I do think that attention to high-level goals for FFmpeg documentation would add a lot of value to the project. Cheers, —Jim DeLaHunt [1] http://ffmpeg.org/pipermail/ffmpeg-user/2020-August/049718.html

Re: [FFmpeg-devel] [RFC] Built-in documentation API

On 2020-08-23 08:21, Nicolas George wrote: Since the idea of documentation built in the libraries seems popular, I have tried to outline an API to access it.… See the attached file […`documentation.c` omitted…]. The idea would be to have the build system convert the documentation into a C file

Re: [FFmpeg-devel] [RFC] Built-in documentation API

On 2020-08-23 08:21, Nicolas George wrote: Since the idea of documentation built in the libraries seems popular, I have tried to outline an API to access it.… See the attached file […`documentation.c` omitted…]. Some comments about the API outline itself, from `documentation.c`: struct AVD

Re: [FFmpeg-devel] Forward frame wall clock time from avdevice to HLS muxer

ailable for free download from the SMPTE web site[4] until 31 Dec 2020 (extended from 21 July 2020). You might want to get them now, for future reference. Please do update this list on what you do. I for one would like to take a look at it. Best regards, —Jim DeLaHunt, sof

Re: [FFmpeg-devel] Forward frame wall clock time from avdevice to HLS muxer

the difference from expected, and continue to update the PTS by the expected number of ticks. For some applications that might be an acceptable way to bury the error. What am I missing? Why, despite these workarounds, is a realtime clock not suitable as a PTS source?     —Jim DeLaHunt

Re: [FFmpeg-devel] Forward frame wall clock time from avdevice to HLS muxer

On 2020-08-28 00:19, Moritz Barsnick wrote: On Wed, Aug 26, 2020 at 23:52:58 -0700, Jim DeLaHunt wrote: Earlier this year, there were patches[3] which aimed to put linear timecodes in a format related to SMPTE 12M into a structure marked by a `AV_FRAME_DATA_S12M_TIMECODE` value. Maybe that

Re: [FFmpeg-devel] [PATCH] doc/decoders: Clear up description of ac3's drc_scale option

On 2020-08-28 15:39, Aman Verma wrote: Make clear that the value to -drc_scale is an exponentiating value, not a scaling factor. Also, document the default value. Signed-off-by: Aman Verma --- doc/decoders.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/decod

Re: [FFmpeg-devel] [PATCH] doc/decoders: Clear up description of ac3's drc_scale option

On 2020-08-29 15:10, Aman Verma wrote: ...As an aside, am I supposed to submit the revised patch in reply to this thread or should I submit it as a new thread? This is my first time contributing to a project that uses mailing lists. The instructions are at

Re: [FFmpeg-devel] [PATCH] libavformat/mxfenc: Add some () to attempt to workaround build issue on osx

ive in correcting the compile errors in libavformat/mxfenc.o, and then make fate ran successfully. -- --Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada mobile +1-6