Quoting Timo Rothenpieler (2022-12-05 14:39:37) > This is fairly basic and makes a lot of assumptions, but it works > for the most simple cases. > > For one, it only ever fetches exactly one packet per call to receive_frame. > Right now it's impossible for there to ever be more than one, but the API > allows for more, which might need handled in the future. > > It also basically translates the new API back to the old, since that's how > the frame threading code operates. Which feels backwards in regards to > the new API, but it was the path with least resistance in implementing this.
If it only supports one packet to one frame, then it goes against the whole point of using the receive_frame API. -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
