<html>
<body>
<font size=3>At 14:16 06.02.2012, you wrote:<br><br>
<blockquote type=cite class=cite cite="">Olav,<br><br>
A change like this could easily break the format. That would be a
bad choice.</blockquote><br>
That makes sense. Explains why it is not there today.<br><br>
<br>
<blockquote type=cite class=cite cite="">On the other hand, an
informational 'application' block could be added in a way that does not
break the format, and this would even be backwards compatible since
'application' blocks have always been a part of the specification.
You simply won't be able to rely on them being there.</blockquote><br>
This is probably the best thing then. Adding the info will be optional?
It would certainly be an improvement and hopefully become part of the
command line description so users would know how to do it.<br><br>
Best regards<br><br>
Olav Sunde<br><br>
<br>
<blockquote type=cite class=cite cite="">Brian Willoughby<br>
Sound Consulting<br><br>
<br>
On Feb 6, 2012, at 03:16, Olav Sunde wrote:<br>
<blockquote type=cite class=cite cite="">This next is a feature request:
Today it is not possible to know the encoding of a flac archive. Many new
devices support playback of flac, however tiny processors sometimes have
a hard time decoding files with the default encoding of -5 or higher,
resulting in unstable playback or even reduced audio quality. A
re-encoding to -0 often solve these issues.<br>
Can you look at a way to store parameters used for encoding in an archive
so we can check it later? </font></blockquote></blockquote></body>
</html>