> Would whoever wrote that actually identify themselves in their email?
> That would be quite helpful (as well as courteous).
Apologies, I've updated the name attached to this email, and will sign all
messages moving forward. I created a custom email with my domain for use with
this mailing list
On 6/14/2025 10:22 PM, FFmpeg via ffmpeg-user wrote:
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, or some other application. I tend to doubt it.
Would whoever wrote that actually identi
> 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
On 2025-06-15 08:37 am, FFmpeg via ffmpeg-user wrote:
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.
> 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
On 2025-06-06 01:43 pm, FFmpeg via ffmpeg-user wrote:
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 libavdevic
> 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
On 2025-06-04 03:20 am, FFmpeg via ffmpeg-user wrote:
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 definite
> 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
On 2025-06-01 05:58 am, FFmpeg via ffmpeg-user wrote:
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 interface
> On Jun 1, 2025, at 11:38 PM, Carl Zwanzig wrote:
>
> On 6/1/2025 8:27 PM, Huspnet wrote:
>> Mediainfo default response will show that with a command line such as:
>> mediainfo /path/to/mediafile
>
> Does that refer to the AVFoundation output? That's what I was referring to.
Of course. Also
On 6/1/2025 8:27 PM, Huspnet wrote:
Mediainfo default response will show that with a command line such as:
mediainfo /path/to/mediafile
Does that refer to the AVFoundation output? That's what I was referring to.
z!
___
ffmpeg-user mailing list
ffmp
> On Jun 1, 2025, at 3:53 PM, Carl Zwanzig wrote:
>
> delivering 44.1k when you want 48k. Not sure how you would verify that on a
> Mac.
Mediainfo default response will show that with a command line such as:
mediainfo /path/to/mediafile
L. Lee
__
I'm kind of wondering if AVFoundation is lying about the sample rate and
delivering 44.1k when you want 48k. Not sure how you would verify that
on a Mac.
Might also try moving "-ar 48000" to before the "-f" (or remove that
altogether and see what comes out).
Later,
z!
__
I believe you will find that the HEAD version differs from both "stable" and
"latest". If I'm wrong, I'm fairly sure that someone will correct me, but it
may be another day before such a message is sent to the list.
L. Lee
> On Jun 1, 2025, at 12:55 AM, FFmpeg via ffmpeg-user
> wrote:
>
> I
> 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 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
version as you did
17 matches
Mail list logo
