Re: [FFmpeg-user] Read from pulseaudio - latency - how to fix!

On 01-09-2022 17:06, Thomas Seilund via ffmpeg-user wrote: Dear All I do live streaming and I need to pick up the audio from a microphone. I test latency like this: ffplay -f pulse -i "alsa_input.usb-Remo_Tech_Co.__Ltd._OBSBOT_Tiny-02.analog-mono" ffplay -f alsa -i default After

Re: [FFmpeg-user] Guidance on debugging a potential memory leak

On 9/1/22 13:26, Carl Eugen Hoyos wrote: Am Do., 1. Sept. 2022 um 21:16 Uhr schrieb Jorge Villatoro via ffmpeg-user : If you'd like to call it something else that's fine with me, but it's clear that the memory usage of the process escalates over time Which is not unusual for applications

Re: [FFmpeg-user] Guidance on debugging a potential memory leak

Am Do., 1. Sept. 2022 um 21:16 Uhr schrieb Jorge Villatoro via ffmpeg-user : > > If you'd like to call it something else that's fine with me, but it's clear > that the memory usage of the process escalates over time Which is not unusual for applications writing multimedia files. massif (another

Re: [FFmpeg-user] Guidance on debugging a potential memory leak

On Thu, Sep 1, 2022 at 11:24 AM Carl Eugen Hoyos wrote: > Am Do., 1. Sept. 2022 um 19:07 Uhr schrieb Jorge Villatoro via > ffmpeg-user : > > > I've tried running valgrind on this process for a while but I'm not > really > > sure how to decipher the results other than that there doesn't appear to

Re: [FFmpeg-user] Guidance on debugging a potential memory leak

On 9/1/2022 11:24 AM, Carl Eugen Hoyos wrote: If valgrind does not show a memory there is no memory leak. Probably; the tool is generally considered reliable but "never say never" (this is why we test the testing tools). A process may need more memory over time but that is not a leak.

Re: [FFmpeg-user] Guidance on debugging a potential memory leak

Am Do., 1. Sept. 2022 um 19:07 Uhr schrieb Jorge Villatoro via ffmpeg-user : > I've tried running valgrind on this process for a while but I'm not really > sure how to decipher the results other than that there doesn't appear to be > an obvious leak. If valgrind does not show a memory there is

[FFmpeg-user] Guidance on debugging a potential memory leak

Hi, I believe that I've stumbled across a slow memory leak in the QSV encoder, or possibly the underlying library I'm not really sure. I've been able to see a slow leak (~50MB/hr in the worst case) in ffmpeg processes performing an QSV encode where an identical configuration running a CUDA encode

[FFmpeg-user] Read from pulseaudio - latency - how to fix!

Dear All I do live streaming and I need to pick up the audio from a microphone. I test latency like this: ffplay -f pulse -i "alsa_input.usb-Remo_Tech_Co.__Ltd._OBSBOT_Tiny-02.analog-mono" ffplay -f alsa -i default After running one of the commands I can hear my own voice in my

[FFmpeg-user] Read from pulseaudio - latency - how to fix!

Dear All I do live streaming and I need to pick up the audio from a microphone. I test latency like this: ffplay -f pulse -i "alsa_input.usb-Remo_Tech_Co.__Ltd._OBSBOT_Tiny-02.analog-mono" ffplay -f alsa -i default After running one of the commands I can hear my own voice in my

Re: [FFmpeg-user] Need to Convert MP4 (or MKV) with AAC *and* AC-3 Audio to Multi-Rendition HLS (each with *both* audio streams)

Thank you Moritz! I will apply your advice and report back! On Thu, Sep 1, 2022, 02:26 Moritz Barsnick wrote: > Hi Clay, > > On Tue, Aug 30, 2022 at 18:51:13 -0400, Clay wrote: > > If you have a better way to achieve this, I am ***all ears***. > > Here is the code I have so far: > > I think

Re: [FFmpeg-user] Need to Convert MP4 (or MKV) with AAC *and* AC-3 Audio to Multi-Rendition HLS (each with *both* audio streams)

Hi Clay, On Tue, Aug 30, 2022 at 18:51:13 -0400, Clay wrote: > If you have a better way to achieve this, I am ***all ears***. > Here is the code I have so far: I think you need to fix your command line in various places: > ffmpeg -i ../InputFile-1920x804-24f.mp4 \ > -filter_complex