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="tourettes" data-source="post: 656334" data-attributes="member: 10858"><p>The problem is not the inaccurate timers itself, those could be firing of on good accuracy - but the issue comes from the thread scheduling. It wont help if the timer fires when OS kernel doesn't allow the thread to be working. This is why MMCSS was added in Vista. It will allow thread priority to be boosted when there is timing critical work to be done - <a href="http://msdn.microsoft.com/en-us/library/ms684247%28VS.85%29.aspx" target="_blank">Multimedia Class Scheduler Service (Windows)</a></p><p></p><p>At least on the audio renderer side there was / is huge difference how accurate the thread wakeup times are when MMCSS was enabled.</p><p></p><p></p><p></p><p>Probably that same (or much better) accuracy would be gained if MMCSS would be used for the scheduling thread (and maybe for other threads as well). I would say that adding the 2nd timer is not going to help that much since all is just being limited by the OS thread scheduling - as written earlier the timers itself aren't inaccurate.</p><p></p><p>I'll do some small experimenting with the MMCSS off/on with the audio renderer and post the timer / thread wakeup accuracy data.</p><p></p><p></p><p></p><p>Indeed <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p></blockquote><p></p>
[QUOTE="tourettes, post: 656334, member: 10858"] The problem is not the inaccurate timers itself, those could be firing of on good accuracy - but the issue comes from the thread scheduling. It wont help if the timer fires when OS kernel doesn't allow the thread to be working. This is why MMCSS was added in Vista. It will allow thread priority to be boosted when there is timing critical work to be done - [url=http://msdn.microsoft.com/en-us/library/ms684247%28VS.85%29.aspx]Multimedia Class Scheduler Service (Windows)[/url] At least on the audio renderer side there was / is huge difference how accurate the thread wakeup times are when MMCSS was enabled. Probably that same (or much better) accuracy would be gained if MMCSS would be used for the scheduling thread (and maybe for other threads as well). I would say that adding the 2nd timer is not going to help that much since all is just being limited by the OS thread scheduling - as written earlier the timers itself aren't inaccurate. I'll do some small experimenting with the MMCSS off/on with the audio renderer and post the timer / thread wakeup accuracy data. Indeed :P [/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