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 fro
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 from a confusing error message,
> and leads t
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 -nostdi
2017-11-14 12:38 GMT+01:00 Jim DeLaHunt :
> Those are good comments. Thank you. I can see how to improve the wording.
> I could add them to my current branch, and submit a new patch.
Yes, this is what is expected.
Please do not top-post here, Carl Eugen
_
Moritz:
Those are good comments. Thank you. I can see how to improve the wording.
I could add them to my current branch, and submit a new patch. However,
I'd prefer to have the present patch approved, then submit a new patch
to make it even better. Editorial changes to docs are sometimes easie
On Tue, Nov 14, 2017 at 02:59:34 -0800, Jim DeLaHunt wrote:
> +To run ffmpeg as a background task, and prevent those input checks,
> +use the @url{ffmpeg.html#stdin-option, @code{-nostdin} option}
This is a bit misleading, as it does not make ffmpeg run as a
background task (the impression one may
