Re: Looking for users of --keep-foreign-metadata

David Willmore <[email protected]> Wed, 2 Nov 2022 16:44:38 -0400
Newsgroups gmane.comp.audio.compression.flac.devel
Message-ID <CA+s+PWSk_mXBwoidkRX0Lv4xybLNa2F+ZpqhFwa5rb232B8_Pg@mail.gmail.com>
If a --force-* option fails, shouldn't it error out instead?  Scripts
aren't going to pick up on a warning, but they should pick up on an errored
exit code (or they're just not written well enough to care).

On Wed, Nov 2, 2022 at 2:20 PM Martijn van Beurden <[email protected]> wrote:

> Op wo 2 nov. 2022 om 13:48 schreef Martijn van Beurden <[email protected]>:
> > Perhaps an option --force-stored-foreign-metadata could be added to
> > have FLAC blindly use the foreign metadata chunks and data chunk
> > headers. I think this might result in invalid files (wrong chunk
> > sizes) in corner cases, for example when a FLAC file has been altered
> > (shortened/lengthened) but the chunks haven't been updated. I think
> > that might be the reason for the current behaviour.
> >
>
> Perhaps the middle ground here is to let FLAC output as it does now,
> but warn the users when it differs from what is stored?
> _______________________________________________
> flac-dev mailing list
> [email protected]
> http://lists.xiph.org/mailman/listinfo/flac-dev
>

_______________________________________________
flac-dev mailing list
[email protected]
http://lists.xiph.org/mailman/listinfo/flac-dev