Do you mean finding ways to crack the protection?
Originally Posted by duby229
Oh no, I would never do that if it were an option. Never.
It is how dvd support on linux came about and it will be how bd support on linux will come about... Except this time it is not going to be a simple 8 line patch that does it. It is going to take talent and those that have the talent need to do it.
I think you will find that I was being facetious. On the whole I agree with you, but until I can actually use a Bluray disc in a manner I deem appropriate I am not going to be using them. And it is hardly a necessity for me at the moment.
Same boat here, really annoying.
Originally Posted by elmariachi
As far as bluray movies go, installing libaacs and downloading a KEYDB (put into ~/.config/aacs ) file is all needed to have pretty good playback. mplayer and xbmc play blurays just fine, and as a bonus, the annoying menus don't work! Pop in and play. (oh, and the bluray has to be mounted). It's basic, a bit hands on, but possible.
I was under the impression that the new encoding scheme had not even been cracked yet for basic playback. Can you provide us with anymore information with how this was done?
Originally Posted by Serafean
It hasn't been cracked, and can't be cracked once and for all, unlike CSS.
Originally Posted by Hamish Wilson
But people have figured out how to extract keys from the discs, and if you get your hands on the crypto key, you can play the movie. One crypto key per movie, remember, so they have to keep cracking them and you need to keep getting them.
This method works with AACS protected bluray discs.
But what about BD+ protection, is that defeated too?
MakeMkv decrypts them, it seems… http://www.makemkv.com/faq/item/9
Originally Posted by MastaG
Michael, the article contains some omissions. VA-API features the following capabilities today:
Originally Posted by phoronix
* Video processing (WIP):
- Noise reduction
- Color balance (ProcAmp)
- Color conversion between various formats
- Advanced de-interlacing (temp/spatial) but no strong driver implementation yet
- Raw DRM for transcoding pipelines without any display server or even monitor attached
- GLX (deprecated)
As you mentioned, VA-API is constantly improving, so more capabilities are in the works.
Note: 10-bit per YUV component is not supported. i.e. no Hi10P.
Besides, VA-API is nothing without HW coverage (drivers) and SW coverage (applications). So far, I can count around 5 different types of hardware that could be supported by around 6 different drivers or shim layers. On the software side, most applications support VA-API nowadays too. i.e. HW and SW coverage indeed looks quite good.