From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
Date: Fri, 15 Mar 2024 09:42:41 +0530
Message-ID: <db6e3830-53ed-44b1-9b4a-50cef159da37@gyani.pro> (raw)
In-Reply-To: <171041137125.7287.13066847473884265473@lain.khirnov.net>
On 2024-03-14 03:46 pm, Anton Khirnov wrote:
> Quoting Gyan Doshi (2024-03-13 08:49:52)
>
>> 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?
The encoder attaches the coded alpha as side data to the packet. Only a
couple of containers support this SD.
The demuxer, in turn, attaches the alpha as SD upon export.
> Loopback decoders work exactly like normal decoders, except their
> packets arrive from an encoder instead of a demuxer.
In terms of syntax, do all LB streams have to be specified in the first
output? Does that output muxer have to be null, or can those packets be
routed to both output and LB? Regards, Gyan
_______________________________________________
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-15 4:12 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
2024-03-15 4:12 ` Gyan Doshi [this message]
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=db6e3830-53ed-44b1-9b4a-50cef159da37@gyani.pro \
--to=ffmpeg@gyani.pro \
--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