Martijn van Beurden
Martijn van Beurden
Perhaps we can take a look at libopusfile for inspiration about seeking? Seeing these lines of code, it seems they've already figured it out: https://github.com/xiph/opusfile/blob/b23e611ffbed22886dfc1640abfcfd5bc6677b72/src/opusfile.c#L31-L59
I've been pondering this issue for a while. I've come up with a few decisions that need to be made - What to do with metadata. After all, that is...
I've been pondering how to fix this, but I think there is no clean solution possible. The extra data that follows could belong to the data chunk, but it could...
> * Or if it declares something else, and then FLAC (without --ignore-chunk-sizes) would object because audio doesn't match declaration? The problem is that there is no way for FLAC...
> * That means: FLAC should report back (as "warning" or "error", that is a policy question) that the specified chunk sizes are wrong, and that the user must consider...
Yes, in this instance that is possible, but that is not a general solution. Even so, I won't fix this before the release of 1.4.0, this need thorough testing and...
I meant that just looking at the filesize wouldn't be of any use for a smaller file with a wrong chunk size.
@ValZapod Are you sure you didn't post this at the wrong issue?
@H2Swine I've published a fix in #446. There is another problem though: using --keep-foreign-metadata on this file makes FLAC use *a lot* of memory until it is killed by my...
This is a duplicate of #113 Just because I'm curious, could you please tell what you use libFLAC.dll for?