-
Notifications
You must be signed in to change notification settings - Fork 385
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
getFrameAtTime returning the same frame #45
Comments
This is very confusing, but getFrameAtTime takes Us instead of ms for time parameter, so you may success by passing progress*1000 for it. |
Yes I tried that, but still the same frame is showing. |
As skonb said, you aren't passing the correct unit of time to |
And as I said, I tried passing everything *1000 and it made no difference. |
As I said, send me a link to the video so I can test myself, otherwise I
|
I did attach a link in the first post. |
Please what is the actual time unit the method should receive? |
Hello,
What I'm trying to do, is capture a video and then play it frame-by-frame.
The way I decided to do this is load the video into your library, and using a SeekBar change the "Preview" image.
The first problem I encountered was the duration I received was always 0. After playing around with this for a little bit, I found that the library returns only duration in multiplications of a thousand. (0-1000-2000-etc).
When I try getting frames using getFrameAtTime - I get the same frame and not actual frames from the video.
At first I thought the problem was relating to the video being time lapsed (using setCaptureRate) - but after removing this option it didn't change much.
When pulling the video to my computer it plays fine and recognized as MPEG format.
What could be the problem?
Here is the extraction code:
One thing to note:
the function never return's a null value - just the same bitmap all over again.
Thank you,
Ron.
P.S.: Here is a link to the video just in case it will help you: https://drive.google.com/file/d/0B50D54gw1jgHT25rQ0ZuRFc5cFk/view?usp=sharing
The text was updated successfully, but these errors were encountered: