From: Niklas Haas <ffmpeg@haasn.xyz> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Enhancement layers in FFmpeg Date: Mon, 1 Aug 2022 15:58:40 +0200 Message-ID: <20220801155840.GB106612@haasn.xyz> (raw) In-Reply-To: <DM8P223MB03652357059A5B176B29C88CBA9A9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Mon, 01 Aug 2022 13:17:12 +0000 Soft Works <softworkz@hotmail.com> wrote: > From my (rather limited) angle of view, my thoughts are these: > > When decoding these kinds of sources, a user would typically not only > want to do the processing in hardware but the decoding as well. > > I think we cannot realistically expect that any of the hw decoders > will add support for this in the near future. As we cannot modify > those ourselves, the only way to do such processing would be a > hardware filter. I think, the EL data would need to be attached > to frames as some kind of side data (or similar) and get uploaded > by the hw filter (internally) which will apply the EL data. If both the BL and the EL are separate fully coded bitstreams, then could we instantiate two independent HW decoder instances to decode the respective planes? > IMO it would be desirable when both of these things would/could be > done in a single operation. For Dolby Vision we have little choice in the matter. The EL application needs to happen *after* chroma interpolation, PQ linearization, IPT matrix application, and poly/MMR reshaping. These are currently all on-GPU processes in the relevant video output codebases. So for Dolby Vision that locks us into the design where we merely expose the EL planes as part of the AVFrame and leave it to be the user's problem (or the problem of filters like `vf_libplacebo`). An open question (for me) is whether or not this is required for SVC-H264, SHVC, AV1-SVC etc. > As long as it doesn't have its own format, its own start time, > resolution, duration, color space/transfer/primaries, etc.. > I wouldn’t say that it's a frame. Indeed, it seems like the EL data is tied directly to the BL data for the formats I have seen so far. So they are just like extra planes on the AVFrame - and indeed, we could simply use extra data pointers here (we already have room for 8). > > Best regards, > softworkz > _______________________________________________ > 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". _______________________________________________ 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:[~2022-08-01 13:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-01 11:24 Niklas Haas 2022-08-01 13:17 ` Soft Works 2022-08-01 13:58 ` Niklas Haas [this message] 2022-08-01 14:26 ` Soft Works 2022-08-01 13:45 ` Hendrik Leppkes
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=20220801155840.GB106612@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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