Martijn van Beurden
Martijn van Beurden
On second thought, there is another way to exploit this, but that is very unreliable: when running out of memory. As FLAC uses only a tiny amount of memory and...
No, the encoding parameters bound how much memory is used, so an attacker cannot let libFLAC use an arbitrary amount of memory, except when the program allows for supplying invalid...
There is a tool to scan FLAC files here: https://pypi.org/project/r128gain/ and https://github.com/desbma/r128gain Anyone is welcome to supply a patch to implement this directly into `flac` and `metaflac`.
With PR #549 copying of all metadata blocks (except seektable and streaminfo which can't and shouldn't be copied) can be done as follows ``` metaflac --remove --except-block-type=STREAMINFO,SEEKTABLE destinationfile.flac metaflac --list...
This has been implemented in #549
This fix was needed here: https://lists.xiph.org/pipermail/flac-dev/2023-June/006642.html
I have the same problem here: https://www.ietf.org/archive/id/draft-ietf-cellar-flac-09.html#name-uncommon-bit-depth-2 The [xml source](https://www.ietf.org/archive/id/draft-ietf-cellar-flac-09.xml) says ``` 8-bit µ-law can be losslessly converted to 14 bit (Linear) PCM ``` However, the HTML source says ```...
Thanks for the pointer!
> And at the changelog I see, the ID3 tags were being supported in the past We're talking almost 19 years ago here. Support from plugins was removed in October...
The problem is that FLAC files with an ID3v2 block are not valid, according to the FLAC spec. Now, the `flac` command line tool does have quite some handling of...