I think this is definitely relevant to bring this up. Not many users have 1080i H264 TV broadcasts, so I think it's important that the developers know that the new changes have introduced problems for some users. I imagine only a small proportion of developers watch 1080i H264 DVB-T using XP + hardware acceleration. As an end user I am unsure of the changes to the code, but want to make the developers aware just in case the changes have introduced a bug vs increased hardware requirements for more power hungry rendering.
I would say that with the improvements MP 1.0.2 + 780G +Athlon X2 + XP + PDVD8 (Hardware Accleration) + 1080i TV + bob deinterlacing is definitely now off the edge. I havn't retried MP1.0.2 since I overlclocked the FSB. However I am not complaining, It is good that the flicker issue for vista has been solved/improved.
780G + Athlon X2 + XP (I can't vouch for vista) unfortunately now fails requirements for 1080i TV
I am happy with MP1.0 Final, and will probably install a new video card along with more HDDs when 1.10 is released.
[[*] AMD 780G: with Athlon X2 it manages to do _some_ 1080i content properly - seems to be right on the edge. No problems with any Phenom (HT3 CPU). If there's stuttering, you might be able to workaround it with CoreAVC, another version of PDVD codecs or live with Bob deinterlacing.
I would say that with the improvements MP 1.0.2 + 780G +Athlon X2 + XP + PDVD8 (Hardware Accleration) + 1080i TV + bob deinterlacing is definitely now off the edge. I havn't retried MP1.0.2 since I overlclocked the FSB. However I am not complaining, It is good that the flicker issue for vista has been solved/improved.
780G + Athlon X2 + XP (I can't vouch for vista) unfortunately now fails requirements for 1080i TV
I am happy with MP1.0 Final, and will probably install a new video card along with more HDDs when 1.10 is released.