Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
       [not found] <20240313072725.7C7BA412605@natalya.videolan.org>
@ 2024-03-13  7:49 ` Gyan Doshi
  2024-03-14 10:16   ` Anton Khirnov
  0 siblings, 1 reply; 4+ messages in thread
From: Gyan Doshi @ 2024-03-13  7:49 UTC (permalink / raw)
  To: FFmpeg development discussions and patches



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?

Are there any limitations to loopback decoding e.g. would a vpx w/alpha 
encode be decoded back to a alpha pix fmt?

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
  2024-03-13  7:49 ` [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding Gyan Doshi
@ 2024-03-14 10:16   ` Anton Khirnov
  2024-03-15  4:12     ` Gyan Doshi
  0 siblings, 1 reply; 4+ messages in thread
From: Anton Khirnov @ 2024-03-14 10:16 UTC (permalink / raw)
  To: FFmpeg development discussions and patches

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
  2024-03-14 10:16   ` Anton Khirnov
@ 2024-03-15  4:12     ` Gyan Doshi
  2024-03-21 10:22       ` Anton Khirnov
  0 siblings, 1 reply; 4+ messages in thread
From: Gyan Doshi @ 2024-03-15  4:12 UTC (permalink / raw)
  To: ffmpeg-devel



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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding
  2024-03-15  4:12     ` Gyan Doshi
@ 2024-03-21 10:22       ` Anton Khirnov
  0 siblings, 0 replies; 4+ messages in thread
From: Anton Khirnov @ 2024-03-21 10:22 UTC (permalink / raw)
  To: FFmpeg development discussions and patches

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-03-21 10:23 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20240313072725.7C7BA412605@natalya.videolan.org>
2024-03-13  7:49 ` [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: add loopback decoding Gyan Doshi
2024-03-14 10:16   ` Anton Khirnov
2024-03-15  4:12     ` Gyan Doshi
2024-03-21 10:22       ` Anton Khirnov

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