From: "Clément Péron" <peron.clem@gmail.com> To: ffmpeg-devel@ffmpeg.org Cc: "Clément Péron" <peron.clem@gmail.com> Subject: [FFmpeg-devel] [RFC PATCH 0/3] Propagate PRFT side data Date: Thu, 21 Sep 2023 14:16:57 +0200 Message-ID: <20230921121720.362842-1-peron.clem@gmail.com> (raw) Dear FFMpeg contributors, I'm new to the FFMpeg code base and audio/video sync world, so forgive me in advance If my questions are a bit dumb. I have a project where I need to synchronize multiple RTSP cameras with other network sensors (sync with NTP or PTP). In my case, I used Ffmpeg to decode the RTSP stream and then output the rawvideo to the stdout pipe. After looking in the RTPdec, I found multiple timestamps PST, DTS and also the PRFT (Producer Reference Timestamp). In my case the PRFT seems the correct one. After several tests and diggs, I found that the AV_PKT_DATA_PRFT produce by the RTSP Demux doesn't seems to be forwarded to the encoder/decoder, nor to the final Muxer. So I have multiple question: Is the forward of the AV_PKT_DATA_PRFT the correct solution? I saw also that Dashenc and Movenc use this Side data but how do they get it? Actually I have a dirty hack to output PRFT on the stdout, is there something "more standard" to communicate between Ffmpeg and a python script? Thanks for your help, Clément Clément Péron (3): frame: decode: propagate PRFT side data packet to frame avcodec: rawenc: Forward PRFT frame data to packet HACK: avformat: rawenc: allow to output a raw PRFT libavcodec/decode.c | 1 + libavcodec/rawenc.c | 12 ++++ libavfilter/f_sidedata.c | 1 + libavformat/rawenc.c | 122 +++++++++++++++++++++++++++++++++++++++ libavutil/frame.c | 1 + libavutil/frame.h | 4 ++ 6 files changed, 141 insertions(+) -- 2.42.0 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2023-09-21 12:17 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 12:16 Clément Péron [this message] 2023-09-21 12:16 ` [FFmpeg-devel] [RFC PATCH 1/3] frame: decode: propagate PRFT side data packet to frame Clément Péron 2023-09-21 12:16 ` [FFmpeg-devel] [RFC PATCH 2/3] avcodec: rawenc: Forward PRFT frame data to packet Clément Péron 2023-09-21 12:17 ` [FFmpeg-devel] [RFC PATCH 3/3] HACK: avformat: rawenc: allow to output a raw PRFT Clément Péron 2023-09-21 20:09 ` Michael Niedermayer 2023-09-21 20:51 ` Andreas Rheinhardt 2023-09-22 7:44 ` Clément Péron 2023-09-22 7:59 ` Andreas Rheinhardt 2023-09-22 8:38 ` Clément Péron 2023-09-22 9:26 ` Paul B Mahol 2023-09-22 10:05 ` Clément Péron 2023-09-22 11:41 ` Paul B Mahol 2023-09-22 12:39 ` Clément Péron 2023-09-22 13:16 ` Paul B Mahol 2023-09-22 14:29 ` Clément Péron 2023-09-22 17:39 ` Paul B Mahol 2023-09-22 10:02 ` Andreas Rheinhardt 2023-09-22 10:10 ` Clément Péron 2023-09-22 11:34 ` Andreas Rheinhardt 2023-09-22 12:31 ` Clément Péron 2023-09-21 13:12 ` [FFmpeg-devel] [RFC PATCH 0/3] Propagate PRFT side data Kieran Kunhya 2023-09-21 15:41 ` Clément Péron 2023-09-24 9:12 ` Clément Péron 2023-10-24 15:10 ` Clément Péron
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230921121720.362842-1-peron.clem@gmail.com \ --to=peron.clem@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git