On 18 Feb 2012, at 17:46, compn <[email protected]> wrote: > On Sat, 18 Feb 2012 16:39:33 +0100, Reimar Döffinger wrote: >> I don't know anything about libbluray - don't use it, don't have it >> installed. I can suggest the below, but it is vague and I don't >> intend to get more explicit. >> Index: src/news.en >> =================================================================== >> --- src/news.en (revision 3610) >> +++ src/news.en (working copy) >> @@ -13,6 +13,17 @@ >> </h2> >> >> <p> >> +Correction: MPlayer does support encrypted BluRay playback, though we do not >> +deal with how to obtain decryption keys. The two alternative methods use the >> +URL schemes bd:// (always supports decryption, but you need the key for each >> +and every disk in ~/.dvdcss/KEYDB.cfg and only works well with very simple >> +BluRays, similar to dvd:// vs. dvdnav://) and br:// (uses libbluray and >> +supports whatever that supports/was configured to support - if done >> +correctly that should be the same as VLC mentioned below, but we >> +are not involved in that). > > its very vague and doesnt explain how the keydb.cfg has to be formed or > the format/template of how keys are supposed to be listed in it. but > that info would probably do better in the DOCS anyhow. > > why are the keydb.cfg different from vlc to mplayer? seems confusing.
They shouldn't be different, MPlayer cannot make use of all entries in it/it is an older format. Or to put it differently: one that works for MPlayer should work for VLC, just not necessarily the other way round. Note that I don't like the VLC method (unless it updates it?): It can happen that you put in a new BluRay in the drive and suddenly none of your disks play any more. _______________________________________________ MPlayer-DOCS mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/mplayer-docs
