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

2018-05-23 Thread Jim DeLaHunt
ective 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

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

2017-12-05 Thread Jim DeLaHunt
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 Canada

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

2017-12-03 Thread Jim DeLaHunt
factoring. However, making those improvements is a much bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt <from.ffmpeg-...@jdlh.com> --- doc/developer.texi | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-)

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

2017-11-29 Thread Jim DeLaHunt
,    —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 mailing

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

2017-11-28 Thread Jim DeLaHunt
On 2017-11-27 15:03, Carl Eugen Hoyos wrote: 2017-11-26 22:57 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: [...] + @subheading Subscribe to the ffmpeg-cvslog

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

2017-11-27 Thread Jim DeLaHunt
On 2017-11-27 15:00, Carl Eugen Hoyos wrote: 2017-11-26 22:44 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: 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 corrob

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

2017-11-26 Thread Jim DeLaHunt
On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: [...] + @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 deve

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

2017-11-26 Thread Jim DeLaHunt
On 2017-11-26 03:42, Carl Eugen Hoyos wrote: 2017-11-26 9:31 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: -@subsection Documentation/Other +@section Documentation/Other +@subheading Subscribe to the ffmpeg-devel mailing list. +It is important to be subscribed to the Of

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

2017-11-26 Thread Jim DeLaHunt
ards others and third 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 ___ ffmp

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

2017-11-26 Thread Jim DeLaHunt
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

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

2017-11-26 Thread Jim DeLaHunt
bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt <from.ffmpeg-...@jdlh.com> --- doc/developer.texi | 74 +++--- 1 file changed, 43 insertions(+), 31 deletions(-) diff --git a/doc/developer

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

2017-11-23 Thread Jim DeLaHunt
ng describing 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 DeL

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

2017-11-22 Thread Jim DeLaHunt
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] Add FAQs about running in background (rev 2)

2017-11-22 Thread Jim DeLaHunt
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

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

2017-11-21 Thread Jim DeLaHunt
On 2017-11-21 16:05, Carl Eugen Hoyos wrote: 2017-11-22 0:59 GMT+01:00 Jim DeLaHunt<from.ffmpeg-...@jdlh.com>: On 2017-11-21 15:40, Carl Eugen Hoyos wrote: 2017-11-21 22:41 GMT+01:00 Jim DeLaHunt<from.ffmpeg-...@jdlh.com>: -@subheading Subscribe to the ffmpeg-cvslog

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

2017-11-21 Thread Jim DeLaHunt
On 2017-11-21 15:40, Carl Eugen Hoyos wrote: 2017-11-21 22:41 GMT+01:00 Jim DeLaHunt<from.ffmpeg-...@jdlh.com>: -@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

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

2017-11-21 Thread Jim DeLaHunt
efactoring. However, making those improvements is a much bigger and more difficult task. This change is "low hanging fruit". Signed-off-by: Jim DeLaHunt <from.ffmpeg-...@jdlh.com> --- doc/developer.texi | 69 +- 1 file changed, 37 i

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

2017-11-21 Thread Jim DeLaHunt
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

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

2017-11-20 Thread Jim DeLaHunt
On 2017-11-20 05:18, Carl Eugen Hoyos wrote: 2017-11-19 11:27 GMT+01:00 Jim DeLaHunt <from.ffmpeg-...@jdlh.com>: 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

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

2017-11-19 Thread Jim DeLaHunt
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/) m

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

2017-11-19 Thread Jim DeLaHunt
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] Source for http://ffmpeg.org/contact.html and documentation.html ?

2017-11-18 Thread Jim DeLaHunt
. Are 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 DeLaHunt

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

2017-11-17 Thread Jim DeLaHunt
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] [PATCH] Add FAQs about running in background (rev 2)

2017-11-15 Thread Jim DeLaHunt
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

Re: [FFmpeg-devel] FATE on multiple platforms

2017-11-14 Thread Jim DeLaHunt
w target 5 platforms regardless? This would be another good piece of information to put in the instructions on submitting patches. Thank you in advance for the clarification.     —Jim DeLaHunt -- --Jim DeLaHunt,j...@jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingua

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

2017-11-14 Thread Jim DeLaHunt
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 background

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

2017-11-14 Thread Jim DeLaHunt
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

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

2017-11-14 Thread Jim DeLaHunt
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] I just ran FATE. Did the tests pass?

2017-11-13 Thread Jim DeLaHunt
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 mobile +1-

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

2017-11-08 Thread Jim DeLaHunt
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 <from.ffm...@jdlh.com> wrote: Hello, ffmpeg developers: I'm gearing up to submit a patch, adding an FAQ to the documentation. According to

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

2017-11-05 Thread Jim DeLaHunt
rchives, 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://jdlh.com/)