Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/flacenc: Enable sample rates > 655350 Hz
Date: Tue, 15 Nov 2022 22:56:16 +0100
Message-ID: <20221115215616.GC1783292@pb2> (raw)
In-Reply-To: <CADQbU68CYZQx0h5Noi7WiWtfJt9m8vsbNaAkmK=LSEzDmNzy6Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2716 bytes --]

On Tue, Nov 15, 2022 at 05:14:26PM +0100, Martijn van Beurden wrote:
> Op ma 31 okt. 2022 om 19:33 schreef Martijn van Beurden <mvanb1@gmail.com>:
> >
> > Op ma 31 okt. 2022 om 17:58 schreef Derek Buitenhuis
> > <derek.buitenhuis@gmail.com>:
> > >
> > > It is interesting that the IETF RFC and the Xiph spec disagree on whether this is allowed.
> > >
> >
> > The Xiph spec also says the IETF spec is better, and it remains as
> > historical reference and overview :)
> >
> > > The Xiph spec says:
> > >
> > >     Sample rate in Hz. Though 20 bits are available, the maximum sample rate is limited by the
> > >     structure of frame headers to 655350Hz. Also, a value of 0 is invalid.
> > >
> > > The RFC just says:
> > >
> > >    Sample rate in Hz.
> > >
> >
> > The spec as it is on the FLAC website (which is being "preserved") is
> > wrong. I don't know how this came to be, I think it was at first
> > poorly worded and later incorrectly fixed. See this commit:
> > https://github.com/xiph/flac/commit/96534bb5f35eb9c2f6f393dc470625e9c74df1a5
> > The text as it was before that commit doesn't make any sense, the text
> > as it is after the commit is not correct either.
> >
> > The issue here is that FLAC has a sample rate in the streaminfo
> > metadata block, at the very start of the file. That one can
> > accommodate sample rates up to 2^20-1. The frame headers repeat the
> > sample rate every frame and can only accommodate up to 655350Hz, but
> > they can also reference the streaminfo metadata block. Because of the
> > possibility to reference that 20 bit number, it is possible to store
> > sample rates up to 1048575Hz. You can see this patch only touches the
> > encoder: the FFmpeg decoder has already been equipped to deal with
> > this since its inception in 2004.
> >
> > There is some kind of limitation to sample rates above 655350Hz, or
> > samplerates between 65535Hz and 655350Hz that are not a multiple of 10
> > though: a FLAC file with such a sample rate cannot be multicast,
> > because a decoder receiving a multicast stream does not receive the
> > streaminfo metadata block, and thus cannot use it to figure out the
> > correct sample rate.
> >
> > Please let me know when this explanation falls short.
> >
> > Kind regards, Martijn van Beurden
> 
> Hi all,
> 
> With this email, I would like to renew the attention of the mailing
> list for this patch.

will apply

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2022-11-15 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 16:09 Martijn van Beurden
2022-10-31 16:58 ` Derek Buitenhuis
2022-10-31 18:33   ` Martijn van Beurden
2022-10-31 21:25     ` Derek Buitenhuis
2022-11-15 16:14     ` Martijn van Beurden
2022-11-15 21:56       ` Michael Niedermayer [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=20221115215616.GC1783292@pb2 \
    --to=michael@niedermayer.cc \
    --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