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 9B185465E2 for ; Thu, 22 Jun 2023 15:01:21 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7CEA868C124; Thu, 22 Jun 2023 18:01:18 +0300 (EEST) Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 8605C68C081 for ; Thu, 22 Jun 2023 18:01:11 +0300 (EEST) Received: by mail-oi1-f176.google.com with SMTP id 5614622812f47-38dec65ab50so5346359b6e.2 for ; Thu, 22 Jun 2023 08:01:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687446069; x=1690038069; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=dLVadp7ntKRl+rQphzsQ3WvKSC+SNnGTNL6dfEEXKH0=; b=EiHOiMQydacQlrtjEZsHpgoYN/b0rRUpvW7Ryd+7RsDIjPkYuOvPGP6zoUmsteEblh c6nEKmgkR6fR8euPGdrN5540ahfgQxwEDOpVISKOhKxLC7//S0wR0MFDantF/Mn9Lrpp mPMFEopT5rr0xedVqUSLJgafm0MDBM3larNk2+WjDG51btyaad6q4osbpUVBcF+MWX1q S+7lElgvz5Zs7XwFqg0giooKkTfMC8a1zSQWYFajnfOkwpxyps4FmFNgr52O5pAdDyP0 Ws/x51E2Op/rfpkrDJ6Us30pb7msNdb0lKkb2+q6ObqxgKZfbqipd4t004GR0XeAlPo6 mjuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687446069; x=1690038069; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=dLVadp7ntKRl+rQphzsQ3WvKSC+SNnGTNL6dfEEXKH0=; b=KNj9MXBzX1glGoBrmInh6mkXUlRMMV1Fb3rY5IoBOi0bUYBY5bsAgvl1R1dgK8kfmu h1P2fZwqBDdlM+YS84I5mQEOz9uQDF86rklb0s+irhiYTTEKImZXFj61nTkwDVY9HEK5 6pFVw/L+22K2khDjQAWuaSyr99CdhNUoPTC10ffW82tqRSeM0Pslp06HFJtEFF4g8be+ H8wABec5TsORjNzSqSphEB4cbwBSnpXBNnxkq5mTd+TJaQhF4aLmuo1UhlqljrM/nCLT vJfEgsy7kdGSqrCCcWBoXESiBRLeyWCxZyttMT9xtvx7v9XxStN+oETplRIoVInYhh6D U7HQ== X-Gm-Message-State: AC+VfDzahTqmAmuXceLrOMvd502jh7oTYs85bM5B/mDkdmucBDRzaYMP eYFRofN8iftxf+XFpaKFBCZrSn86npo= X-Google-Smtp-Source: ACHHUZ71Fy6l1O6Q2yhAYc5m3NUWBD0uJABb1kVyK3vvaSt86clOSnem/wp4Tg1oxXHOtsfMgieSkw== X-Received: by 2002:a05:6808:2810:b0:398:4761:20d with SMTP id et16-20020a056808281000b003984761020dmr18626154oib.19.1687446069154; Thu, 22 Jun 2023 08:01:09 -0700 (PDT) Received: from [192.168.0.12] (host197.190-225-105.telecom.net.ar. [190.225.105.197]) by smtp.gmail.com with ESMTPSA id bh26-20020a056808181a00b00397fb7fcc31sm3196253oib.45.2023.06.22.08.01.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Jun 2023 08:01:08 -0700 (PDT) Message-ID: Date: Thu, 22 Jun 2023 12:01:07 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <20230622145709.GB3250409@pb2> From: James Almer In-Reply-To: <20230622145709.GB3250409@pb2> Subject: Re: [FFmpeg-devel] [RFC] SDR 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: On 6/22/2023 11:57 AM, Michael Niedermayer wrote: > Hi all > > My humble opinion(s) and plan(s) about SDR > > FFmpeg as a multimedia framework should support SDR. > > The only practical way to support SDR in FFmpeg ATM is through a demuxer (or equivalent) > Not everyone is happy about a SDR demuxer. > > The "active" code could be in the demuxer itself or an external library. > > I think the 2 important factors for external vs internal are > 1. Does it support features beyond what a multimedia framework needs? > 2. How many active developers work on it > > If we support just audio and video (de)modulation it fits nicely in FFmpeg > maybe we should consider improving the APIs we have so we have better places > than demuxers for functionality like this, but thats a long term goal that > requires a team effort or a dedicated volunteer. Its not a bad idea at all and > I certainly am in favor for improving the APIs. > > OTOH if we support things beyond audio/video, maybe wifi packets, bluetooth > and so forth then SDR should be a seperate library. > > Also this choice is not a constant, we can easily start out inside libavformat > and > * if sdrdemux grows beyond what makes sense in FFmpeg split it out into an external > libraray > * if APIs in FFmpeg evolve so that other places become possible, move it into > libavfilter or whatever other place fits better > > What i would suggest is: > * get the current code or revission of it into the git master branch as a demuxer. > * see how many people enjoy working on SDR and how far these people want to take it > * keep an open mind about the future of this code, and move it elsewhere when it > makes sense to do so. > * ATM i think incubating this SDR stuff in FFmpeg and have it grow makes more sense > than having it in a seperate place and a demuxer in FFmpeg depending on that. > > PS: Also something like plugins would help for things like this. As one could then > maintain code like a sdr-demuxer outside the main repository. So noone who doesnt > like it needs to touch it in any way while users who want it can easily enable > it ... > > Thx Add it as an input device in lavd, since it's after all a capture device. Share the common code with the "file" demuxer in lavf using avpriv, since lavd and lavf are completely intertwined. Just my 2 cents. _______________________________________________ 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".