After some testing, I can give more details to the problem:
Whenever I navigate to the 1st Frame in MPC-HC (no matter whether I use stop, the trackbar or step), I have to step forward twice to get to the 2nd Frame. After that, each step brings me to the next frame, just as it should. This looks like a bug at first sight, but I saw in an older version of MPC (release_v1_5_1_2903) that rewinding to the beginning (e.g. by clicking stop) didn't display frame 0, so I am guessing you used some kind of workaround to display that frame and this is why you have to step twice to get to the 2nd Frame. But now in the newer version the rewind-problem was solved and the workaround is still in there somewhere.
Like I said, I just guessed all that. Can anyone enlighten me, whether I am correct? Or maybe for a start you can just tell me which function is called when the stop-Button is pressed, because I can only find functions that return E_NOTIMPL.
There's something else I found out:
When we used a custom source filter in debug mode, we noticed that whenever we hit "stop" in MPC-HC, his stop-function and his seek-function are being balled twice (alternating). While doing that in my app didn't help, it still looks like a clue and I am going to follow any of those.
|