Reply to thread

Message

<blockquote data-quote="JimCatMP" data-source="post: 965414" data-attributes="member: 103549">Hi&nbsp;Very frustrating, you have my sympathies. I've looked at your log files and nothing I see points fingers.&nbsp;Your using MePo 1.2.3, with the following Codecs&nbsp;&quot; mpeg2audiocodec MPC - MPA Decoder Filter&nbsp; &nbsp; mpeg2videocodec MPC - MPEG-2 Video Decoder (Gabest)&nbsp; &nbsp; h264videocodec - ffdshow DXVA Video Decoder&nbsp; &nbsp; aacaudiocodec - MPC - MPA Decoder Filter&nbsp;&nbsp; &nbsp; As you problem affects over viewers after MePo has been run (and you can't kill MePo) I would suspect your codecs are the problem - some element of the code is still running (locked into the Windows kernel, you can't kill it when it's there and it's not taking signals from the outside world). Over views are then trying to use elements of the codec and can't, hence the crash.Suggest you do the following 3 things -&nbsp;1) Install the LAV filters, MePo Installer, and set all codec functions to them, then try MePo.&nbsp;2) Run MePo &amp; 'crash it'. In task manager, go to Performance tab, and open Resource Monitor and right click on MePo, and select Analyze Wait Chain - see what it tells you.&nbsp;3) Disable all plugins, all of them (as there are dll associated with each) and try &amp; crash MePo.&nbsp;If the 1st one solved problem your good, if not, you'll need to keep trying.&nbsp;It could be OS problem - my main client simply stopped working in MePo, Client &amp; config, separate DDL's impacted. So installed 1.3RC, didn't work - none of the LAV codec's working. So, did a debug dump ready to submit to forum, but looked at App's logs - noted lots of issued nothing to do with MePo (not seen same in your logs, but not expert) so concluded the power zapping system had few weeks ago did more harm than expected, so clean Windows install was only solution, recover DB's (copy your DB's off system, you just need to copy them and relevant thumbs back when your done), shortcutter settings file + usual Windows tweaks for access, and now 100% happy again - but all my content still played on client via WMP<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp;Good luck - you may need it.&nbsp;&nbsp;PS - As mbuzina say's - please set your system specs, makes it easier for possible common problems to be seen.</blockquote>

[QUOTE="JimCatMP, post: 965414, member: 103549"] Hi Very frustrating, you have my sympathies. I've looked at your log files and nothing I see points fingers. Your using MePo 1.2.3, with the following Codecs " [B]mpeg2audiocodec [/B]MPC - MPA Decoder Filter [B] mpeg2videocodec [/B]MPC - MPEG-2 Video Decoder (Gabest) [B]h264videocodec - [/B]ffdshow DXVA Video Decoder [B]aacaudiocodec - [/B]MPC - MPA Decoder Filter As you problem affects over viewers after MePo has been run (and you can't kill MePo) I would suspect your codecs are the problem - some element of the code is still running (locked into the Windows kernel, you can't kill it when it's there and it's not taking signals from the outside world). Over views are then trying to use elements of the codec and can't, hence the crash. Suggest you do the following 3 things - 1) Install the LAV filters, MePo Installer, and set all codec functions to them, then try MePo. 2) Run MePo & 'crash it'. In task manager, go to Performance tab, and open Resource Monitor and right click on MePo, and select Analyze Wait Chain - see what it tells you. 3) Disable all plugins, all of them (as there are dll associated with each) and try & crash MePo. If the 1st one solved problem your good, if not, you'll need to keep trying. It could be OS problem - my main client simply stopped working in MePo, Client & config, separate DDL's impacted. So installed 1.3RC, didn't work - none of the LAV codec's working. So, did a debug dump ready to submit to forum, but looked at App's logs - noted lots of issued nothing to do with MePo (not seen same in your logs, but not expert) so concluded the power zapping system had few weeks ago did more harm than expected, so clean Windows install was only solution, recover DB's (copy your DB's off system, you just need to copy them and relevant thumbs back when your done), shortcutter settings file + usual Windows tweaks for access, and now 100% happy again - but all my content still played on client via WMP:) Good luck - you may need it. PS - As mbuzina say's - please set your system specs, makes it easier for possible common problems to be seen. [/QUOTE]

Verification