From: Thilo Borgmann <thilo.borgmann@mail.de> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v9 1/3] libavdevice/avfoundation.m: use AudioConvert, extend supported formats Date: Fri, 14 Jan 2022 19:10:11 +0100 Message-ID: <00e1cb09-fa15-0580-b5f6-4401c3f13cba@mail.de> (raw) In-Reply-To: <CABWZ6OT6yAU9P9_GjJ2GbaFRyVBVYrxXpqoN0GCgLit4FY9STw@mail.gmail.com> Am 14.01.22 um 18:57 schrieb Romain Beauxis: > Le ven. 14 janv. 2022 à 11:47, Thilo Borgmann <thilo.borgmann@mail.de> a écrit : >> >> Am 14.01.22 um 13:57 schrieb Marvin Scholz: >>> >>> >>> On 6 Jan 2022, at 15:24, Romain Beauxis wrote: >>> >>>> * Implement support for AudioConverter >>>> * Switch to AudioConverter's API to convert unsupported PCM >>>> formats (non-interleaved, non-packed) to supported formats >>>> * Minimize data copy. >>>> >>>> This fixes: https://trac.ffmpeg.org/ticket/9502 >>>> >>>> API ref: >>>> https://developer.apple.com/documentation/audiotoolbox/audio_converter_services >>>> >>>> Signed-off-by: Romain Beauxis <toots@rastageeks.org> >>>> --- >>>> This is the first patch of a series of 3 that fix, cleanup and enhance the >>>> avfoundation implementation for libavdevice. >>>> >>>> These patches come from an actual user-facing application relying on >>>> libavdevice’s implementation of avfoundation audio input. Without them, >>>> Avfoundation is practically unusable as it will: >>>> * Refuse to process certain specific audio input format that are actually >>>> returned by the OS for some users (packed PCM audio) >>>> * Drop audio frames, resulting in corrupted audio input. This might have been >>>> unnoticed with video frames but this makes avfoundation essentially unusable >>>> for audio. >>>> >>>> The patches are now being included in our production build so they are tested >>>> and usable in production. >>>> >>> >>> Hi, >>> >>> the patches are still corrupt and do not apply. >>> As stated earlier, please either use git send-email or attach the patch >>> to the mail instead of putting its contents in it, as apparently Mail.app >>> messes them up. >> >> Still the same for me. Do you use git send-email or git format-patch? > > Thanks for checking on this y'all and sorry about these complications. > > I used git format-patches. I might try git send-email or the github PR > bridge, that seems like a neat trick. github PR sounds like something you don't want. I use format-patch as well and attach the file (not sending via mail.app though). > > I'm working on a new revision of the patches, I discovered more issues > with audio conversion, possibly linked to bugs with the AudioConverter > API. > > I also discovered an API to do the conversion internally without > having to deal with manually reconverting. Hopefully, this also fixes > the issues we uncovered. > > Will post once we have done more testing. All in all, macos sound APIs > are pretty confusing and buggy around the edges it seems. Cool. -Thilo _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-01-14 18:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-06 14:24 Romain Beauxis 2022-01-14 12:57 ` Marvin Scholz 2022-01-14 17:46 ` Thilo Borgmann 2022-01-14 17:57 ` Romain Beauxis 2022-01-14 18:10 ` Thilo Borgmann [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=00e1cb09-fa15-0580-b5f6-4401c3f13cba@mail.de \ --to=thilo.borgmann@mail.de \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git