As I recall, installing libdvdcss, libdvdnav, libdvdread from the official repos solved that problem and allowed me to painlessly watch dvd's through players like VLC and MPlayer.
367 karma · joined May 27, 2016
As I recall, installing libdvdcss, libdvdnav, libdvdread from the official repos solved that problem and allowed me to painlessly watch dvd's through players like VLC and MPlayer.
The video encoding patents are many, and of course written to be as broad as possible.
That said, AV1 will be built on VP10, which is the last of the VPX series of codecs, which in turn have been royalty free for their entire existence (VP7-VP10), to this we can add h264 functionality which are covered by Cisco patents (a core member of AOM) and some features from Daala which are considered non-patented.
Hopefully the AOM consortium has done their due diligence, and thus will be able to effectively fight patent litigation threats which will most likely occur, what speaks in favour of this are the impressive lineup of AOM, with Google, Microsoft, Cisco, Netflix, Amazon, Intel, AMD, ARM, Broadcom, etc, many of which own patents related to video encoding, as well as a very strong motivation to rid themselves of video royalties once and for all, both regarding distribution and hardware implementation.
>(I absolutely hate that this is something I'm worried about)
You and me both. We have great royalty free audio codecs (FLAC, OPUS), good enough royalty free image codec (JPEG, could potentially be replaced by a superior royalty free codec based upon AV1), it would be great if we could have the same for video as well.
There is Wayland which aims to solve these security aspects mentioned in the blog post, it will be shipping by default in the next Fedora release IIRC.
platform native https://github.com/andlabs/ui
gtk http://mattn.github.io/go-gtk/
qt https://github.com/therecipe/qt
qml https://github.com/go-qml/qml
shiny (still being developed, Go native) https://github.com/golang/exp/tree/master/shiny
I have to disagree, first off, it's not as if we've seen a massive shift over to HEVC, in fact the x265 developers lamented this quite recently, mainly blaming the licensing debacle which has ensued, with three different entities with which you need to negotiate royalties in order to use HEVC (MPEGLA, HEVC Advance, Technicolor), and the royalties were already much more expensive than h264 to begin with.
Secondly, it's quite clear that AV1 will happen, Google was already committed in creating a royalty free codec as evident by their VPX series of codecs, and now they have been joined by web and tech giants like Netflix, Microsoft, Amazon, Cisco, Mozilla, Intel, ARM, NVidia, AMD etc.
For these players, a royalty free codec makes perfect sense, the streaming giants know full and well that they will only increase the amount of video they stream and thus will save money longterm by pooling their resources and creating a royalty free codec, and on the hardware side, not having to pay royalties in order to implement hardware support is obviously attractive.
And it does exist, it's in full development, not something in the 'planning stage', the bitstream is said to be finalized at the end of this year or at the beginning of next, so we are not talking 'many years into the future' here, it's based off VP10 and is adopting techniques from Daala and also have access to h264 patented techniques courtesy of Cisco.
As I see it, HEVC is in a bad situation, h264 is still good enough and much cheaper to license, and within a year we will likely have AV1 ready to go for hardware, why would you jump on the HEVC bandwagon at this point ?
My best suggestion would be to just stick with h264 and see how the HEVC/AV1 situation plays out.
Danese Cooper who was responsible for drafting the actual license while at Sun says another thing.
Obvious business sense stands firmly with Danese, it would be very stupid of Sun to hand over the best technological advantages of Solaris to their main competitor, which was Linux, while struggling against it in the market.
Open-sourcing Solaris was a last ditch effort from Sun to attract mindshare (and eventually market share) back from Linux, that plan would be doomed beforehand if Linux could just pick the best parts of Solaris for inclusion.
Crafting a new GPL incompatible license for ZFS and DTrace resulted in Linux not being able to incorporate them.
These are both using a incompatible license (CDDL), they can't be merged into mainline.
Where have you read that Linus doesn't want to integrate it ?
From the LKML response it sounded as if he wanted more explanation of how it solves certain things.
What exactly in Snowdens leaks would increase the chance of terrorist attacks on the US ?
And just to drive home the dire situation he is in, when rumours were spread of Snowden being aboard the Bolivian president's plane headed for latin america, the US pressured european countries to deny airspace and have it directed to Austria where it was searched.
Beyond that it's closed source, so it would require the Paint.NET developers to port it to Linux.
Wine is probably going to be your best bet.
Sure I am, but that meme was (still is?) repeated as a joke, did anyone actually believe it ?
>Also in the old days it was fashionable to try all WM and post screenshots of our setups, specially on weekends.
People still do that, there's a reddit sub dedicated to it: https://www.reddit.com/r/unixporn ,but then again there's a reddit sub dedicated to just about everything.
Just like there are stamp collectors, train spotters, rock climbers, ballroom dancers etc, there are people who find enjoyment in tweaking/expressing themselves through 'pimping' their computer environment, I see nothing wrong with that although it's not my cup of tea.
After having configured my environment of choice according to my specific needs I leave it alone and instead waste my spare time on places like Hacker News ;)
Not really sure what you mean here, I choose a particular WM setup which best serves my workflow, and that's pretty much it, it's not as if you have to continously tweak your setup.
>This is yet another reason why GNU/Linux lost the desktop
Can't really see how it 'lost' the desktop, it never had it, nor was it ever in the runnning to claim it, same goes for OSX despite having a ton of product placement, straight up advertising and riding the huge wave of pro-Apple consumerism in the mobile space.
In short, I don't believe for a second that standardising on a particular UI would have made any difference in 'drawing the masses', if super wealthy Apple at it's prime couldn't, then neither would Linux.
Looking at Rust vs Go over at 'benchmarksgame' (granted these are micro-benchmarks), Go seems to compare very well for tests that are mainly computational and thus avoid involving the GC very much (even beating Rust on a couple).
http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan...
And let's not forget that Go hasn't really had any focus on optimizations up until the last release where SSA was introduced.
Anyway, maybe I'm projecting as I would like to see a full Rust toolchain in Rust, and my (very possibly entirely wrong) impression is that Rust devs have been struggling with getting the full performance potential of Rust through LLVM.
Actually I did a benchmark run not that long ago between Gccgo and Go with the latter winning most of the benchmarks, I believe this mainly has to do with Gccgo lacking escape analysis.
Also not sure that reaching optimization parity with LLVM is an absolute necessity, Clang/LLVM is not as good at optimizing as GCC but that hasn't rendered it unpopular.
Looking at Go as a benchmark, the compiler seems to be improving the optimization at a good pace and supports X86, ARM, PPC, MIPS, S390 despite being relatively young language and also having recently rewritten the compiler.
I would not be surprised if down the line, the Rust devs decided to write their own Rust backend rather than relying on LLVM.
Actually I can't recall Lightwave ever having NURBS, it was all polygon/subdivision surfaces.
Maya has NURBS, and there is NURBS oriented software like Rhino3d, Blender also has rudimentary NURBS support.
>Are they still used frequently in 3D modeling?
I believe it's still the standard for anything requiring precision: computer aided manufacturing/design (CAM, CAD).
That makes no sense to me, given that it runs on Linux as well as BSD.
From what I've read it relies on Qt, Fluxbox, XScreensaver etc, which are hardly BSD based components.
>as opposed to the Linux model where everything is developed independently and then glued together to form a distro.
What's the difference here ?
Lumina is developed independently, the components Lumina builds upon are developed independently of Lumina, it is then glued together with PC-BSD into TrueOS.
Compression time is indeed the achilles heel of Brotli, which is why it's something I would only use for compress once (and preferably decompress very often) scenarios.
Compared to lzma at it's best compression setting for this particular data (-mx9 -m0=LZMA:d512m:fb273:lc8), brotli took 6 minutes and 4 seconds to compress, while the same data took 1 minute and 47 seconds for lzma.
On the other hand, brotli decompressed the same data in 0.6 seconds, while it took lzma 2.2 seconds.
Uh ? What format of data was this ?
I did a pretty large test (2gb+) on OBJ/STL 3d data and brotli compressed within ~5% margin of lzma, and this holds true on other binary data I've compared.
It also compressed better than zstd (as in compression ratio) on the same data at their highest respective compression settings:
bro -quality 11 -window 24
zstd --ultra -22
So I find it baffling that you find brotli to be poor for any binary data, could you share the data in question ?
That only causes problems for vendors who only supplies proprietary drivers, of which there are very few these days (only ones I've personally come across are NVidia and Broadcom), and it's not as if the unstable ABI prevents them from supporting Linux either, since they do.
Beyond that, reasons for why you'd want open source drivers are many, like the kernel devs being able to figure out and fix problems without having to rely on a third party (vendor), upgrade drivers to make use of new kernel functionality without waiting for the vendor to comply/agree, being able to audit them for security problems, being able to port them to every platform on which Linux runs, which includes platforms which the hardware vendor might not think worthwile to support, and of course other systems alltogether like the BSD's (stable ABI sure didn't get them more proprietary drivers), fringe OS'es like Haiku, Minix etc.
So no, the answer is not to lose the flexibility of a changeable ABI, but to have vendors either supply fully open source drivers or the documentation necessary for creating open source drivers, which is pretty much the situation we have today, again with a few aforementioned holdouts.