From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 7CB9F457D8 for ; Wed, 22 Feb 2023 08:04:35 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D1ADD68BFEA; Wed, 22 Feb 2023 10:04:31 +0200 (EET) Received: from smtp.heteigenwijsje.nl (smtp.heteigenwijsje.nl [185.216.161.180]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C5ECF68BFAC for ; Wed, 22 Feb 2023 10:04:25 +0200 (EET) Received: from mail.heteigenwijsje.nl (localhost [127.0.0.1]) by smtp.heteigenwijsje.nl (Postfix) with ESMTP id D603D5E7C9 for ; Wed, 22 Feb 2023 09:04:24 +0100 (CET) Authentication-Results: mail.heteigenwijsje.nl (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=heteigenwijsje.nl DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= heteigenwijsje.nl; h=content-transfer-encoding:content-type :content-type:in-reply-to:from:from:references:to :content-language:subject:subject:user-agent:mime-version:date :date:message-id; s=dkim; t=1677053060; x=1679645061; bh=16X4cQG iH1+K2y6L7u2JmHrVsXHHhqh/4pG1Sc11CsE=; b=RHzMpQF13k4v3U3IzVGefBz uufUymtGPp0xbW0JBRMryhNUM4/uXysNhMU81oQbWpZfLCBmTn6ENTRvOjXRJ5ZG iT6ISJFDasZeSrajyBppUAUwDBQexslf003KTJYnyL1T9bCE5U5iKhqGm/rJHy/9 q/tGM48LDIXqau8Uz794= X-Virus-Scanned: amavisd-new at mail.heteigenwijsje.nl Received: from smtp.heteigenwijsje.nl ([127.0.0.1]) by mail.heteigenwijsje.nl (mail.heteigenwijsje.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SBj3iwL7Y4q0 for ; Wed, 22 Feb 2023 09:04:20 +0100 (CET) Received: from smtp.heteigenwijsje.nl (localhost [IPv6:::1]) by smtp.heteigenwijsje.nl (Postfix) with ESMTP id 9B93D5EC83 for ; Wed, 22 Feb 2023 09:04:20 +0100 (CET) Received: from [IPV6:2a03:10c3:578:1:858e:caee:6573:6c75] ([2a03:10c3:578:1:858e:caee:6573:6c75]) by smtp.heteigenwijsje.nl with ESMTPSA id aNckI4TM9WPndgEAc3PRCQ (envelope-from ) for ; Wed, 22 Feb 2023 09:04:20 +0100 Message-ID: Date: Wed, 22 Feb 2023 09:04:20 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: From: Gijs Peskens In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Wouldn't the simplest solution just be a tiny tool that unwraps the pcap stuff and just passes the packet data out on stdout? That's assuming ffmpeg allows receiving RTP packets on stdin. On 21-02-2023 23:55, sonntex wrote: > New pcap ffmpeg format can have all options rtpdec requires. > > Anyway, I don't suggest you implement this feature. I just want to find a > good entry point to start coding personally. > > I need to create a development tool for rtp tracing, and pcap files seem a > good idea because I can grab rtp using tcpdump, or create pcap files > directly in my application, or whatever. It's better then wrap vp8/vp9 to > ivf or h264 to byte stream and pass it to ffmpeg via pipe because it > doesn't require coding of new solutions for every video and audio formats > transferring over rtp. > > On Tue, Feb 21, 2023 at 10:38 PM Kieran Kunhya wrote: > >> On Tue, 21 Feb 2023, 22:33 sonntex, 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 -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". >> > _______________________________________________ > 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".