[FFmpeg-user] Spontaneously slipping into command mode

2025-07-27 Thread Mark Filipak
This is a serious post about a serious issue -- restarted due to distracting responses. The best way to see and replicate the problem is to run this script (which creates three AC3s and a FOO.TXT on c:\): ffmpeg -y -f lavfi -i anullsrc=channel_layout=2:sample_rate=48000 -t 240.0 -c ac3 "c:\file1.

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Ferdi Scholten
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 gi

Re: [FFmpeg-user] Spontaneously slipping into command mode

2025-07-27 Thread Mark Filipak
On 27/07/2025 16.51, Jim DeLaHunt wrote: > Mark: > > On 2025-07-27 09:42, Mark Filipak wrote: >> This is a serious post about a serious issue -- restarted due to >> distracting responses. >> >> The best way to see and replicate the problem is to run this script >> (which creates three AC3s and a F

Re: [FFmpeg-user] Spontaneously slipping into command mode

2025-07-27 Thread Ferdi Scholten
On 28-07-2025 02:18, Jim DeLaHunt wrote: On 2025-07-27 15:45, Mark Filipak wrote: On 27/07/2025 16.51, Jim DeLaHunt wrote: ...I understand that FFmpeg routinely monitors stdin while running... Oh, yes, of course. But-- But-- But my understanding is that > redirects to stdout. I'm not sending

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Mark Filipak
Hi, Reino, this is off-list. set _JOB_=c:\work\MISS PETTIGREW LIVES FOR A DAY [2007] set _DELAY2CH_=%_JOB_%DELAY2CH.ac3 set _DELAY6CH_=%_JOB_%DELAY6CH.ac3 set _SOURCEa0_=%_JOB_%a0.ac3 set _SOURCEa1_=%_JOB_%a1.ac3 set _DELAYEDa0_=%_JOB_%DELAYEDa0.ac3 set _DELAYEDa1_=%_JOB_%DELAYEDa1.ac3 echo ffconc

Re: [FFmpeg-user] Spontaneously slipping into command mode

2025-07-27 Thread Jim DeLaHunt
On 2025-07-27 15:45, Mark Filipak wrote: On 27/07/2025 16.51, Jim DeLaHunt wrote: ...I understand that FFmpeg routinely monitors stdin while running... Oh, yes, of course. But-- But-- But my understanding is that > redirects to stdout. I'm not sending anything to stdin. ...So, (?). You are

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Rob Hallam
On Sun, 27 Jul 2025, 15:21 Mark Filipak, wrote: > Hi, Reino, this is off-list. > This off list reply came to the list FYI > ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Mark Filipak
On 27/07/2025 10.53, Rob Hallam wrote: > On Sun, 27 Jul 2025, 15:21 Mark Filipak, wrote: > >> Hi, Reino, this is off-list. >> > > This off list reply came to the list FYI Yes, I see. Well, TBird sometimes does surprising things, eh? It did not indicate that it was going to send to ffmpeg-user,

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Mark Filipak
On 27/07/2025 07.00, Reino Wijnsma via ffmpeg-user wrote: > Hello Mark, > > On 2025-07-27T01:17:51+0200, 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 sc

Re: [FFmpeg-user] Spontaneously slipping into command mode

2025-07-27 Thread Jim DeLaHunt
Mark: On 2025-07-27 09:42, Mark Filipak wrote: This is a serious post about a serious issue -- restarted due to distracting responses. The best way to see and replicate the problem is to run this script (which creates three AC3s and a FOO.TXT on c:\): ffmpeg -y -f lavfi -i anullsrc=channel_lay

Re: [FFmpeg-user] It appears that FFmpeg is slipping into command mode

2025-07-27 Thread Reino Wijnsma via ffmpeg-user
Hello Mark, On 2025-07-27T01:17:51+0200, 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. You do realize this is totally off-topic for this mailin