From: Mark Gaiser <markg85@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v8 1/1] avformat: Add IPFS protocol support. Date: Tue, 8 Mar 2022 13:49:22 +0100 Message-ID: <CAPd6JnF3iGTorSSAAR92APJF2tJ6PYbv2dzf=M2biu2MCRSfxw@mail.gmail.com> (raw) In-Reply-To: <20220304180916.GD2829255@pb2> On Fri, Mar 4, 2022 at 7:09 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > On Thu, Mar 03, 2022 at 03:58:53PM +0100, Mark Gaiser wrote: > > On Tue, Mar 1, 2022 at 11:01 PM Michael Niedermayer < > michael@niedermayer.cc> > > wrote: > > > > > On Mon, Feb 28, 2022 at 02:09:15PM +0100, Tomas Härdin wrote: > > > > sön 2022-02-27 klockan 15:29 +0100 skrev Mark Gaiser: > > > > > Ping 2.... > > > > > > > > > > I'd really like to get this merged! > > > > > This kinda blocks me right now from proceeding with IPFS > integration > > > > > in > > > > > Kodi, MPV and VLC. Implementations in those (who rely on ffmpeg) > are > > > > > significantly easier once this patch is finally landed in ffmpeg. > > > > > > > > I'd like to hear at least one other dev chime in on this one > > > > > > what exactly are you not sure about ? > > > what exactly needs a 2nd look ? > > > > > > > My assumption. > > In general just a second look by someone other than Tomas. > > And, as he was skeptical about this patch at first, likely another > opinion > > if this makes sense to add in ffmpeg. > > To me it does very much but i'm biased :) > > ipfs support makes sense to be added to ffmpeg. ive seen ipfs urls and ive > already been annoyed that some tools dont "just" work with them. > While if i compare this to many other formats which i have never seen > outside the context of FFmpeg. So from this biased single sample that i > am, ipfs seems more widespread and thats why iam in favor of its support > > thx > > Great to have your support :) Reading that is quite motivating to work on it, no joke! Just to be clear here. Having this in ffmpeg won't make it "just work" yet. For a minimal feeling of "hey, it works out of the box" you'd need: - The next or version after the next IPFS. - MPV support which relies on this patch to even be supported in mpv - Have a node running locally Once you have those then a "mpv ipfs://<cid>" works without any additional configuration. We're getting there and this is one (admittedly very significant) step in that direction. Lastly. merge time? Could you do the honors? As I don't have the required permissions. > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Everything should be made as simple as possible, but not simpler. > -- Albert Einstein > _______________________________________________ > 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:[~2022-03-08 12:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-17 14:49 [FFmpeg-devel] [PATCH v8 0/1] " Mark Gaiser 2022-02-17 14:49 ` [FFmpeg-devel] [PATCH v8 1/1] avformat: " Mark Gaiser 2022-02-17 14:57 ` Mark Gaiser 2022-02-21 11:32 ` Mark Gaiser 2022-02-27 14:29 ` Mark Gaiser 2022-02-28 13:09 ` Tomas Härdin 2022-03-01 22:01 ` Michael Niedermayer 2022-03-03 14:58 ` Mark Gaiser 2022-03-04 18:09 ` Michael Niedermayer 2022-03-08 12:49 ` Mark Gaiser [this message] 2022-03-08 23:45 ` Michael Niedermayer 2022-03-09 0:30 ` Mark Gaiser 2022-03-09 9:35 ` Michael Niedermayer 2022-03-11 13:45 ` Mark Gaiser 2022-03-12 15:14 ` Michael Niedermayer
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='CAPd6JnF3iGTorSSAAR92APJF2tJ6PYbv2dzf=M2biu2MCRSfxw@mail.gmail.com' \ --to=markg85@gmail.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