Github messages for voidlinux
 help / color / mirror / Atom feed
From: BlitDev <BlitDev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ffmpeg doesn't support rav1e encoder
Date: Sun, 29 Oct 2023 09:58:27 +0100	[thread overview]
Message-ID: <20231029085827.LT2dNezTv_iPpND1XyIk3AQ149H1Q9NkMAvHWCHx75c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46823@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

New comment by BlitDev on void-packages repository

https://github.com/void-linux/void-packages/issues/46823#issuecomment-1784039300

Comment:
> Is there a reason why you can't/don't want to use libsvtav1 instead?

I've tried to set the crf parameter, but it threw an error:
```
Codec AVOption crf (Select the quality for constant quality mode) specified for output file #0 (test-3.mkv) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
```

My command: ```ffmpeg -i source.mkv -c:v libsvtav1 -crf 30 test-3.mkv```
The crf is actually set at 50 (default value) although I set it at 30.

  parent reply	other threads:[~2023-10-29  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22  7:55 [ISSUE] ffmpeg doesn't support rav1e BlitDev
2023-10-28 14:09 ` ffmpeg doesn't support rav1e encoder mhmdanas
2023-10-28 14:09 ` mhmdanas
2023-10-28 14:09 ` mhmdanas
2023-10-29  8:58 ` BlitDev [this message]
2023-10-29 11:16 ` mhmdanas
2023-10-30 15:10 ` BlitDev
2023-10-30 15:20 ` BlitDev
2023-11-20 13:19 ` mhmdanas
2023-12-07  3:34 ` [ISSUE] [CLOSED] " ahesford
2023-12-07  3:34 ` ahesford

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=20231029085827.LT2dNezTv_iPpND1XyIk3AQ149H1Q9NkMAvHWCHx75c@z \
    --to=blitdev@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).