[Ffmpeg-devel-irc] ffmpeg-devel.log.20190309

[burek]

[10:29:29 CET] <sourabhboss> Hello ffmpeg - devel developers I will like to work on HEIF Support project during GSoC 2019
[10:29:55 CET] <sourabhboss> I have a required prequisites 
[10:32:06 CET] <durandal_1707> sourabhboss: contact mentor and you need to complete Qualification Task
[10:32:45 CET] <sourabhboss> Sure durandal_1707 
[10:33:55 CET] <sourabhboss> If someone already working on it Pls ping me 
[10:54:20 CET] <sourabhboss> Anyone know timezone of cehoyos
[10:55:45 CET] <durandal_1707> sourabhboss: he is never on irc
[10:56:02 CET] <durandal_1707> you can contact him only by mail
[10:57:24 CET] <sourabhboss> Okay
[16:33:23 CET] <cone-479> ffmpeg 03Andriy Gelman 07master:0a84ba26081c: avformat/mpegts: reduce buffering during initialization
[16:33:23 CET] <cone-479> ffmpeg 03Michael Niedermayer 07master:f94b4f161151: avformat/mpegts: Simplify score compare
[16:33:23 CET] <cone-479> ffmpeg 03Michael Niedermayer 07master:6e0b5d3a20e1: avcodec/dxv: Correct integer overflow in get_opcodes()
[18:47:22 CET] <kierank> do we need a power9 fate?
[18:51:31 CET] <jamrial> kierank: probably. there are some ppc64 fate clients, but i think those are power8
[18:51:54 CET] <kierank> I spoke to power9 people at SCALE they said it's easy for us to get a VM
[18:52:21 CET] <jamrial> http://fate.ffmpeg.org/report.cgi?time=20190309154448&slot=ppc64le-linux-gcc-8 looks like this one is power9
[18:52:26 CET] <jamrial> not sure who's "mik"
[18:52:55 CET] <jamrial> but redundancy may be a good idea anyway
[18:53:09 CET] <jamrial> and michaelni wanted more fate clients also testing release branches
[19:43:24 CET] <cone-672> ffmpeg 03Kieran Kunhya 07master:2ff7af563a25: vf_showinfo: Fix timecode display
[19:48:47 CET] <kierank> removing libndi
[19:48:55 CET] <durandal_1707> what?!?
[19:49:03 CET] <kierank> I said I would do that
[19:49:10 CET] <durandal_1707> no consensus was reached
[19:49:19 CET] <kierank> https://trac.ffmpeg.org/ticket/7589
[19:49:21 CET] <kierank> there is consensus
[19:49:22 CET] <durandal_1707> you need to put it to ML
[19:49:26 CET] <kierank> it already was
[19:49:28 CET] <kierank> carl did it
[19:49:30 CET] <durandal_1707> trac is not ML
[19:49:35 CET] <kierank> https://patchwork.ffmpeg.org/patch/11263/
[19:50:32 CET] <durandal_1707> contact Carl before you gonna push your removal
[19:51:19 CET] <kierank> done
[19:52:01 CET] <j-b> +1
[20:49:19 CET] <cone-672> ffmpeg 03Martin Vignali 07master:26cf50404d1a: avcodec/proresenc_aw : fix interlace encoding for unsafe height
[21:12:16 CET] <kierank> j-b: durandal_1707: see ml
[21:15:15 CET] <JEEB> ayup
[21:15:18 CET] <JEEB> they've gone silent
[21:22:21 CET] <jamrial> kierank: don't remove the empty line in changelog
[22:17:06 CET] <BtbN> They fixed the license violation, and were asked to release all their stuff under GPL. So yeah, I can totally see why they did not reply to that.
[22:18:00 CET] <BtbN> Also, removing NDI require a major bump and deprecation period.
[22:20:04 CET] <durandal_1707> BtbN: bullshit, that is not needed
[22:20:13 CET] <BtbN> It's an ABI break
[22:20:36 CET] <BtbN> Not in the classical sense, but programs will stop working without warning.
[22:26:21 CET] <jamrial> we have removed wrappers without deprecation period before. all those external aac encoders, libdcadec, etc
[22:26:52 CET] <jamrial> and i bet more people used libfaac than libndi
[22:35:06 CET] <kierank> BtbN: they threaten open source developers with legal threats
[22:35:20 CET] <kierank> why should we help them
[22:35:50 CET] <BtbN> I still wasn't able to find anything about that. The only side of the story I know is from their perspective.
[22:36:07 CET] <kierank> they threatened someone who implemented ndi indepdentetly
[22:36:39 CET] <BtbN> Wasn't it about reverse engineering their library, which is against the license?
[22:36:50 CET] <kierank> no
[22:36:52 CET] <kierank> not in europe
[22:36:56 CET] <kierank> those terms are meaningless
[22:37:15 CET] <BtbN> Well, then you can probably just safely ignore any threaths. Github might kick you though, since US based.
[22:37:23 CET] <kierank> ...
[22:37:32 CET] <kierank> missing the point entirely
[22:37:43 CET] <kierank> why should we support ndi in an open source project, when they threaten open source developers
[22:37:58 CET] <BtbN> I'm more concerned about users than the company.
[22:38:17 CET] <kierank> well users are compiling themselves
[22:38:18 CET] <BtbN> Cause I know quite a lot of people who use NDI, and there is a distinct lack of alternatives.
[22:38:20 CET] <kierank> so they can do what they want
[22:38:28 CET] <BtbN> No, majority of them definitely is not.
[22:38:35 CET] <kierank> then they are violating the gpl
[22:38:39 CET] <kierank> so why should we care
[22:38:46 CET] <BtbN> Yeah, why care about users.
[22:38:55 CET] <kierank> yes why should we care about gpl violators
[22:39:02 CET] <iive> if it is the same thing I think it is, then the proprietary version also has some known exploits.
[22:40:05 CET] <kierank> newtek clearly are using ffmpeg to push their crappy blob
[22:40:13 CET] <kierank> and attack people who want to remove the blob
[22:42:19 CET] <kierank> we wouldn't accept it if it was dolby, microsoft etc
[22:42:30 CET] <kierank> but because someone put it in and started using it doesn't make it right
[22:56:29 CET] <iive> if there is an open source alternative to NDI, does ffmpeg support it?
[22:56:32 CET] <iive> got any links?
[00:00:00 CET] --- Sun Mar 10 2019