home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Flickering Tv-guide and other overlays with EVR enabled
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Eabin" data-source="post: 260581" data-attributes="member: 24932"><p>i did a lot of testing too. seeing as single-core affinity helps a lot, it might as well be some wrong synchronization code (aka. if ( _InVmr9Renderer ) { ... } ), which won't do anything useful, and makes even less sense on dual-core machines. if we could find the offending threads (assuming that they exists), they should be synchronized via a "real" lock.</p><p></p><p>but this still does not explain why this is purely an ATI issue...</p></blockquote><p></p>
[QUOTE="Eabin, post: 260581, member: 24932"] i did a lot of testing too. seeing as single-core affinity helps a lot, it might as well be some wrong synchronization code (aka. if ( _InVmr9Renderer ) { ... } ), which won't do anything useful, and makes even less sense on dual-core machines. if we could find the offending threads (assuming that they exists), they should be synchronized via a "real" lock. but this still does not explain why this is purely an ATI issue... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Flickering Tv-guide and other overlays with EVR enabled
Contact us
RSS
Top
Bottom