Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 572335" data-attributes="member: 10858">Re: HTPCInfo plugin for MediaPortal v0.9.0hi Micropolis,first I would like to thank for a nice plugin (althou I personally dont use it, but lot of our users use). And 2nd I would like to tell some results we have been lately receiving. Seems that the HTPCInfo plugin is source for lot of frame dropping / juddering issues on multiple HTPCs. Here are few pointers that should be taken into consideration for future versions of this plugin (I havent checked the code, so some of these might not be valid)1) Process() method overloading should be done as less as possible (only handle messaging between MP and the plugin there). On every single video frame rendering the Process() is run thru and if there is some code paths that cause few ms delays it could already cause dropped frame(s). We have only 20ms per frame time for the video decoding, running process() code, trying to match the v-sync, rendering the video frame and on top of that OSD etc. So, use as less code that runs in MPMain thread (easy to see if you put logging into every method, MP will log the used thread)2) All non-critical background processing should be halted when MP is palying a video (g_player should give this info)3) All background threads should be running lower priority that the MP itself, this will give smoother GUI animations etc.After solving those, the frame dropping / juddering issues the MP users have been reporting should be much more rare than thay are now.</blockquote>

[QUOTE="tourettes, post: 572335, member: 10858"] [b]Re: HTPCInfo plugin for MediaPortal v0.9.0[/b] hi Micropolis, first I would like to thank for a nice plugin (althou I personally dont use it, but lot of our users use). And 2nd I would like to tell some results we have been lately receiving. Seems that the HTPCInfo plugin is source for lot of frame dropping / juddering issues on multiple HTPCs. Here are few pointers that should be taken into consideration for future versions of this plugin (I havent checked the code, so some of these might not be valid) 1) Process() method overloading should be done as less as possible (only handle messaging between MP and the plugin there). On every single video frame rendering the Process() is run thru and if there is some code paths that cause few ms delays it could already cause dropped frame(s). We have only 20ms per frame time for the video decoding, running process() code, trying to match the v-sync, rendering the video frame and on top of that OSD etc. So, use as less code that runs in MPMain thread (easy to see if you put logging into every method, MP will log the used thread) 2) All non-critical background processing should be halted when MP is palying a video (g_player should give this info) 3) All background threads should be running lower priority that the MP itself, this will give smoother GUI animations etc. After solving those, the frame dropping / juddering issues the MP users have been reporting should be much more rare than thay are now. [/QUOTE]

Verification