<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<br><br>> Date: Sat, 20 Mar 2010 19:23:40 -0700<br>> From: giles@thaumas.net<br>> <br>> We've talked about it, but one of the problems is that the current API<br>> is one-frame-in-one-frame-out, so it's not clear how to pass multiple<br>> input frames at once without breaking API. How would you implement<br>> that?<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>If I understand you correctly, you could do the Microsoft method of making a new function called th_encode_ycbr_in_ex() that takes multiple frames if that's what you need (although I don't understand how this is necessary). Abstractly, you can avoid "breaking API" by adding functionality rather than changing it...</div><div><br><div><br></div><div>> There is some scope for multithreading the per-frame pipeline, but<br>> that only scales to three or four threads.<br><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Does it scale any worse than Vorbis?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>There are many applications that don't scale well past two or four threads so you'll be in good company. It will certainly help in the short term and, in the long term, we may never need to scale it higher than that, much like how multi-threading is rarely used for audio encoding anymore... It certainly won't be any worse than it is now where you can't thread it at all!</div><div><br></div><div><br></div></div> <br /><hr />Don't miss a beat <a href='http://go.microsoft.com/?linkid=9712961' target='_new'>Get Messenger on your phone</a></body>
</html>