You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My goal is to effectively play a video from a file in a custom view by cycling through frames at the video framerate. My first attempt at this uses ffmpeg to decode the entire video file into a stream of PNGs (should probably use rawvideo), then splits that stream into an array of images that can be displayed.
The FFMpegCore use looks like this:
This is manageable for very small videos, but requires that the entire decoded video sequence be held in memory at once making memory usage a problem. So is there any way of decoding one frame to a buffer, showing that frame, then decoding the next frame into the buffer, showing that frame and so on in a loop? I've experimented briefly with using a filestream and pipe input, but that seems to get decoded all at once by FFMpegCore, so I'm not sure if there's a way to effectively "stream" a file like a videoplayer would.
The text was updated successfully, but these errors were encountered:
My goal is to effectively play a video from a file in a custom view by cycling through frames at the video framerate. My first attempt at this uses ffmpeg to decode the entire video file into a stream of PNGs (should probably use rawvideo), then splits that stream into an array of images that can be displayed.
The FFMpegCore use looks like this:
This is manageable for very small videos, but requires that the entire decoded video sequence be held in memory at once making memory usage a problem. So is there any way of decoding one frame to a buffer, showing that frame, then decoding the next frame into the buffer, showing that frame and so on in a loop? I've experimented briefly with using a filestream and pipe input, but that seems to get decoded all at once by FFMpegCore, so I'm not sure if there's a way to effectively "stream" a file like a videoplayer would.
The text was updated successfully, but these errors were encountered: