From: Philip Langdale <philipl@overt.org>
To: Manoj Bonda <mbonda@nvidia.com>
Cc: Ashish Roy <AROY@nvidia.com>, Hardy Doelfel <hdoelfel@nvidia.com>,
Aaron Plattner <aplattner@nvidia.com>,
Mandar Godse <mgodse@nvidia.com>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, Andy Ritger <ARitger@nvidia.com>
Subject: Re: [FFmpeg-devel] [PATCH] AV1 VDPAU hwaccel Decode support
Date: Wed, 22 Jun 2022 18:13:19 +0800
Message-ID: <20220622181319.3540a049@fluffy.lan> (raw)
In-Reply-To: <DM4PR12MB51020EA8D0110DEACA24E9C3A3B39@DM4PR12MB5102.namprd12.prod.outlook.com>
On Tue, 21 Jun 2022 02:45:21 +0000
Manoj Bonda <mbonda@nvidia.com> wrote:
> Hi Philip,
>
> The issue seems to be from MPV side rather than from ffmpeg patch.
> I was able to decode the clip Halo_AV1 properly bitmatching with
> nvcuvid output with ffmpeg + VDPAU.
>
> Please find the cmds I used to verify the same.
>
> ./ffmpeg -hwaccel vdpau -i
> /home/bondamanoj/VideoClips/AV1Clips/Halo_AV1.mp4 -y
> decoded_vdpau.yuv ./ffmpeg -hwaccel nvdec -i
> /home/bondamanoj/VideoClips/AV1Clips/Halo_AV1.mp4
> decoded_nvcuvid.yuv cmp decoded_vdpau.yuv
> ~/Downloads/ffmpeg-git2/FFmpeg/decoded_nvcuvid.yuv
>
> The same clip is dumped using mpv via cmd
> ./mpv --hwdec=vdpau-copy --o=Halo_dump_av1.yuv --of=rawvideo
> /home/bondamanoj/VideoClips/AV1Clips/Halo_AV1.mp4
>
> Is differing and is having corruption while playing.
>
>
> Thanks,
> ManojGupta.
Hi Manoj,
Ok. In that case, I guess it's reasonable to merge. I'm puzzled as to
the behaviour as other codecs work fine and other hwaccels used by the
same av1 decoder also work fine, so I don't see where there is room for
things to go wrong specifically in mpv specifically for this hwaccel.
Anyway, I'll merge it later this week.
Thanks,
--phil
_______________________________________________
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".
prev parent reply other threads:[~2022-06-22 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 13:15 ManojGuptaBonda
2022-05-17 4:46 ` Philip Langdale
2022-05-17 12:07 ` Manoj Bonda
[not found] ` <DM4PR12MB51026463462272DF753EDFAAA3D09@DM4PR12MB5102.namprd12.prod.outlook.com>
[not found] ` <20220519095432.7b07e873@fido7>
2022-06-21 2:45 ` Manoj Bonda
2022-06-22 10:13 ` Philip Langdale [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=20220622181319.3540a049@fluffy.lan \
--to=philipl@overt.org \
--cc=AROY@nvidia.com \
--cc=ARitger@nvidia.com \
--cc=aplattner@nvidia.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=hdoelfel@nvidia.com \
--cc=mbonda@nvidia.com \
--cc=mgodse@nvidia.com \
/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