Re:Microsoft FFmpegInterop library for Windows
by magicalist on Saturday January 30, 2016 @02:56PM
(#11003452)
> Depending on how that case finally comes back, I'd expect that could really affect Microsoft's strategy, here
Remember that because there were originally patent claims in the suit, the appeal went to the Federal Circuit -- even though the patent claims were dropped -- not the Ninth Circuit where the district court is located. As a result, the Federal Circuit's ruling that APIs are not uncopyrightable is not precedent since it doesn't concern patents (the Federal Circuit's remit).
Their reasoning might influence future rulings, but precedence-wise the ruling has no bearing on the future of copyright on APIs in the US.
Re:Microsoft FFmpegInterop library for Windows
by zaroth on Saturday January 30, 2016 @05:06PM
(#11004002)
The way I see it, this is an open source shim layer. I don't see any copyright issue whatsoever. Whoever chooses to use the shim is using ffmpeg anyway, so they are already exposed to the license in exactly the same way. This just makes it easier to use ffmpeg 'the right way' on various devices, if I understand correctly.
If somehow MS can't make and open source clean compatibility layers for their own software, then that's a big problem.
Re:Microsoft FFmpegInterop library for Windows
by kyberias on Saturday January 30, 2016 @03:32PM
(#11003611)
I think you're mistaken. This project does not "implement and API written by someone else". They implement a Windows API interface (MediaStreamSource) that wraps the FFmpeg library so that it can be easily used in various Windows OSs.
Re:Microsoft FFmpegInterop library for Windows
by baldfat on Saturday January 30, 2016 @08:09PM
(#11004736)
I really am liking these Microsoft projects. FFMPEG on Windows would make so many thing MUCH easier for my Audio and Video Projects. Right now ffmpeg on Windows is hit or miss for me currently.
Re:Microsoft FFmpegInterop library for Windows
by rossy on Sunday January 31, 2016 @01:20AM
(#11005467)
I have never had any trouble with FFmpeg on Windows. Even building it from source or building programs that use it is pretty foolproof with MSYS2. FFmpeg also has Windows specific features like DXVA for video decoding and (recently) Schannel for TLS.
It seems like this library is specifically for integrating FFmpeg with the built-in classes for video playback in Windows Store apps, but you don't have to use those classes to use FFmpeg on Windows.
Re:Microsoft FFmpegInterop library for Windows
by milkey_mouse on Saturday January 30, 2016 @11:19PM
(#11005205)
FFmpeg on the command line on Windows has been fine for me every time I use it, using the Zeranoe builds. They seem to come with the right codecs and everything.
Re:Microsoft FFmpegInterop library for Windows
by baldfat on Sunday January 31, 2016 @01:20AM
(#11005468)
Those are the ones I also use and it hasn't been flawless for me, BUT I tend to do a TON of video for professional production (Happens only a few times a year). I get hiccups that I don't know everyone would really notice or care about, but is HUGE for my purposes.
Depending on how that case finally comes back, I'd expect that could really affect Microsoft's strategy, here.
Remember that because there were originally patent claims in the suit, the appeal went to the Federal Circuit -- even though the patent claims were dropped -- not the Ninth Circuit where the district court is located. As a result, the Federal Circuit's ruling that APIs are not uncopyrightable is not precedent since it doesn't concern patents (the Federal Circuit's remit).
Their reasoning might influence future rulings, but precedence-wise the ruling has no bearing on the future of copyright on APIs in the US.
edit: the EFF has a little more detail:
https://www.eff.org/deeplinks/2015/06/bad-news-supreme-court...
https://www.eff.org/deeplinks/2015/06/eff-stands-innovative-...
This issue has popped up a number of times for Linux kernel modules, and at what point they are a derived work - https://lwn.net/Articles/13398/. Here is an email thread concerning this http://yarchive.net/comp/linux/gpl_modules.html.
If somehow MS can't make and open source clean compatibility layers for their own software, then that's a big problem.
Is that distinct from being copyrightable?
I'm sure that if it becomes a big enough problem, the problem will be buried in lawsuits once Microsoft or IBM or similar stub their toes on it.
It seems like this library is specifically for integrating FFmpeg with the built-in classes for video playback in Windows Store apps, but you don't have to use those classes to use FFmpeg on Windows.
Edit: Works Flawlessly in Linux.