If your setting differs from what is sent, there is no way except transcode.
If your setting identical to what is sent, you can start recording by waiting for key frame. This will lead the latency in your dump file compares to the time you toggle record button on the UDP stream. This latency is depended on GOP size of original stream On Tue, Dec 31, 2019 at 08:29 Audric Ackermann <[email protected]> wrote: > Hi, > > I think I already know the answer but I want to play UDP stream (h264 & > klv) in an android app, and be able to toggle a "recording button" to save > the data as a file with the exact same input parameters than what is sent > to be. > The only way to do this is to decode the whole frame (to display it) and > reencode it when the button is pressed, right? > > Because of the h264 I am not sure when the button is pressed I have a > keyframe already, so there is no other way than doing this way? > > Thanks for this clarification, > Audric > _______________________________________________ > Libav-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/libav-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe".
_______________________________________________ Libav-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
