And this problem only happens to a few of my videos, the rest seeks very fast. On the full video, one random seek will hangs the program for 3+ minutes, I lost patient after the 3 minute count, so the actual decoding time could be double or triple. The sample is only 3 minutes out of a 2 hours long video. You can see about memory use in "file information" dialog. With long gop and large frames it can take all your memory. It is a 250 frame gop.ītw it may help if you see keyframes, press edit->markers from keys. With fcchandler mkv driver you can do this, gui will appear more responsive, but to get any picture displayed you actually have to wait. This can make a difference if you request one frame, and immediately request another. I know one problem which I may try to solve: currently "caching input driver" does not allow to abort decoding.
Yes it takes time to decode but eventually it does finish.
0 kommentar(er)
