From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] avfilter/adelay - interactive commands
Date: Tue, 18 Jan 2022 09:23:04 +0100
Message-ID: <CAPYw7P7EtAusTbLfgNisSjXzHgObqMcTVVFYPrmNXY4Y8=+JJg@mail.gmail.com> (raw)
In-Reply-To: <CAKEaJ+H1ngwdP3G7w=JWcvx_U4Z0iBS_zKca+HLTah6K6-qm9w@mail.gmail.com>
On Mon, Jan 17, 2022 at 11:02 PM deiwo deiwo <deiwo101@gmail.com> wrote:
> Hello,
> I would like to ask if it makes sense to implement ZeroMQ interactive
> commands for the adelay filter, from the performance and memory point of
> view.
> If it does make sense then is it possible to malloc/free/realloc memory
> within the command processing function? Can it cause noticeable delays in
> the stream outputs?
>
> I am new to the ffmpeg development so I am sorry if this kind of question
> does not belong to this mailing list.
>
>
I fail to see how that would work. Please elaborate your idea.
> Thanks for the response,
> David L
> _______________________________________________
> 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".
>
_______________________________________________
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-01-18 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:02 deiwo deiwo
2022-01-18 8:23 ` Paul B Mahol [this message]
2022-01-18 9:09 ` deiwo deiwo
2022-01-18 17:10 ` deiwo deiwo
2022-01-18 17:38 ` Paul B Mahol
2022-01-18 17:58 ` deiwo deiwo
2022-01-18 18:25 ` Paul B Mahol
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='CAPYw7P7EtAusTbLfgNisSjXzHgObqMcTVVFYPrmNXY4Y8=+JJg@mail.gmail.com' \
--to=onemda@gmail.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