nice, does Thusnelda comply with Theora specs? will it require can change to the decoder?<br><br><br><br><div class="gmail_quote">On Mon, Mar 24, 2008 at 11:51 AM, <<a href="mailto:xiphmont@xiph.org">xiphmont@xiph.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mon, Mar 24, 2008 at 11:11 AM, zhongshan zhang <<a href="mailto:zhangzs@gmail.com">zhangzs@gmail.com</a>> wrote:<br>
> Hi list,<br>
><br>
> I just came across this site:<br>
> <a href="http://web.mit.edu/xiphmont/Public/theora/demo.html" target="_blank">http://web.mit.edu/xiphmont/Public/theora/demo.html</a><br>
><br>
> I was wondering are these issues being addressed or will be addressed before<br>
> the 1.0 release?<br>
<br>
</div>The Thusnelda encoder, which is correcting the encoder deficiencies,<br>
is an extensive set of changes and we're likely to release 1.0 without<br>
Thusnelda, then immedaitely switch mainline development to the new<br>
encoder in Thusnelda.<br>
<br>
The primary motivation is stability; although the old encoder is not<br>
high-performance, it is very rugged and relaible. The new Thusnelda<br>
encoder needs more testing to be considered trustworthy.<br>
<br>
See the update at:<br>
<br>
<a href="http://web.mit.edu/xiphmont/Public/theora/demo2.html" target="_blank">http://web.mit.edu/xiphmont/Public/theora/demo2.html</a><br>
<br>
Monty<br>
</blockquote></div><br>