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: Tue, 26 Apr 2022 03:06:35 +0000
Message-ID: <MWHPR08MB26559314D62577220A039AFE80FB9@MWHPR08MB2655.namprd08.prod.outlook.com> (raw)
In-Reply-To: <CA+anqdyNzW0v0CxjR=z6qBvXczv9z7aN4DX6BjmJM6AG0maung@mail.gmail.com>
Hi Hendrik,
Thank you for your feedback.
We will not merge it into master, maintain this patch on our side.
Regards
Janpriya
From: Hendrik Leppkes<mailto:h.leppkes@gmail.com>
Sent: 23 April 2022 02:36 PM
To: FFmpeg development discussions and patches<mailto: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 Fri, Apr 22, 2022 at 4:30 PM Malviya, Janpriya
<Janpriya_Malviya@bose.com> wrote:
>
> 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.
This sounds like you are solving a very specific problem in your
environment, coming from your software stack and setup, in a generic
library.
I fail to see the use for anyone else.
- Hendrik
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://urldefense.com/v3/__https://ffmpeg.org/mailman/listinfo/ffmpeg-devel__;!!I6pijIezNA!1yC7ZIMlMQc1s4je3aXXpcvFtzUbTATAg7GUrZcQjrPlJctsKBvQmJp9Ct517a6cWWrCmaeSFObq9RzZv3XGlIg$<https://urldefense.com/v3/__https:/ffmpeg.org/mailman/listinfo/ffmpeg-devel__;!!I6pijIezNA!1yC7ZIMlMQc1s4je3aXXpcvFtzUbTATAg7GUrZcQjrPlJctsKBvQmJp9Ct517a6cWWrCmaeSFObq9RzZv3XGlIg$>
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".
prev parent reply other threads:[~2022-04-26 3:06 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
2022-04-23 9:06 ` Hendrik Leppkes
2022-04-26 3:06 ` Malviya, Janpriya [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=MWHPR08MB26559314D62577220A039AFE80FB9@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