Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 954027" data-attributes="member: 18896">Upon startup of MovPic plugin, it scans your existing collection for any missing mediainfo, artwork, etc. It also scans for new files and imports them if needed. The entire process of mediainfo, importing, etc is not very concurrent friendly if you are using a slow system and/or items that are not multi-thread optimized.&nbsp;For example the LAV codec is not very multi-thread friendly, and you should try the MPC-HC standalone filters.&nbsp;Even on a fast system, if LAV is in use by MediaPortal for playback and I evoke it again on the same box via concurrent RDP then it starts to skip frames inside MediaPortal. I repeat the same test with MPC-HC codecs and it works fine. Granted I still use LAV, because I simply avoid the concurrency issue.&nbsp;In your case, you can for example adjust MovingPictures to not auto-import or at least reduce the impact. And you should check your movingpictures.log file to see what entries in your collection cause it to constantly look for new artwork, rescan mediainfo, etc. If you simply fix all those anomalies one at a time, then there is hardly any impact, except the quick scan to verify all is ok.</blockquote>

[QUOTE="RoChess, post: 954027, member: 18896"] Upon startup of MovPic plugin, it scans your existing collection for any missing mediainfo, artwork, etc. It also scans for new files and imports them if needed. The entire process of mediainfo, importing, etc is not very concurrent friendly if you are using a slow system and/or items that are not multi-thread optimized. For example the LAV codec is not very multi-thread friendly, and you should try the MPC-HC standalone filters. Even on a fast system, if LAV is in use by MediaPortal for playback and I evoke it again on the same box via concurrent RDP then it starts to skip frames inside MediaPortal. I repeat the same test with MPC-HC codecs and it works fine. Granted I still use LAV, because I simply avoid the concurrency issue. In your case, you can for example adjust MovingPictures to not auto-import or at least reduce the impact. And you should check your movingpictures.log file to see what entries in your collection cause it to constantly look for new artwork, rescan mediainfo, etc. If you simply fix all those anomalies one at a time, then there is hardly any impact, except the quick scan to verify all is ok. [/QUOTE]

Verification