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: 722677" data-attributes="member: 83973"><p>The lines on v70 will not be as flat as v67 - that is intentional - it was designed to lower the CPU load, as an experiment.</p><p></p><p>My guess is that the scenes with high movement generate higher CPU load - which will cause more timing variation => more ripples/spikes in the graphs.</p><p></p><p>The 'Rptd FPS' comes from the decoder/EVR mixer right at the beginning of play, when it doesn't really know if the video is progressive or interlaced - so it assumes it might need de-interlacing so it reports 48 fps instead of 24 fps. The 'Detd FPS' is calculated and averaged from the timestamps as the video plays so it's the real fps.</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Owlsroost, post: 722677, member: 83973"] The lines on v70 will not be as flat as v67 - that is intentional - it was designed to lower the CPU load, as an experiment. My guess is that the scenes with high movement generate higher CPU load - which will cause more timing variation => more ripples/spikes in the graphs. The 'Rptd FPS' comes from the decoder/EVR mixer right at the beginning of play, when it doesn't really know if the video is progressive or interlaced - so it assumes it might need de-interlacing so it reports 48 fps instead of 24 fps. The 'Detd FPS' is calculated and averaged from the timestamps as the video plays so it's the real fps. 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
