From: Zhao Zhili <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] How to implement pcap ffmpeg format? Date: Thu, 23 Feb 2023 01:59:52 +0800 Message-ID: <tencent_57191C454BACE613D0A166F267CD6A8D5306@qq.com> (raw) In-Reply-To: <CAPeTicPskmPW-HJV9eK+LbFSdNf+hfGabk_U0F2focJyxtjGyg@mail.gmail.com> > 在 2023年2月23日,01:22,sonntex <sonntex@gmail.com> 写道: > > Are you sure that vp8 and vp9 can be put to mpeg-ts? You missed the point. Use any (streaming) container which supports the codec, e.g., webm. Please don’t top post. > > On Wed, Feb 22, 2023 at 3:25 PM Zhao Zhili <quinkblack@foxmail.com> wrote: > >>> -----Original Message----- >>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of >> sonntex >>> Sent: 2023年2月22日 21:59 >>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> >>> Subject: Re: [FFmpeg-devel] How to implement pcap ffmpeg format? >>> >>> So, if I have an rtp stream inside my application and want to save it >>> somehow to a playable media container, I have to wrap this stream to >>> something that could be transferred by pipe to ffmpeg, for instance to >> ivf >>> or to h264 byte stream. The first format requires deep codec parsing to >> >> Why not remux RTP to something like TS at the first replace, instead of >> deal with pcap? >> >>> extract at least width and height, perhaps other properties. Seems easy >> but >>> non-unified. Another approach is to pass the stream to a local udp >> socket, >>> simultaneously execute and control the ffmpeg process. It could lead to >>> data loss and requires socket coding in such a simple application. >>> >>> I understand why ffmpeg developers don't want to include pcap support to >>> ffmpeg but it could be implemented as an external code by somebody else >> for >>> whom it seems to be useful. I can't really find any blockers to do that >>> except that all the code inside rtpdec is encapsulated in its *.c file >> and >>> is not accessible from a hypothetical new pcap format. What I found is >> that >>> udp.c derives url protocol interface and does the same as pcap format >>> should do - extract rtp packets from a source and pass it further to >>> rtpdec. The problem is that pcap format is a format, not a protocol, >> which >>> reads data from ffmpeg file protocol. And the question was how to build >> the >>> chain of <file protocol> -> <input pcap format> -> <input rtp format>? >>> >>> On Wed, Feb 22, 2023 at 12:54 PM Rémi Denis-Courmont <remi@remlab.net> >>> wrote: >>> >>>> Hi, >>>> >>>> I agree with Kieran that this doesn't look like it belongs in FFmpeg >> or in >>>> any media framework. In fact, Wireshark has some support for extracting >>>> media from RTP, and that seems like the right place for it. >>>> >>>> With that said, you can't realistically pass RTP packets on the >> standard >>>> input. RTP is datagram-based. Packet boundaries are relevant; it can't >> go >>>> over a pipe. Unless you use a Unix datagram socket as standard input, >> but >>>> that would be very weird. >>>> >>>> Besides, there may be multiple streams on different ports, with >> different >>>> payload maps, and the receiver needs to know which port which packet >> came >>>> on. >>>> >>>> Note: Unfortunately, earlier attempts to standardise a container for >>>> RTP/RTCP packets have failed. >>>> _______________________________________________ >>>> 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". >>>> >>> _______________________________________________ >>> 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". >> >> _______________________________________________ >> 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". >> > _______________________________________________ > 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". _______________________________________________ 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 prev parent reply other threads:[~2023-02-22 18:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-21 22:33 sonntex 2023-02-21 22:38 ` Kieran Kunhya 2023-02-21 22:55 ` sonntex 2023-02-22 8:04 ` Gijs Peskens 2023-02-22 8:52 ` sonntex 2023-02-22 12:53 ` Rémi Denis-Courmont 2023-02-22 13:51 ` Devin Heitmueller 2023-02-22 13:59 ` sonntex 2023-02-22 15:25 ` Zhao Zhili 2023-02-22 17:22 ` sonntex 2023-02-22 17:59 ` Zhao Zhili [this message] 2023-02-22 18:34 ` sonntex
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=tencent_57191C454BACE613D0A166F267CD6A8D5306@qq.com \ --to=quinkblack@foxmail.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