one other fix you guys might want to put in before 1.0 is the ASM
optimization on Win32. i would suggest change the inline asm to intel
intrinsics if possible. thats the recommended way of doing asm code
nowadays. and it should be supported by both gcc and vc++?
<br><br>Cheers,<br><br><br><div><span class="gmail_quote">On 11/1/07, <b class="gmail_sendername">Ralph Giles</b> <<a href="mailto:giles@xiph.org">giles@xiph.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Nov 01, 2007 at 09:44:10AM +0000, Luis Gonzalez wrote:<br><br>> I see in the libtheora 1.0 beta3 changelog that included new libtheoradec and libtheoraenc libraries supporting the new API from theora-exp , that it means that have multithread encoder?
<br><br>No, this is just a packaging issue. We want to transition to separate<br>encoder and decoder libraries and the new api.<br><br>We haven't merged the multithreaded encoder yet. I'd planned to do that<br>after
1.0.<br><br>More generally, Monty has been trying to improve the rate control a bit.<br>We'll probably hold 1.0 for that project. Beta3 is waiting on emulating<br>the theora-exp encoder api in the mainline encoder. So the current todo/
<br>roadmap looks something like:<br><br>1.0beta3 (end of next week) :<br><br>* support theora-exp encoder api in libtheoraenc<br><br>1.0beta4 (hopefully by the end of November)<br><br>* improved rate control<br>* fix known png2theora bug
<br><br>1.0 release (two weeks after beta4, hopefully with no changes)<br><br>1.1 (whenever)<br><br>* merge multithreaded encoder/decoder<br>* post-VP3 mode support in the encoder.<br>* rgb in/out<br><br>FWIW,<br> -r<br>_______________________________________________
<br>theora-dev mailing list<br><a href="mailto:theora-dev@xiph.org">theora-dev@xiph.org</a><br><a href="http://lists.xiph.org/mailman/listinfo/theora-dev">http://lists.xiph.org/mailman/listinfo/theora-dev</a><br></blockquote>
</div><br>