theora - May 2011 - Ptalarbvorm Update?

To my recollection, there hasn't been any talk about Ptalarbvorm. Is  
Ptalarbvorm development ditched? (I have noticed some commits for it every  
now and then, but nothing like the amount of commits last year)

-- 

Daniel Hendrycks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/theora/attachments/20110527/6a2bf6e3/attachment.htm

> Hi,
>
> It has been moved to the SVN trunk now.
> I still use it from time to compare teh quality improvement after each  
> update:
> http://screenshotcomparison.com/comparison/51305 (Look at the eyebrows  
> of the left character)
>
> Regards
> --Zikzak
Is the first screenshot Thusnelda, and the second the latest of  
Ptalarbvorm?
Thanks, I'm kinda just wondering if they're not even going to release it
as final, or have another gold version.

P.S. What's that a screenshot of?

-- 

Daniel Hendrycks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/theora/attachments/20110528/e5808934/attachment.htm

On Fri, May 27, 2011 at 11:22 PM, Daniel Hendrycks <kondo8 at hotmail.com>
wrote:
> To my recollection, there hasn't been any talk about Ptalarbvorm. Is
> Ptalarbvorm development ditched? (I have noticed some commits for it every
> now and then, but nothing like the amount of commits last year)
As mentioned, the development was moved to mainline. However, it's
hasn't been super-active lately for a couple of reasons.

One of them being that the active developers have been focusing their
time lately on other projects, including some (e.g. the Opus codec)
which have externally imposed deadlines.

As of right now while the quality of the SVN code is significantly
better than 1.1 overall there are some annoying regressions that I
think we want to fix before a release? in particular our quality on
fades has gone down and our tendency to produce ringing on titles has
increased.  The new faster speed level is somewhat broken (as a user
you probably wouldn't notice, but it's doing the analysis calculations
incorrectly? which is at least aesthetically bad if not a big
practical problem), and there are a lot of low hanging performance
fruit that would be nice to get in prior to a new release.


Of course, you can run the software today and report your findings.
Any such reports will help get out a new release?