From: Roger Pack <rogerdpack2@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] avisynth as an internal filter, any objections?
Date: Mon, 22 Jul 2024 12:00:59 -0600
Message-ID: <CAL1QdWdwd5nU9TNenwMckfs+At8+jLczpJ7E__MYmmw0+=8gjQ@mail.gmail.com> (raw)
In-Reply-To: <fb47f4ab-d9e5-4705-8248-716a4a9de8fa@gmx.net>
On Thu, Jul 18, 2024 at 6:16 AM Stefan Oltmanns via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> AviSynth (or better VapourSynth) as filter sounds great, but is it possible?
> The reason why input plugins (like FFmpegSource2) in
> AviSynth/VapourSynth create an index file in a first pass is to allow
> frame-accurate random access to the video. Also the exact number of
> frames of a clip has to be known, because I could access that property
> in VapourSynth.
Yeah that's a good question, wonder how vsrawsource does it...
related: https://forum.videohelp.com/threads/404486-Ffmpeg-piped-as-source-to-avisynth
_______________________________________________
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:[~2024-07-22 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 1:04 Roger Pack
2024-07-17 11:40 ` Michael Niedermayer
2024-07-17 15:49 ` Kacper Michajlow
2024-07-17 22:30 ` Marth64
2024-07-17 22:34 ` Paul B Mahol
2024-07-17 22:37 ` Marth64
2024-07-18 10:21 ` Stefan Oltmanns via ffmpeg-devel
2024-07-18 14:22 ` Michael Niedermayer
2024-07-22 18:00 ` Roger Pack [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='CAL1QdWdwd5nU9TNenwMckfs+At8+jLczpJ7E__MYmmw0+=8gjQ@mail.gmail.com' \
--to=rogerdpack2@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