Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 521807" data-attributes="member: 10858">Those are completely two different ways of rendering we are talking with GUI and video playback. Video playback is always scheduling the frames to be drawn by the EVR renderer, this component is not taking in account if the focus is on MP window or not. Where as MP GUI (and visualization) are rendered and frames are scheduled by the MP main thread which is taking into account the window focus (this is done to give more CPU / GPU time when some other applications are accessed).In short there is no technical limitations for the current behavior, but instead we have wanted to keep things simplified (one config option less) and now it fires back in some cases where visualization is rendered and no focus is on MP (pretty minor user base are affected this as MP's main audience is HTPC's where MP is always running and if external applications are used they are filling the screen).In short, it is fixable but as it is a new feature it won't be handled in 1.1.0. Also as it will add one extra setting it might be considered not important enough that it should allow the complexity to rise (we have had hundreds of features or small additions during the years that aren't taken into use because of their small benefit and making application more complex for users and developers).</blockquote>

[QUOTE="tourettes, post: 521807, member: 10858"] Those are completely two different ways of rendering we are talking with GUI and video playback. Video playback is always scheduling the frames to be drawn by the EVR renderer, this component is not taking in account if the focus is on MP window or not. Where as MP GUI (and visualization) are rendered and frames are scheduled by the MP main thread which is taking into account the window focus (this is done to give more CPU / GPU time when some other applications are accessed). In short there is no technical limitations for the current behavior, but instead we have wanted to keep things simplified (one config option less) and now it fires back in some cases where visualization is rendered and no focus is on MP (pretty minor user base are affected this as MP's main audience is HTPC's where MP is always running and if external applications are used they are filling the screen). In short, it is fixable but as it is a new feature it won't be handled in 1.1.0. Also as it will add one extra setting it might be considered not important enough that it should allow the complexity to rise (we have had hundreds of features or small additions during the years that aren't taken into use because of their small benefit and making application more complex for users and developers). [/QUOTE]

Verification