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="davidf" data-source="post: 656712" data-attributes="member: 19484"><p>I played with (hacking in) the WaitableTimer last night which dropped the CPU markedly (it also stuffed the timing owlsroost had got working as well) This gave a reduction the amount of polling and does seem to be accurate. The most sensitive thing seems to be the number of threads running under MMCS that seems to cause all sorts of issues if there are too many. I'll try and correct the timing again and see what it looks like at that point. I think it would be possible to get a very accurate timer (self correcting) running which could get to within 1 ms of any point in the raster display without too much messing around, at least if I ignore the renderer for now.</p><p> </p><p></p><p> </p><p>I'll use that tool which was posted and have a look - although from messing the timing quite a few times last night I'm betting on the CPU. robyf's dual core is working fine whereas my single core can get stuttery but only when the Audio Renderer is added, the only difference in the 2 setups is the extra core on the 330 over the 230.</p></blockquote><p></p>
[QUOTE="davidf, post: 656712, member: 19484"] I played with (hacking in) the WaitableTimer last night which dropped the CPU markedly (it also stuffed the timing owlsroost had got working as well) This gave a reduction the amount of polling and does seem to be accurate. The most sensitive thing seems to be the number of threads running under MMCS that seems to cause all sorts of issues if there are too many. I'll try and correct the timing again and see what it looks like at that point. I think it would be possible to get a very accurate timer (self correcting) running which could get to within 1 ms of any point in the raster display without too much messing around, at least if I ignore the renderer for now. I'll use that tool which was posted and have a look - although from messing the timing quite a few times last night I'm betting on the CPU. robyf's dual core is working fine whereas my single core can get stuttery but only when the Audio Renderer is added, the only difference in the 2 setups is the extra core on the 330 over the 230. [/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