On 29-07-2025 01:40, Mark Filipak wrote:
Mark, I get the impression that you are not hearing what people in this thread are trying to tell you.
On 2025-07-28 14:05, Mark Filipak wrote:
FFmpeg is clearly entering a command mode even though I'm not submitting any options that support command mode. FFmpeg listens to stdin and accepts commands all. the. time., unless you tell it not to by giving the `-nostdin` option. Thank you, Jim. Yes, I understand now. FFmpeg is not waiting for a specific command. It accepts _all_ stdin, no matter whether an option
On 28/07/2025 17.52, Jim DeLaHunt wrote: that expects commands is employed, or in fact whether there's any options at all, and it silently disposes of stdin that is not a command, and apparently continues to do so until stdin is empty. Oh, that's just *ducky*.
I was vaguely aware of FFmpeg commands but had no idea that they are so global and 'thoughtless', 'unthinking'. Wonderful! ;-(
What I have learned: To forevermore submit "start ffmpeg" instead of "ffmpeg".
Thanks again!--Mark.
PS: I don't believe it is Windows that is misbehaving. Not at all.
Both FFmpeg and the Windows Command prompt are behaving as designed. Both also offer ways to circumvent their intended behavior.