Re: [xine-devel] news on MPlayer homepage

[Michael R. <mr...@us...>]

Hi Mike,

> > I was just browsing through the MPlayer site and found that they
>              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ your first mistake...

:)
Besides being even more broken HTML than our page I found that theirs 
looks quite nice.

> > "Anyway lately an intentional (possibly forgot) tidbit was found in
> > xine's own copy of the ffmpeg tree (why, oh why), which disabled
> > the usage of MMX/SSE/Altivec/etc-enabled functionality in ffmpeg
> > codecs for quite some time :))) Have a nice time using xine! :)"
> >
> > Hum? I didn't know that. Is this true?
>
> 	Nope. This arose from a misunderstanding on the ffmpeg list. Here
> is what happened:
>
> * I am developing VP3, and am having discrepancies with the IDCT
>   facilities
> * I browse my source tree and notice that optimizations were disabled
> * I post an embarrassed note about it on ffmpeg-devel
> * later I realize that I had, for some unknown reason, disabled the
>   opts. in my own local tree some months prior, but that change never
>   propagated into CVS
> * MPlayer website maintainer insists on keeping this silly lie posted

I see. My guess was they misunderstood this note in our ChangeLog:
  * performance improvements (enabled ffmpeg direct rendering)
But thanks for the clarification.

> 	Anyway, don't let it get to you. The MPlayer (G1) project is on
> its way out.

Really? That soon?

> > Backend-frontend-separation? Sounds familiar to me. :)
>
> 	Indeed, MP-G2 is modeled after a program quite near and dear to
> our hearts.

Could be interesting to see how someone starting from scratch approaches 
this. Fresh ideas are always good.

Michael

-- 
/* Fuck me gently with a chainsaw... */
	2.0.38 /usr/src/linux/arch/sparc/kernel/ptrace.c