From: Martijn van Beurden <mvanb1@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/flacenc: add backward-compatible 32 bit-per-sample capability
Date: Sun, 19 Dec 2021 22:41:14 +0100
Message-ID: <CADQbU68cvsRbYnmdqiRc0Ltcyz0XWgrrdGKfNuabcak11QyJng@mail.gmail.com> (raw)
In-Reply-To: <MrJXGWj--g-2@lynne.ee>
Op zo 19 dec. 2021 om 22:11 schreef Lynne <dev@lynne.ee>:
> What happens if there's an overflow and the prediction coefficients
> are lowered? Is there a loss of bits? What about if it gives up?
The result remains lossless. If the prediction coefficients are
lowered, the residual of the prediction increases. This means the file
gets a little bigger, but the data is still all there.
If it gives up on searching for suitable LPC coefficients, it uses a
verbatim subframe instead of an LPC subframe. That means all data is
stored as unencoded PCM, with no form of prediction whatsoever. This
results in (usually a large) increase in storage space needed, but
this is still lossless.
_______________________________________________
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:[~2021-12-19 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 20:53 Martijn van Beurden
2021-12-19 21:11 ` Lynne
2021-12-19 21:41 ` Martijn van Beurden [this message]
2021-12-19 23:05 ` Lynne
2021-12-20 8:11 ` [FFmpeg-devel] [PATCH v2] " Martijn van Beurden
2021-12-20 11:25 ` Martijn van Beurden
2022-01-03 20:26 ` [FFmpeg-devel] [PATCH v3] " Martijn van Beurden
2022-01-05 3:57 ` Lynne
2022-01-08 14:24 ` [FFmpeg-devel] [PATCH v4] " Martijn van Beurden
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=CADQbU68cvsRbYnmdqiRc0Ltcyz0XWgrrdGKfNuabcak11QyJng@mail.gmail.com \
--to=mvanb1@gmail.com \
--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