Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] How to implement pcap ffmpeg format?
Date: Tue, 21 Feb 2023 22:38:21 +0000
Message-ID: <CAK+ULv6OTtO0pN7a8eV=AyXevb4EYXLUVWD8+MptzNSzWznX9A@mail.gmail.com> (raw)
In-Reply-To: <CAPeTicPGwBtXS9N73Te=FFeOChi-br=etgGw6R5JfAh8rQVbNA@mail.gmail.com>

On Tue, 21 Feb 2023, 22:33 sonntex, <sonntex@gmail.com> wrote:

> I want to implement something which helps me to play rtp stored in pcap
> files.
>
> tcpdump -i lo udp port 50000 -s0 -w - | ffplay <codec options> -i -
>
> The specification of pcap files is really simple and I could create a new
> ffmpeg format, but don't know how to process rtp packets extracted from
> pcap, because it seems that all functions for rtp parsing are private.
>
> Need a good example of inner ffmpeg formats processing.
>

How is ffmpeg meant to know the meaning of the contents of a pcap and the
format inside?

This is a very bad idea.

What's next, ffmpeg implementing userspace TCP? Are we going to add support
for parsing filesystems as well?

Regards,
Kieran Kunhya

>
_______________________________________________
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".

  reply	other threads:[~2023-02-21 22:38 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 [this message]
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
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='CAK+ULv6OTtO0pN7a8eV=AyXevb4EYXLUVWD8+MptzNSzWznX9A@mail.gmail.com' \
    --to=kierank@obe.tv \
    --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