From: Roman Arzumanyan <r.arzumanyan@visionlabs.ai>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/cuvidddec: Guess pixel format based on probed bit depth and chroma sampling
Date: Fri, 2 Aug 2024 17:05:00 +0300
Message-ID: <CAJZRZV=dM1hVRuBVd01QgyziBgQG0Mcxns-OXCV-GpZAV76SLA@mail.gmail.com> (raw)
In-Reply-To: <d562f5e7-5966-4fdd-9a26-8c69f1f73f15@rothenpieler.org>
Thanks a lot Timo !
Just for my own education: in my application I follow the usual sequence of
API calls to init hw device context and open the codec. What's the right
place to probe the input? I was under the impression that it's done within
avformat_find_stream_info().
пт, 2 авг. 2024 г. в 16:57, Timo Rothenpieler <timo@rothenpieler.org>:
> On 02/08/2024 15:31, Roman Arzumanyan wrote:
> > Hello world,
> >
> > Please find v2 of the previous patch attached.
> > Both bit depth and chroma sampling (420 and 444 as supported by Nvdec)
> are
> > now taken into account when selecting sw_pix_fmt.
>
> It's actually AV_PIX_FMT_YUV444P16 for both 10 and 12 bit, due to how
> the bits are aligned opposite to what ffmpeg expects in
> AV_PIX_FMT_YUV444P10.
>
> No need to resend for that, will ammend locally.
> _______________________________________________
> 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:[~2024-08-02 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 13:31 Roman Arzumanyan
2024-08-02 13:57 ` Timo Rothenpieler
2024-08-02 14:05 ` Roman Arzumanyan [this message]
2024-08-02 15:32 ` Timo Rothenpieler
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='CAJZRZV=dM1hVRuBVd01QgyziBgQG0Mcxns-OXCV-GpZAV76SLA@mail.gmail.com' \
--to=r.arzumanyan@visionlabs.ai \
--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