From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 148FD457EA
	for <ffmpegdev@gitmailbox.com>; Wed, 22 Feb 2023 12:54:06 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5742968BFF0;
	Wed, 22 Feb 2023 14:54:03 +0200 (EET)
Received: from ursule.remlab.net (vps-a2bccee9.vps.ovh.net [51.75.19.47])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id BEB4E68BFBC
 for <ffmpeg-devel@ffmpeg.org>; Wed, 22 Feb 2023 14:53:56 +0200 (EET)
Received: from ursule.remlab.net (localhost [IPv6:::1])
 by ursule.remlab.net (Postfix) with ESMTP id 08EBFC000A;
 Wed, 22 Feb 2023 14:53:55 +0200 (EET)
Received: from [127.0.0.1] ([212.149.142.231])
 by ursule.remlab.net with ESMTPSA id vv6YO2MQ9mNYfQ4AwZXkwQ
 (envelope-from <remi@remlab.net>); Wed, 22 Feb 2023 14:53:55 +0200
Date: Wed, 22 Feb 2023 14:53:55 +0200
From: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>,
 Gijs Peskens <gijs@peskens.net>, ffmpeg-devel@ffmpeg.org
User-Agent: K-9 Mail for Android
In-Reply-To: <b3ebec32-5df6-db7c-31b9-f7fd4d2743ae@peskens.net>
References: <CAPeTicPGwBtXS9N73Te=FFeOChi-br=etgGw6R5JfAh8rQVbNA@mail.gmail.com>
 <CAK+ULv6OTtO0pN7a8eV=AyXevb4EYXLUVWD8+MptzNSzWznX9A@mail.gmail.com>
 <CAPeTicPFCP+txmxwVKTbwrktW-MqX+JmWaVpAcFdsu-tkSbvfg@mail.gmail.com>
 <b3ebec32-5df6-db7c-31b9-f7fd4d2743ae@peskens.net>
Message-ID: <57B02A18-17B3-4BA8-A4AF-E7BA00289E54@remlab.net>
MIME-Version: 1.0
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: [FFmpeg-devel] How to implement pcap ffmpeg format?
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/57B02A18-17B3-4BA8-A4AF-E7BA00289E54@remlab.net/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

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