Quote:
Originally Posted by jokerb47
I tested on about 10 videos - problem remains. But it turned out that it is KMPLayer related, because in PotPlayer everything works with same MadVr settings(same videos). how create debug log? 
But same version of KMPlayer worked fine with "delay playback start" of 82.5...
debug report: http://www.sendspace.com/file/cfqoyh |
Aaaaaaah, I see. The problem is relatively simple:
When using e.g. CoreAVC for decoding, KMPlayer creates an instance of CoreAVC for decoding and an instance of madVR for rendering and connects them. This works just fine.
When configuring KMPlayer to use a madVR decoder, KMPlayer creates an instance of madVR for decoding and an instance of madVR for rendering and tries to connect them. Connecting doesn't work, but KMPlayer doesn't care. So basically in this situation KMPlayer has two instance of madVR running at the same time. This seems to work just fine by itself. One madVR instance seems to be sitting idle while the other is doing all the work. Unfortunately the one which is sitting idle is intercepting the "run playback" events and blocking them because the queues of the idle madVR instance are not full (and never will be). The other madVR instance which is really doing all the work never gets the "run playback" events. Because of that playback never starts.
Edit: Found an easy way to fix that in madVR. Will be fixed in the next build.