From: Niklas Haas <ffmpeg@haasn.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/3] lavc/h274: fix PRNG definition
Date: Thu, 28 Sep 2023 21:18:08 +0200
Message-ID: <20230928211808.GD106730@haasn.xyz> (raw)
In-Reply-To: <CABLWnS-Qc_kTPPrDG_ui2sfUZOwFFNx7nz1-wh2Zwx5tffmieQ@mail.gmail.com>
On Thu, 28 Sep 2023 12:03:08 -0400 Vittorio Giovara <vittorio.giovara@gmail.com> wrote:
> On Thu, Sep 28, 2023 at 11:08 AM Niklas Haas <ffmpeg@haasn.xyz> wrote:
>
> > On Wed, 27 Sep 2023 21:07:55 +0200 Michael Niedermayer <
> > michael@niedermayer.cc> wrote:
> > > where can i find the text describing this that you refer to ?
> >
> > It is in SMPTE RDD 5 (DOI 10.5594/SMPTE.RDD5.2006), you can find it on
> > the usual places.
> >
>
> Could it maybe be mentioned in the commit log? Or documented in a comment
> (not familiar with the file, apologies if it's already so)
Hi,
it is mentioned in the commit message attached to the initial
implementation of this file, and also linked multiple times throughout
the source code.
_______________________________________________
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:[~2023-09-28 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 13:56 Niklas Haas
2023-09-27 13:56 ` [FFmpeg-devel] [PATCH 2/3] lavc/h274: correct grain DB indices Niklas Haas
2023-09-27 13:56 ` [FFmpeg-devel] [PATCH 3/3] lavc/h274: fix comment (cosmetic) Niklas Haas
2023-09-27 14:10 ` [FFmpeg-devel] [PATCH 1/3] lavc/h274: fix PRNG definition Niklas Haas
2023-09-27 19:07 ` Michael Niedermayer
2023-09-28 15:07 ` Niklas Haas
2023-09-28 16:03 ` Vittorio Giovara
2023-09-28 19:18 ` Niklas Haas [this message]
2023-09-28 18:53 ` Michael Niedermayer
2023-09-28 19:17 ` Niklas Haas
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=20230928211808.GD106730@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