-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
massive regression in seek times #425
Comments
The number of times that the warning comes out is interesting. This makes me think that there is some sort of line-painter bug going on where as you pull frames one-at-a-time it goes back to the start and scans all the way forward. I took a quick look at the code and there is a bunch of caching logic but did not work out exactly how it worked. My guess is that there may be a way to keep better track of where we are in pims and not trigger the full "scan from the beginning" logic. I also wonder if you do I also wonder if using something like |
I am on |
thanks for the suggestions @tacaswell. unfortunately,
|
prior to 18feda2 and with av=8 the time to index into AVI files was independent of the frame number:
but with av=9 and the above commit (necessary for av=9 to work), seeking to a large frame number takes much longer that accessing a frame near the beginning of the video:
is there anyway to fix this? a workaround? i suspect it is av/ffmpeg's fault. but the latest release of pims is now unusable for my purposes because of this degredation in performance. :(
The text was updated successfully, but these errors were encountered: