Just a quick heads up…for some strange reason, the “Star_Wars_SSE_TN1_v1_6.iso” appears to have AACS protection AND (I believe as a direct result) would NOT load properly in a “stock” copy of the current VLC (v2.2.4) for Mac and produced the following error message:
Blu-ray error
This Blu-ray Disc needs a library for AACS decoding, and your system does not have it.SOLUTION:
Please visit http://vlc-bluray.whoknowsmy.name/ to DL and install the current “Keys database” and “AACS dynamic library” for your Windows, MacOS X or Linux-based system.
[NOTE: Under MacOS X, the “~/lib directory” that you’ll want to copy your DLed “libaacs.dylib” to may be found by right-clicking the VLC app, selecting “Show Package Contents”, and navigating to “~Contents -> MacOS -> lib”.]This took me a little while to find the above website AND to work through a less than fully clear MacOS instructions.
Huge THANKS go to Williarob and Team Negative1 (and other project contributors) for producing such a quality preservation!
Kind regards,
-A.S.
I might be mistaken, but I think it’s not real AACS encryption. Deleting the AACS folder might be sufficient to getting it to load. Haven’t tested it on this exact release, but it is the case for others built this way.
towne32-
BDInfo ALSO reports AACS encryption (in a scan of the BDMV folder)…
AACS QUICK SUMMARY:
Disc Title: Star_Wars_SSE_TN1_v1_6
Disc Size: 40,307,313,340 bytes
Protection: AACS
BD-Java: No
Playlist: 00001.MPLS
Size: 37,538,162,688 bytes
Length: 2:01:15.393
Total Bitrate: 41.28 Mbps
Video: MPEG-4 AVC Video / 33993 kbps / 1080p / 23.976 fps / 16:9 / High Profile 4.1
Audio: English / LPCM Audio / 2.0 / 48 kHz / 1536 kbps / 16-bit
Audio: Spanish / LPCM Audio / 2.0 / 48 kHz / 1536 kbps / 16-bit
Audio: English / LPCM Audio / 1.0 / 48 kHz / 768 kbps / 16-bit
Subtitle: English / 31.947 kbps
Subtitle: Spanish / 31.366 kbps
Subtitle: German / 36.134 kbps
Subtitle: French / 26.990 kbps
Subtitle: Italian / 30.846 kbps
Subtitle: Finnish / 30.025 kbps
I am no expert in the field of AACS encryption, however, I might hazard a guess that perhaps some setting in the Blu-ray mastering software used could be the culprit? In any event, while it was a bit of a pain in the ass to find and sort out the details of a workaround…this is certainly NOT a show-stopper.
I expect that the AACS encryption was almost certainly unintentional. My intent in sharing my findings were to report the issue, share the workaround that I found, and IF a v1.6.1, v1.7, or a v2.0 are ever released…addressing the detected AACS encryption could make it into into agenda somewhere?
On behalf of myself (AND my two boys), I do REALLY, REALLY appreciate the fruits of the labors of Williarob and the rest of Team Negative1 (and contributors) for sharing this beautiful “fan preservation” with us!
Cheers!
-A.S.