Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Add NVENC "Maximum encoded slice size in bytes" for H.264/HEVC codecs.
Date: Mon, 14 Aug 2023 23:20:34 +0200
Message-ID: <f60cf0cd-4b1d-2efc-92e7-b9639dc14577@rothenpieler.org> (raw)
In-Reply-To: <CAK+ULv7pYb-RBcd7ssvJHsNVkQ2foP4Pd0auNG+sVFnVyM27+g@mail.gmail.com>

On 14.08.2023 01:08, Kieran Kunhya wrote:
> On Sun, 13 Aug 2023 at 18:36, Timo Rothenpieler <timo@rothenpieler.org>
> wrote:
> 
>> Did you actually get this to work?
>> I'm testing it right now, and at stupid low values like 10 bytes I get a
>> working but heavily artifacted video.
>> If I set it to something like 2048 all I get is a full size video that
>> VLC decodes to a black screen.
> 
> 
> This could be a bug in hwaccel decode. Does it work in software decode?

Yeah, it works fine with software decode. At least in VLC.
Though surprisingly the bigger slice size limit looks significantly 
worse than the stupid low one of 10, it might have just ignored me?
_______________________________________________
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:[~2023-08-14 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  2:39 Водянников Александр
2023-07-27 12:08 ` Timo Rothenpieler
2023-07-27 13:22   ` Kieran Kunhya
2023-08-13 17:36 ` Timo Rothenpieler
2023-08-13 23:08   ` Kieran Kunhya
2023-08-14 21:20     ` Timo Rothenpieler [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=f60cf0cd-4b1d-2efc-92e7-b9639dc14577@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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