Pierre-Yves Thoulon wrote:
METADATA_BLOCK_HEADER has a 24-bit field to encode the length of
METADATA_BLOCK_DATA ; hence the limitation (which not only applies
to METADATA_BLOCK_PICTURE but all metadata blocks.
I see. So it's possible to abuse some other metadata blocks too..
I found the
On Thu, Jun 19, 2014 at 09:23:26PM +0200, Martijn van Beurden wrote:
op 19-06-14 20:17, lvqcl schreef:
It seems quite common for 16-bit files:
I second that. Apparently it depends on the kind of music, some
albums have no warnings (mostly classical music it seems), some
have over 20 per
On Thu, Jun 19, 2014 at 06:52:05PM +0200, Martijn van Beurden wrote:
One other issue that I've brought up before but hasn't been
fixed yet: none of the people that have contributed to FLAC in
the last few years (save Miroslav) are in the AUTHORS file :)
Also, it would be nice to mention in
On Fri, Jun 20, 2014 at 01:21:03PM +0400, lvqcl wrote:
Miroslav Lichvar цкщеу:
+/*
+ * This is used to avoid overflow with unusual signals in 32-bit
+ * accumulator in the *precompute_partition_info_sums_* functions.
+ */
+#define FLAC__MAX_EXTRA_RESIDUAL_BPS 4
+ /*
On Fri, Jun 20, 2014 at 02:15:31PM +0400, lvqcl wrote:
Miroslav Lichvar wrote:
As overflow in the accumulator won't result in a data loss, I think
this is good enough until someone can figure out a better approach.
FLAC calculates real bitdepth of input signal for every block. Is it
Hi!
Can anyone name hardware decoders that can't decode non-subset FLAC stream?
Which hardware device or software fails for mismatch of any conditions
described at http://xiph.org/flac/format.html#subset?
Thanks in advance!
___
flac-dev mailing list
