From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
Date: Thu, 14 Mar 2024 11:16:11 +0100
Message-ID: <171041137125.7287.13066847473884265473@lain.khirnov.net> (raw)
In-Reply-To: <eab6319d-9d3b-4766-81da-ac2d381a9478@gyani.pro>
Quoting Gyan Doshi (2024-03-13 08:49:52)
>
>
> On 2024-03-13 12:57 pm, Anton Khirnov wrote:
> > ffmpeg | branch: master | Anton Khirnov<anton@khirnov.net> | Mon Feb 19 10:27:44 2024 +0100| [a9193f7b7d65aafa326e25571c6672636a8ee3d2] | committer: Anton Khirnov
> >
> > fftools/ffmpeg: add loopback decoding
> ...
> > +E.g. the following example:
> > +
> > +@example
> > +ffmpeg -i INPUT \
> > + -map 0:v:0 -c:v libx264 -crf 45 -f null - \
> > + -dec 0:0 -filter_complex '[0:v][dec:0]hstack[stack]' \
> > + -map '[stack]' -c:v ffv1 OUTPUT
>
> Can you add an example showing the assignment of a specific decoder
> along with a lavc generic + private option to a loopbacked stream?
Sent a patch with some notes on this.
> Are there any limitations to loopback decoding e.g. would a vpx w/alpha
> encode be decoded back to a alpha pix fmt?
I don't know how vpx alpha works, was it a separate stream in the
demuxer or something like that?
Loopback decoders work exactly like normal decoders, except their
packets arrive from an encoder instead of a demuxer.
--
Anton Khirnov
_______________________________________________
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:[~2024-03-14 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313072725.7C7BA412605@natalya.videolan.org>
2024-03-13 7:49 ` Gyan Doshi
2024-03-14 10:16 ` Anton Khirnov [this message]
2024-03-15 4:12 ` Gyan Doshi
2024-03-21 10:22 ` Anton Khirnov
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=171041137125.7287.13066847473884265473@lain.khirnov.net \
--to=anton@khirnov.net \
--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