> This has to be something specific with your setup since there are
> (commercial) software which use avfoundation via ffmpeg for audio capture.
I can only imagine this means they're using a different version of FFmpeg. But
perhaps it's due to having something like Rogue Amoeba Loopback installed
> Ok, you may need to apply the patch at the below link as well.
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/5842508d-32f6-3073-8d1f-9ea8819d9...@mail.de/
The patch wouldn't apply, so I added the changes manually:
https://drive.proton.me/urls/W6F51WMXN0#A9OhuFyzpRQo
Yet, the problem persi
> Diff patch attached. Use `git apply` .
>
> Initially test with
>
> -f avfoundation \
> -audio_probe_wait 2 \
> -i ... \
>
>
> Check till values of 15 or so.
Thank you for the patch Gyan, I applied it, verified that the changes applied
in the libavdevice/avfoundation.m file, and rebuilt. Unf
> With AVFoundation, sometimes audio parameters aren't initialized at start of
> capture. The OS initializes the audio very shortly afterwards, but ffmpeg
> uses the parameters advertised in the beginning, which will be incorrect.
This definitely tracks with the behavior I'm witnessing.
> I wro
> I haven't seen another reply to your request, so I'm offering this one.
>
> You may want to try the HEAD version of ffmpeg. Sometimes the HEAD version
> provides a remedy for some issues, but not always.
> If it doesn't provide a solution, you can remove it, and reinstall the
> release versi
I'm currently attempting to move from a Windows audio/video capture rig to a
Mac. On Windows, I relied heavily on FFmpeg & DirectShow to capture clean
audio/video feeds from PCIe capture cards, as well as audio from my RME audio
interfaces. I was hoping that I could do the same on macOS with FFm
