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
Development
General Development (no feature request here!)
MP1 EVR Presenter/dshowhelper community development
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="Owlsroost" data-source="post: 656331" data-attributes="member: 83973"><p>You're right - the problem with the Windows timers seems to be that they all run at a low-ish priority level, so they are fairly accurate most of the time, but it only takes a high-priority task etc to be scheduled by windows => the scheduler thread has just been asleep for 10-20ms longer than it should have been....at which point it probably has to drop a frame....</p><p></p><p>I added the 'timer' thread to try and get two delay timers using completely different mechanisms running in parallel, on the basis that if one timer got messed up the other one might still be OK - it does seem to help but it costs some CPU time of course. For info, on the render stats screen, 'Derr:' is the difference between actual time delay versus the target.</p><p></p><p>It's good to have someone running an Atom/ION system digging into the code - welcome aboard <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Owlsroost, post: 656331, member: 83973"] You're right - the problem with the Windows timers seems to be that they all run at a low-ish priority level, so they are fairly accurate most of the time, but it only takes a high-priority task etc to be scheduled by windows => the scheduler thread has just been asleep for 10-20ms longer than it should have been....at which point it probably has to drop a frame.... I added the 'timer' thread to try and get two delay timers using completely different mechanisms running in parallel, on the basis that if one timer got messed up the other one might still be OK - it does seem to help but it costs some CPU time of course. For info, on the render stats screen, 'Derr:' is the difference between actual time delay versus the target. It's good to have someone running an Atom/ION system digging into the code - welcome aboard :) Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MP1 EVR Presenter/dshowhelper community development
Contact us
RSS
Top
Bottom