On 27-07-2025 01:36, Mark Filipak wrote:
On 26/07/2025 19.17, Mark Filipak wrote:
PREFACE: It appears that FFmpeg is slipping into command mode, taking
the next couple letters from stdin, and interpreting them. That screws
up the remaining script of course.
Note: This is using Gyan's latest git build.
Workaround: Use 'start ffmpeg' instead of 'ffmpeg'. That causes the two
invocations to run in separate terminal sessions (but note that they
then run concurrently instead of sequentially).
I will not submit this as a bug until it's been replicated.
I'm told I need to be more explicit...
Q: Is there anyone who would like to replicate this issue and then reply
to the list so I can submit it to the bug list (that has entries that
are two decades old)?
Thank you for your attention.
--Mark.
Cannot replicate as I do not have Windows anymore, but...
From my own experience when I used batch scripting in Windows (and when
using Windows in general).
File creation (from stdin) is slow on Windows and my guess is this, when
creating a file from stdin and invoking a command directly after this
creation, that relies on the crated file you might need to pause until
the file has been created. Otherwise the stdin might also be used by the
started command in the same session.
Using start needs Windows to create a new session for the job and this
gives time for the file creation to complete and stdin is not in the
same session as the invoked program
Should you want to run ffmpeg sequentially use start /wait
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
