Closed GoogleCodeExporter closed 8 years ago
The source code is available, so modifying FFmpegFrameGrabber.java in the way
you need to shouldn't be too difficult. The AVFrame object is available as a
field variable, so exposing that should be all you need AFAIK.
If that's not what you are looking for, please explain a bit more clearly how
you would have FFmpegFrameGrabber modified, thanks!
Original comment by samuel.a...@gmail.com
on 23 Dec 2013 at 4:03
Thank you for responding.
So to be more specific - I have been going through the source code trying to
get my head around it and figure out how it works. But that's pretty much my
problem as I'm not very experienced programmer and FFmpeg itself seems horribly
complicated to me plus the whole code is written in a very different style than
what I'm used to from Java and C#, which I take it is the result of you trying
to make this whole thing resemble C++ as much as possible.
Specifically, I need to either modify the existing grabFrame method so that it
would return AVFrame instead of Frame or create a new method AVFrame
grabAVFrame(). The overall functionality would be the same, all I need is the
different return type.
Original comment by glere...@gmail.com
on 23 Dec 2013 at 1:01
Well, there are two `AVFrame` fields, one is `picture` and the other is
`samples_frame`. The `picture` gets updated on a call to `grab()`, so try to
call `grab()` and `picture` should contain the info you are seeking... Is that
it?
Original comment by samuel.a...@gmail.com
on 23 Dec 2013 at 1:46
Yes, that seems to work. That's actually much easier a solution than I thought
it would be.
Thank you very much for your help.
Original comment by glere...@gmail.com
on 23 Dec 2013 at 2:51
In the newly released JavaCV 0.7, I've added a new `Frame.opaque` field, which
`FFmpegFrameGrabber` fills with the corresponding raw `AVFrame` object, so that
should take care of this issue.
Please let me know if this is not satisfactory in some way, thanks!
Original comment by samuel.a...@gmail.com
on 7 Jan 2014 at 12:46
Original issue reported on code.google.com by
glere...@gmail.com
on 22 Dec 2013 at 11:29