Could it be metadata? Could the Oppo be scanning metadata before deciding to play files? <br><br><div class="gmail_quote">On Sun, Feb 6, 2011 at 12:06 AM, Brian Willoughby <span dir="ltr"><<a href="mailto:brianw@sounds.wa.com">brianw@sounds.wa.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On this note, is there any way to ask the current version of flac to<br>
create a file that is backwards compatible with an older version of<br>
flac? I suppose one possibility is to go back into the archives and<br>
grab an older version of flac, then use that to compress everything.<br>
The trouble then becomes how to determine which version of the<br>
decoder your hardware implements, so that you can make sure your flac<br>
files are not too "new" for the hardware.<br>
<font color="#888888"><br>
Brian<br>
</font><div class="im"><br>
<br>
On Feb 5, 2011, at 21:01, Brian Willoughby wrote:<br>
> Ah, another possibility is that the oppo BDP-95 implements an older<br>
> version of the decoder, and it's merely new flac files that give it a<br>
> headache. My friend happened to have an old version of flac<br>
> installed on his computer, 1.1.4, and that reported stream errors<br>
> with his files until he upgraded to 1.2.1 - if the oppo has anything<br>
> older than 1.2.1 then I suppose that might explain the decoding<br>
> problems.<br>
<br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Flac mailing list<br>
<a href="mailto:Flac@xiph.org">Flac@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/flac" target="_blank">http://lists.xiph.org/mailman/listinfo/flac</a><br>
</div></div></blockquote></div><br>