Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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, 21 Mar 2024 11:22:54 +0100
Message-ID: <171101657473.7287.12529372893895699228@lain.khirnov.net> (raw)
In-Reply-To: <db6e3830-53ed-44b1-9b4a-50cef159da37@gyani.pro>

Quoting Gyan Doshi (2024-03-15 05:12:41)
> 
> 
> 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.

The packets arrive at the decoder exactly as the encoder produced them,
so if that's enough then it should work.

> > 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?

Actually they are not a part of the output, they form their own parsing
unit equivalent to -i/output. Probably this could be documented better.

> Does that output muxer have to be null, or can those packets be 
> routed to both output and LB?

The muxer can be anything, it does not know anything about loopback
decoders. The only limitation in this regard is that it is not
(currently) possible to avoid muxing entirely.

-- 
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".

      reply	other threads:[~2024-03-21 10:23 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
2024-03-21 10:22       ` Anton Khirnov [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=171101657473.7287.12529372893895699228@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