2012-06-02, 22:54
(2012-06-02, 20:47)torcar Wrote: As I understand, a part of the reason why this problem has existed for such a long time is that it's hard to replicate for those who's not afflicted. (DDDamian: Correct me if i'm wrong)
Love the phrase "afflicted" No your not wrong - you're bang on. This is not an ignored issue so much as one that we can't readily reproduce.
Whether we're less-sensitive to it, or have the right hardware combinations is hard to say, but asking around the dev team (who are mostly videophiles) we don't seem to be among the "afflicted".
As mentioned, some folks using the latest with AE have reported the sync-issue resolved, cases where they previously had the same issues.
Google around and it's not just XBMC with the issue so much as it's also a GPU clocking issue, but I think it's fair to say XBMC + bad hw timing is the worst combination.
The well-respected (by me anyways!) AVS forums have a very telling thread on the issue: http://www.avsforum.com/avs-vb/archive/i...33324.html
Keep us posted when you've had more time to play with your new build!