From: "Malviya, Janpriya" <Janpriya_Malviya@bose.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Banerjee, Debasmit" <Debasmit_Banerjee@bose.com>,
"White, Brian" <Brian_White@bose.com>,
"Van Iderstine, David" <David_Van_Iderstine@bose.com>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/mov.c: Added configuration flag to skip cover art atom while opening mov parser
Date: Fri, 22 Apr 2022 14:30:05 +0000
Message-ID: <MWHPR08MB26558B73D0FF495552BDE6E480F79@MWHPR08MB2655.namprd08.prod.outlook.com> (raw)
In-Reply-To: <3a78fe07-7a1f-817b-a1cf-604fd01b385f@gmail.com>
Hi Derek,
We require to add this configuration for the following reasons :
- We have our own pipeline mechanism to download & fetch audio data from source.
- We are using ffmpeg with custom IO callbacks for parsing & decoding fragmentedMP4 streams.
- Inside the custom IO read operation we are asking to download data from upstream elements.
- If any stream contains a cover page ( e.g. image file ) then the custom io read call-back issues a read request with large buffer size ( which is obvious ) . On the other side , our source downloader is unable to handle a data request of that size because of buffer constraints.
- To integrate FFmpeg with our architecture , we added this flag to issue skip for cover page from parsing
Let me know what you think.
Regards
Janpriya.
-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Derek Buitenhuis
Sent: 20 April 2022 06:54 PM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/mov.c: Added configuration flag to skip cover art atom while opening mov parser
On 4/20/2022 12:39 PM, Malviya, Janpriya wrote:
> Hello ffmpeg dev team,
> Please look in attached patch. while integrating FFmpeg we require to add "skip_cover_page" options to skip cover art atom from parsing for M4A / MP4 streams. By default values set as 0 ( False ) so it will not impact others.
Why?
- Derek
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://urldefense.com/v3/__https://ffmpeg.org/mailman/listinfo/ffmpeg-devel__;!!I6pijIezNA!1yHHDlJTrhDzhOKl0pzKhQjCdI7Xz9tLwffBUFRwvGDfkcYo9QqHko7Q5IXdWX3dcmxQgWIkgJL4x75FVs6l1MCHEuEzoIU8$
To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
_______________________________________________
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".
next prev parent reply other threads:[~2022-04-22 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:39 Malviya, Janpriya
2022-04-20 13:23 ` Derek Buitenhuis
2022-04-22 14:30 ` Malviya, Janpriya [this message]
2022-04-23 9:06 ` Hendrik Leppkes
2022-04-26 3:06 ` Malviya, Janpriya
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=MWHPR08MB26558B73D0FF495552BDE6E480F79@MWHPR08MB2655.namprd08.prod.outlook.com \
--to=janpriya_malviya@bose.com \
--cc=Brian_White@bose.com \
--cc=David_Van_Iderstine@bose.com \
--cc=Debasmit_Banerjee@bose.com \
--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