<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - Add option to manually disable bilinear filtering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68360#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - Add option to manually disable bilinear filtering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68360">bug 68360</a>
from <span class="vcard"><a class="email" href="mailto:dr.hyder@gmail.com" title="Charles Hyder <dr.hyder@gmail.com>"> <span class="fn">Charles Hyder</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=68360#c18">comment #18</a>)
<span class="quote">> "What I think is causing unneeded smoothing at scale=1 is some bug in the
> geometry calculations."
>
> No, it is caused by the fact that it executes the new scaleImageYuXuBilinear
> code instead of the old scaleImageYuXu</span >
Oh, so it's just for images! What was the motivation for moving to a new algo,
btw? Just curious. Obviously, it did better in some situation, I assume. Can I
see an example? Or can you point me to the right place to look, please?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>