Re: [FFmpeg-user] FFmpeg interrupted (SIGSTOP signal) but pipewire shows its node is still running

2024-02-04 Thread gnusuario--- via ffmpeg-user
To be more precise, the node in pw-top is named after the library FFmpeg uses: Lavf60.16.100. In top all threads of ffmpeg are suspended (T). On Mon, 05 Feb 2024 00:33:20 GMT, gnusuario--- via ffmpeg-user ffmpeg-user@ffmpeg.org wrote: Forgot to mention that the FFmpeg version is the ome from

Re: [FFmpeg-user] FFmpeg interrupted (SIGSTOP signal) but pipewire shows its node is still running

2024-02-04 Thread gnusuario--- via ffmpeg-user
Forgot to mention that the FFmpeg version is the ome from Packman repositories. 6.1.1. On Mon, 05 Feb 2024 00:29:13 GMT, gnusuario--- via ffmpeg-user ffmpeg-user@ffmpeg.org wrote: I'm using FFmpeg to save screencasts to disk. I start FFmpeg and pause, continue or stop the screencast by

[FFmpeg-user] FFmpeg interrupted (SIGSTOP signal) but pipewire shows its node is still running

2024-02-04 Thread gnusuario--- via ffmpeg-user
I'm using FFmpeg to save screencasts to disk. I start FFmpeg and pause, continue or stop the screencast by sending signals to the process. I found out that in recorded screencasts with pauses the audio does not pause and continues as if FFmpeg was actively running. Because of that, after

Re: [FFmpeg-user] The Guild

2024-02-04 Thread David Niklas
Mark was good enough to privately email me and we were discussing this. He asked to take it to ffmpeg-user (below), so here you go. The only thing you missed (IMHO) was a bit of misunderstanding between us, which isn't included, as quotes or otherwise, herein. On Sun, 4 Feb 2024 15:28:36 -0500