View Full Version : BlurayTestAndDecrypt - tool to test bluray files and remove AACS
nalor
20th August 2016, 21:45
Created another small tool mainly for my personal needs, but enhanced it a little bit because of @Hironimo s question for a tool to decrypt m2ts files.
In short:
can be used to check if a bluray m2ts or bluray iso file is damaged or not
can be used to remove aacs protection from a bluray m2ts or bluray iso file in case the VUK is available in the keydb.cfg file
can repair BD+ protection damages in case a fixuptable is provided
can dump/rip discs and check the final iso for errors
I've >1000 DVDs in my collection and also >100 Blurays but simply no space in the living rooms - so I decided to rip them all to harddisk and store the discs in the basement. Unfortunately not all rips are 100% correct - I noticed problems during the playback for a few of them and so I started this tool to verify if the iso created from a bluray has errors or not.
This is now 'Mode 1' in the tool. When I copied the decrypt-procedures from FindVUK into this tool I created the other 3 modes.
# Mode 1 - Simple Test
Each m2ts file on a bluray can be sliced into units of 6144 bytes length and the first 16 bytes of each unit are always unprotected and can be used to check 2 details.
In case the 'copy permission indicator' is set to 'unit encrypted': is the mpg-ts-synchronisation-byte of the first mpg-block correct? (this is byte 5 of each unit and has to be 0x47)
And in case it is not protected: check if all synchronisation-bytes are set correctly (unit is further sliced into mpg-transport-packets of 192bytes length) and the synchronisation byte for each packet is verified.
This mode is the fastest test mode and does not require a VUK for the bluray! (but it cannot detect all defective units in encrypted files)
>> this test takes ~3 Min for an encrypted bluray iso read from my internal SSD (it detects 491 error-units in my damaged test-iso file)
# Mode 2 - Test incl. decryption of each encrypted unit
performs the same tests as before and additionally checks if each encrypted unit can be correctly decrypted with VUK (read from keydb.cfg) (>> all synchronisation bytes are set correctly after decryption)
This mode requires a VUK in the local keydb.cfg file for the disc!
>> this test takes ~7 Min for an encrypted bluray iso read from my internal SSD (it detects 514 error-units in my damaged test-iso file)
# Mode 3 - Decrypt but stop on error
Basically the same as Mode 2 - but this time all decrypted units are written to disc but it stops in case a defective unit is encountered.
# Mode 4 - Decrypt but continue on error
Identical to Mode 3 with the small difference that it continues in case of an error (but only successfully decoded units are written to the destination file)
# Mode 5 - ISO2ISO or ISO-Inplace Decrypt (decrypts AACS and repairs BD+)
New mode introduced with 0.41 (ISO-Inplace since 0.61) - complete disc structure remains unchanged!
# Mode 6 - List UnitKeys
New mode introduced with 0.48 - the correct unit keys for all files are listed (nothing get's decrypted - just an info mode)
# Mode 7 - Dump disc and test final iso file for errors
New mode introduced with 0.62
To use it simply drag one of the supported items on the exe-File:
m2ts File
ISO File
a drive letter with a bluray
A few settings can be set in an ini-file, the most important ones are:
AlwaysAskMode >> if set to 1 you get always the menu to select the desired mode, if set to 0 the previous mode is used
AlwaysAskDest >> if set to 1 you'll always have to choose the destination directory, if set to 0 the previous destination directory is used
And now a few words about the BD+ repair feature:
Basically BD+ introduces damages to the video files and usually all the BD+ fuzz is to get hands on the fixup-table to repair those damages.
libbdplus stopped working a long time ago - so at the moment there's no 'open source' way to get hands on fixup tables - but there are commercial applications that help us in this case :)
Pavtube BdMagic is the tool of my choice (honestly I haven't found it myself - got a hint from another member here in the forum - so kudos to him! ) - if you need a table for a disc just start the tool, open the disc and it downloads the table for this and stores it in your userfolder.
BTD now scans all available tables and in case it finds one that matches the current disc if converts it into the 'open source' convtab format and stores the converted table in the directory userfolder\appdata\roaming\bdplus\convtab
You can view those tables with 'ConvTableView' if you're interested.
In case you don't need the Pavtube application for something else, you can set the ini value 'DeletePavtubeTableAfterConversion' to 1 so the source table is always deleted after the conversion to the convtab format.
But be aware that Pavtube is sometimes wrong - I've one disc in my collection were it downloads a fixup table that does not belong to the disc... so usually it's working fine, but sometimes it fails.
Finally the video files are correctly playable - but it's possible that the BD-J menu is not working. Usually the BD+ VM and the BD-J menu interact with each other - and in case the BD+ VM isn't running at all, the menu doesn't load at all (e.g. on the disc 'Hitman' I get a message that my player needs a firmware update - but the original disc plays without problems and in case I'll remove all protections with the fox it's also working as expected - but in this the JAR files of the menu are completely different in comparison to the original files, so this is nothing that can be done easily and will never be part of BTD ;)
History of the tool:
20160820 .. 0.18 First public release
20160821 .. 0.20
FIX: endless loop when multiple files are dragged on the exe
FIX: do not write a single logline for each defective unit
FIX: MemoryLeak in 'AACS_DecryptUnit'
CHANGE: added OnError support (provides useful details in case of a crash)
FEATURE: rename ISO file depending on result (either add (OK) or (ERR) to file) - can be enabled in ini-file
FIX: crash in case a file already starts with a completely empty unit
20161030 .. 0.41
FEATURE: ISO files can be read directly virtual drive not necessary any longer
FEATURE: ISO2ISO decryption possible (complete disc structure remains unchanged, only AACS and BD+ are decrypted/repaired)
FEATURE: BD+ repair with fixuptables
CHANGE: ini parameters to define if mode selection is always possible
CHANGE: ini parameters to define if input of destination folder is always possible
CHANGE: new ini parameter to define if pavtube bd+ tables should get deleted after conversion to convtab format
CHANGE: new bdplus-convtab path: "?FOLDERID_RoamingAppData?\bdplus\convtab" (because \bdplus\ is already used by libbdplus)
FIX: crash in case the file disappears (e.g. unmount of iso)
FIX: error in case an unprotected iso should be checked - now the AACS values are only initialized in case an AACS folder can be found on the disc
20161110 .. 0.42
FIX: check if the outputdir has a \ at the end (stupid error - already implemented check never did something useful :( - fixed it now )
FIX: take care that 1) correct and 2) identical outputdir/file are used for aacs and bd+ processing
20161111 .. 0.43
FIX: drive mode didn't work at all (wrong destination file used - now the name of the destination file is also written to logfile in case it fails)
20161111 .. 0.47
FIX: error processing unencrypted m2ts files
FEATURE: get BD+ fixuptables from leawo blurayplayer
FEATURE: read also mediakey+volumeid or unitkeys from keydb.cfg file
CHANGE: rewrite of logging engine (and splitting 90% of the source into separate modules for easier maintenance)
20170121 .. 0.48
FIX: removed preceding whitespace in loglevelprefix for logoutput
CHANGE: settings module integrated
CHANGE: new mode - list correct unit keys for files
CHANGE: changed to console-mode
CHANGE: added icon
20170203 .. 0.51
CHANGE: new ini parameter to decide if destination file should be deleted in case of an error
BUGFIX: now rename of directories in ISO is working again
BUGFIX: TestSimple repaired
CHANGE: Continue in case of an error in TestAdvanced Mode
CHANGE: after testing in TestSimple mode, rename to OK_SIMPLE or ERR_SIMPLE
CHANGE: less output in console window for test-modes in DRIVE mode (is now identical to ISO mode)
20170228 .. 0.53
BUGFIX: Updated UDF module
CHANGE: Progress Display in Title
20170302 .. 0.54
CHANGE: also support bluray file copies in folders
20180130 .. 0.61
BUGFIX: removed additional empty block (2KB) at the end of an iso2iso decryption
BUGFIX: AlwaysAskDest now also works in 'drive' mode
FEATURE: alternative aacs keydb file can be specified in ini file
FEATURE: Support Undo Files created during BD+ repair (to reverse the repair in case the BD+-FUT file is faulty)
FEATURE: massive speedboost due to internal changes and switch to libgcrypt aes library
CHANGE: small udf support enhancement
FEATURE: new undo-module
FEATURE: iso files now also support to skip AACS decryption and carry on with BD+ and PlaylistObfuscation detection
FEATURE: iso mount now supported with native windows-iso support in Windows8 and later
BUGFIX: Leawo BD+ table are correctly converted now
BUGFIX: PlOb correction should work now (untested)
BUGFIX: error in case an unencrypted file is reached in mode 4 - DecryptISO2ISO
BUGFIX: open ISO file in write mode to allow correction in mode 9 (correct playlist obfuscation)
BUGFIX: removed automatic switch to inplace decryption for ISO2ISO in case destination file already exists
BUGFIX: calculation of progress for iso files corrected
FEATURE: request acknowledge from user for InPlace decryption
BUGFIX: do not ask for destination directory in case InPlace decryption is requested
20180319 .. BTAD 0.62
BUGFIX: udf implementation ignored 'ImplementationUse' -> failed to parse disc 'RED_BIRD_2D_F2'
FEATURE: mode 'Dump and Test' to rip discs from drive and test the resulting ISO file
20180321 .. BTAD 0.63
BUGFIX: udf implementation ignored 'ImplementationUse' (also fixed in 2nd location _UDF_readwriteFileIdentifierDescriptor )
20180324 .. BTAD 0.64
BUGFIX: udf implementation ignored 'ImplementationUse' (also fixed in 3rd location BRUDF_File_Rename )
20181015 .. BTAD 0.70
CHANGE: new keydb-module
BUGFIX: udf implementation
CHANGE: required changes for changed aacs module
FEATURE: simple test for DVD VOB files
FEATURE: test of DVD-ISO files (only if DVD filesystem is valid - if files in directory \VIDEO_TS are identical in ISO9660 and UDF filesystem and also check if .IFO and .BUP files have identical size)
BUGFIX: udf implementation (do not write error in case an entry does not have allocation extents)
BUGFIX: correctly determine old scan result in case it has been 'ERR_Simple' (do not rename again .. )
20191212 .. BTAD 0.77
FEATURE: added test-filesystem mode for bluray isos (to check if there's an ISO9660 filesystem available)
FIX: memory leak in drive_ms
FIX: correctly calculate UnitKeys when decrypting UDF ISO files
FIX: alloc mem error corrected when dumping drive to iso
FIX: crash after dump/before validation
FIX: error renaming AACS to BTD! after iso2iso decoding
FEATURE: add progress to title when dumping drive
20200420 .. Download BTAD 0.79 (fvonline-db.bplaced.net/bluraytest/BlurayTestAndDecrypt_0.79.zip)
FIX: invalid memory access when trying to decode BD+ protected discs
FIX: open keydb-file in shared readonly mode
20210810 .. Download BTAD 0.80 (fvonline-db.bplaced.net/bluraytest/BlurayTestAndDecrypt_0.80.zip)
FIX: failed to properly parse multiple unit keys separated by | without spaces (therefore the test and decryption failed in case the first unit key is not the correct one)
20210810 .. Download BTAD 0.81 (fvonline-db.bplaced.net/bluraytest/BlurayTestAndDecrypt_0.81.zip)
FIX: replace special characters before creating files
20230425 .. Download BTAD 0.94 (fvonline-db.bplaced.net/bluraytest/BlurayTestAndDecrypt_0.94.zip)
FEATURE: added benchmark mode
FIX: mode from ini file not always correctly detected as supported when askmode=0
FEATURE: use RDK for BusDecryption
CHANGE: in case there's not enough free space available, also show the available amount
CHANGE: normalize all "drive" parameters to x:\ (e.g. "x" or "x:")
CHANGE: store and restore window position on exit/start
CHANGE: adjust used colours
CHANGE: show progress in titlebar during simple or advanced test
CHANGE: create BD+ FUT tables with 'mediakey' in name
FEATURE: if XREVEAL is installed also create the BD+ FUT table in it's directory (in case it's different from the default directory)
CHANGE: add option for auto-update
candela
13th September 2016, 21:11
It is somewhat confusing that you need to delete the ini to select a different mode. You could print this info in the window maybe. Also first I thought you could drag files into the window, but you need to close and drag onto the exe. Btw, check PM
nalor
13th September 2016, 21:19
Hi - I know the version available here has a few bugs that I noticed while testing my own images... so it's still not perfect.
At the moment I'm trying to parse the ISO files with UDF filesystem directly to create 1:1 copies of isos with only AACS getting removed.
The easiest way to choose between different modes without deleting the ini files every time is by creating multiple copies of the exe with different filenames - usually the name of the ini follows the name of the exe, so although it might not be the best solution it should do the trick.
candela
15th September 2016, 21:28
Btw, have you tried comparing decrypted files from your tool with DVDFab decrypted ones? I sometimes get many differences compared to DVDFab (which are not BD+ related 5-bytes errors). Your images seem to be the same as DumpHD though
dizzier
15th September 2016, 21:45
Btw, have you tried comparing decrypted files from your tool with DVDFab decrypted ones? I sometimes get many differences compared to DVDFab (which are not BD+ related 5-bytes errors). Your images seem to be the same as DumpHD though
Note that there is a copy protection indicator in each aligned unit (each 6144 bytes of m2ts file). It states if the unit is encrypted or not. Some software clears it after decryption (libaacs does), some not (I believe MakeMKV does not, but it was a long time since I've last checked). Search http://git.videolan.org/?p=libaacs.git;a=blob;f=src/libaacs/aacs.c for 0xc0 to see what I mean. Those obviously will generate a lot of differences in decrypted files.
nalor
15th September 2016, 21:46
Btw, have you tried comparing decrypted files from your tool with DVDFab decrypted ones? I sometimes get many differences compared to DVDFab (which are not BD+ related 5-bytes errors). Your images seem to be the same as DumpHD though
Hi! No, never tried. Basically all I'm doing is the AES decryption (and as I can detect all mpeg headers in the result I don't think that there's something that could go wrong without being noticed) and I'll remove the 'aacs encrypted' flag.
So honestly there's not much that can go wrong...
(but I've already noticed in the past that dvdfab isn't really verifying if the created files are really correct. e.g. in case the source cannot be read properly it simply writes wrongly decrypted blocks into the destination file... )
candela
15th September 2016, 21:54
Note that there is a copy protection indicator in each aligned unit (each 6144 bytes of m2ts file). It states if the unit is encrypted or not. Some software clears it after decryption (libaacs does), some not (I believe MakeMKV does not, but it was a long time since I've last checked). Search http://git.videolan.org/?p=libaacs.git;a=blob;f=src/libaacs/aacs.c for 0xc0 to see what I mean. Those obviously will generate a lot of differences in decrypted files.
This would result in 1 byte errors spaced 6144 bytes or 192 bytes apart no? this is not the case
I used TSPE - Transport Stream Packet Editor / Analyser (http://www.bitstreamtools.com/Theory/Timecodes/index.php) (anyone have the old freeware version of this tool?) to scan the rips of a BD+ disc and VLC to play them:
- BlurayTest&Decrypt (remove AACS): TSPE = OK, VLC = corruption since BD+ is not removed
- DumpHD (remove AACS & BD+): TSPE = PMT continuity & CRC errors, VLC = OK
- DVDFab (remove AACS & BD+): TSPE = OK, VLC = OK
So I'm thinking it's either:
- DumpHD contains bugs writing the M2TS
- applying BD+ patches fixes errors on video PES level but introduces errors on M2TS packet level which must be fixed. After demuxing, the elementary video and audio streams are identical between DumpHD and DVDFab so it seems DVDFab is doing this
- BD+v3 conversion table produced by DumpHD and DVDFab ;) contains errors and patches wrong things
Update: tested some other discs and they all have errors according to TSPE so can't draw any real conclusions. DVFab seems to alter the streams for an unknown reason after decrypting, which is quite annoying
candela
3rd October 2016, 11:13
There are some problems with relative paths on command line
1) works:
- BlurayTestAndDecrypt.exe F:\BDMV\STREAM\00001.m2ts
2) doesn't work:
- cd F:\BDMV\STREAM
- C:
- BlurayTestAndDecrypt.exe F:00001.m2ts
3) doesn't work:
- F:
- cd F:\BDMV\STREAM
- BlurayTestAndDecrypt.exe 00001.m2ts
(scenarios from memory, may not be 100% accurate :))
nalor
30th October 2016, 01:16
There are some problems with relative paths on command line
1) works:
- BlurayTestAndDecrypt.exe F:\BDMV\STREAM\00001.m2ts
2) doesn't work:
- cd F:\BDMV\STREAM
- C:
- BlurayTestAndDecrypt.exe F:00001.m2ts
3) doesn't work:
- F:
- cd F:\BDMV\STREAM
- BlurayTestAndDecrypt.exe 00001.m2ts
(scenarios from memory, may not be 100% accurate :))
Honestly never tried it that way.. basically only 'absolute' paths are supported - tried to check for invalid path arguments in 0.41.
nalor
30th October 2016, 01:20
Just released BTD 0.41
2 major new features:
# integrated UDF support - this allows to directly read from iso files without the need for a virtual drive in between and also direct ISO2ISO decrypting
# BD+ repair support - with the help of fixup tables that can be downloaded with Pavtube BdMagic it's possible to repair the BD+ damages (you're not limited to Pavtube - but for me it's the most convenient way...)
Hopefully it's working well :)
candela
10th November 2016, 01:32
I found several errors while attempting to decrypt single files:
1)
DecryptDestination = D:\BDMV\
01:19:25 - Detected File >F:\BDMV\STREAM\00801.m2ts<
01:19:31 - Decrypt OutputDir: D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\
01:21:57 - MODULE.BDPLUS [E] ERROR! Sourcefile invalid >D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\00801.m2ts<
=> error because file is actually saved as
D:\BDMV\00801.m2ts
2)
DecryptDestination = D:\BDMV
2016-11-10 00:35:32 # 12678897 # MODULE.BDPLUS [E] ERROR! Sourcefile invalid >D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\00801.m2ts<
=> error because file is actually saved as
D:\BDMV00801.m2ts (file & dir combined)
3) update: actually it also happens if I try to decrypt F:, it saves the files in a wrong dir
nalor
10th November 2016, 20:08
Already on it...
nalor
10th November 2016, 21:39
I found several errors while attempting to decrypt single files:
1)
DecryptDestination = D:\BDMV\
01:19:25 - Detected File >F:\BDMV\STREAM\00801.m2ts<
01:19:31 - Decrypt OutputDir: D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\
01:21:57 - MODULE.BDPLUS [E] ERROR! Sourcefile invalid >D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\00801.m2ts<
=> error because file is actually saved as
D:\BDMV\00801.m2ts
2)
DecryptDestination = D:\BDMV
2016-11-10 00:35:32 # 12678897 # MODULE.BDPLUS [E] ERROR! Sourcefile invalid >D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\00801.m2ts<
=> error because file is actually saved as
D:\BDMV00801.m2ts (file & dir combined)
3) update: actually it also happens if I try to decrypt F:, it saves the files in a wrong dir
Please try the new 0.42 - hopefully it fixes the problems, if not come back to me - thanks :)
candela
11th November 2016, 13:38
Now it works if I drag a single file but when I drag the drive F: it gives
13:34:13 - Decrypt OutputDir: D:\BDMV\C981D0350CD9AD659EC4832E59D94B56963F0229_THE_BOOK_OF_LIFE\
13:34:13 - #### TEST ###################################################################
13:34:13 - #############################################################################
13:34:13 - On Drive >f:< - 1/116 - File >f:\BDMV\STREAM\00009.m2ts< Mode >Decrypt - StopOnError<
13:34:13 - ERROR! Couldn't create destination file!
13:34:13 - Duration >0:00:00<
13:34:13 - #############################################################################
13:34:13 - On Drive >f:< - 2/116 - File >f:\BDMV\STREAM\00010.m2ts< Mode >Decrypt - StopOnError<
13:34:13 - ERROR! Couldn't create destination file!
nalor
11th November 2016, 22:50
Now it works if I drag a single file but when I drag the drive F: it gives
Fixed - someday I should start to test releases before I publish them...
candela
12th November 2016, 12:30
At first glance, 0.43 seems to be working now. After many years we again have a free tool for ripping and BD+ repair, hurrah :thanks:
spotter
17th November 2016, 17:12
Ah, this is a tool I've been looking for, but there's one feature that would be awesome.
Imagine I have a bluray that is damaged (scratched), I can ddrescue as much of it as I can (i.e. copies it sector by sector and keeps a map of what it couldn't read), I can then ddrescue a different disc (even if also damaged) to fill in the missing sectors. I can generate an encrypted iso this way.
Now, since I have the disk, your tool should be able to generate the appropriate decryption keys via the drive but use them to decrypt the complete iso. Would help for discs whose VUK isn't in the keydb.
spotter
17th November 2016, 18:00
also any chance you would want to make this a project on github? Ex: I'd like to get it working within linux.
nalor
17th November 2016, 18:49
Ah, this is a tool I've been looking for, but there's one feature that would be awesome.
Imagine I have a bluray that is damaged (scratched), I can ddrescue as much of it as I can (i.e. copies it sector by sector and keeps a map of what it couldn't read), I can then ddrescue a different disc (even if also damaged) to fill in the missing sectors. I can generate an encrypted iso this way.
Now, since I have the disk, your tool should be able to generate the appropriate decryption keys via the drive but use them to decrypt the complete iso. Would help for discs whose VUK isn't in the keydb.
Thanks for your post - but unfortunately BTAD cannot retrieve decryption keys for anything... all it does (test or decrypt a disc or files) is only possible in case the VUK is already known.
And to get the VUK you can already use FindVUK - although it's limited to Windows because it relies on the tools from DVDfab it's also possible to get the VUK for scratched discs and iso files on harddrive.
So finally I think you can get the VUK with FindVUK and afterwards decrypt your rescued iso with BTAD.
spotter
17th November 2016, 18:53
ok, that makes sense, source to this tool would be nice, unless you have some other goal in mind for it which precludes that.
nalor
17th November 2016, 19:05
also any chance you would want to make this a project on github? Ex: I'd like to get it working within linux.
I'll publish the source on github after adding the last 1 or 2 features I'd like to implement.
It's written in Purebasic - and this language also supports linux (but I've never tried to compile something for linux... so I don't know how easy it will be).
spotter
17th November 2016, 20:30
I've never used pure basic, but i can help with getting it compiled on linux. I'm assuming you are are using the standard libraries libaacs libbdplus libraries from purebasic?
nalor
17th November 2016, 21:52
I've never used pure basic, but i can help with getting it compiled on linux. I'm assuming you are are using the standard libraries libaacs libbdplus libraries from purebasic?
Reimplemented the necessary parts directly in purebasic ;)
So nothing external necessary to take into account.
spotter
29th November 2016, 06:26
weird Q, do you know how to handle bus encryption? In that case my ddrescue method would probably need to be implemented in place of whatever tool is doing the "bus decryption" unless its possible to authenticate to the drive and then reads just work as expected? (don't know enough about bus encryption obviously)
dizzier
30th November 2016, 12:44
Bus encryption is handled by libaacs if you have a working host certificate (which we have). Pretty nice description is available on libaacs git: http://git.videolan.org/?p=libaacs.git;a=commit;h=583df16fa867ccda948a6c760ee8912684fb7b9d
Most discs do not implement bus encryption anyway, so it probably is not really a big problem.
spotter
30th November 2016, 17:53
ok, what that means to me is that my ddrescue type method to recover damaged disks will not work with a bus encrypted disc.
I was hoping it was more along the lines if you cryptographically authenticate to the player/drive/disc than any read will be unencrypted otherwise the drive will encrypt/mangle it, but guess that's not the case and that it's actually a generation of a "dynamic" key that is used to encrypt (in drive) and decrypt (in player) the data.
my current ddrescue methodology is essentially
ddresccue -> iso (repeat until one gets it 100% might require multiple media copies, but all can be damaged)
BlurayTestAndDecrypt -> decrypted iso
(and I'm trying to see how dvdfab/anydvd act on a encrypted and decrypted iso, would they decrypt an iso, would they remove the "structural" (i.e. non crypto) protections from a decrypted iso)
I guess its good that not many discs use it then.
hubblec4
10th December 2016, 14:18
I want to test your tool, but after download I get a warning from Waterfox that this file is a Virus or Malware.
candela
29th December 2016, 23:49
1) There appears to be a problem with non-encrypted m2ts file in mode 3/4 (mode 2 works fine)
Mode3
2016-12-29 23:32:24 # 1000472648 # On Drive >F:\< - 1/46 - File >F:\BDMV\STREAM\00002.m2ts< Mode >Decrypt - StopOnError<
2016-12-29 23:32:24 # 1000472657 # Bluray_TestDecryptFile - SrcFile >F:\BDMV\STREAM\00002.m2ts< DstFile >D:\BDMV\EE59C14A4AD80A352295D2CDC7CF349F90E34250_ROPE_G51\00002.m2ts<
2016-12-29 23:32:24 # 1000472723 # Filename >F:\BDMV\STREAM\00002.m2ts< Size GB > 0.00< Unit_Enc > 0< Unit_Unenc > 9< Unit_Err > 0< Duration >0:00:00< DECS
2016-12-29 23:32:24 # 1000472734 # Something went terribly wrong - filesize different!!! Src >55296<Dst >-1<
Mode2
2016-12-29 23:45:40 # 1001268631 # 1/1 - Srcfile >F:\BDMV\STREAM\00002.m2ts< Mode >Test - AdvancedTest<
2016-12-29 23:45:40 # 1001268639 # Bluray_TestDecryptFile - SrcFile >F:\BDMV\STREAM\00002.m2ts< DstFile >D:\BDMV\00002.m2ts<
2016-12-29 23:45:40 # 1001268699 # Filename >F:\BDMV\STREAM\00002.m2ts< Size GB > 0.00< Unit_Enc > 0< Unit_Unenc > 9< Unit_Err > 0< Duration >0:00:00< TSTA
2016-12-29 23:45:40 # 1001268714 # Duration >0:00:00<
2016-12-29 23:45:40 # 1001268726 # Overall duration >0:00:00<
2) changing the DebugLog value in the ini doesn't appear to affect the log files, I always get the same information
3) Can you built in support for KEYDB.cfg entries with other keys than VUK:
- 1 or more UnitKey
- MK + VID
nalor
30th December 2016, 23:55
ok, what that means to me is that my ddrescue type method to recover damaged disks will not work with a bus encrypted disc.
Best option: use a drive that is not bus-encryption-capable :D
This way there's no need to worry if a disc is bus-encryption-enabled or not.
nalor
31st December 2016, 00:02
I want to test your tool, but after download I get a warning from Waterfox that this file is a Virus or Malware.
I know - this topic is a neverending story... I'm using purebasic to write my tools and there's something in the exe files that is suspicous to a few anti-virus/malware tools (take a look at the findvuk thread, I've tried to find a way to circumvent the problem but finally gave up because it's simply not possible without changing the dev-language or something like this.).
I'll promise that I've never and will never integrate harmful procedures into my tools - but finally it's up to you if you want to trust me or not.
nalor
31st December 2016, 00:11
1) There appears to be a problem with non-encrypted m2ts file in mode 3/4 (mode 2 works fine)
Need to check - I know I've fixed a few bugs since my last release, but unfortunately also started to 'modularize' parts of the code and haven't finished yet.
2) changing the DebugLog value in the ini doesn't appear to affect the log files, I always get the same information
Debug log is only available in very few areas of the code - my current refactoring will introduce different loglevels that are available in all areas - so once I'm finished it should be easier to get more logoutput ;)
3) Can you built in support for KEYDB.cfg entries with other keys than VUK:
- 1 or more UnitKey
- MK + VID
Should be possible - but need to finish the other work before I'll start to implement this one.
nalor
5th January 2017, 22:51
Released a new build - it fixes the problem reported by candela and also introduces the ability to decrypt files with mediakey+volumeid or unitkeys from keydb.cfg file.
But I have to admit that I haven't tested this feature... so please keep me posted if it's working as expected :D
I've changed the logging procedure and splitted the source into lot's of smaller modules and it's possible to set the loglevel for each module as you want.
There's a new entry in the ini file called 'LogLevel' and usually only a 'Default' entry is present and set to level 2='INFO'
Logentries look like:
2017-01-05 22:28:20 # 13865088 # [I] bluray_udf / _UDF_Parse_FileSystem /
format is:
date+time - milliseconds - loglevel - module - procedure - logentry
so in case you want for example less logoutput for the 'bluray_udf' module, simply add a line 'bluray_udf=1' into the loglevel ini section and now only errors and warnings are logged.
I made a few simply tests and I think it should work :)
In case of errors just come back to me and I'll try to fix them.
candela
6th January 2017, 01:32
Some basic test shows the unencrypted m2ts bug is fixed and it works with only a unitkey.
Btw, if a unitkey is missing (eg multiple unitkeys required but only 1 known) you get an error but the file isn't copied. Perhaps there should be an option to copy the file encrypted. Then the encryption can still be removed later if a "better" key is found
spotter
8th January 2017, 08:38
Best option: use a drive that is not bus-encryption-capable :D
This way there's no need to worry if a disc is bus-encryption-enabled or not.
true, and it turns out the drive in my linux box where I make the ddrescue copies doesn't have bus encryption, but if this drive dies, then will be hard to replace.
nalor
8th January 2017, 11:12
true, and it turns out the drive in my linux box where I make the ddrescue copies doesn't have bus encryption, but if this drive dies, then will be hard to replace.
This is the reason why I started this thread here: List of bluray-drives with their features (e.g. BusEncryptionCapable) (http://forum.doom9.org/showthread.php?t=172914)
This way it's easier to get a replacement drive :)
spotter
8th January 2017, 21:56
I understand, just that the vast majority (if not all?) of the ones without bus encryption aren't readily available.
nalor
8th January 2017, 22:23
When I check my local online flee market I find a lot of available drives without bus encryption.
You cannot buy them new, but it's easy to find used drives.
Gesendet von meinem E5823 mit Tapatalk
hubblec4
13th January 2017, 21:53
I know - this topic is a neverending story... I'm using purebasic to write my tools and there's something in the exe files that is suspicous to a few anti-virus/malware tools (take a look at the findvuk thread, I've tried to find a way to circumvent the problem but finally gave up because it's simply not possible without changing the dev-language or something like this.).
I'll promise that I've never and will never integrate harmful procedures into my tools - but finally it's up to you if you want to trust me or not.
Thanks for this info.
I was wondering because I have no AntiVirus software installed.
And I have never seen before a virus warning directly from Waterfox.
nalor
21st January 2017, 00:13
Released a new version - the only relevant change is a new mode to list the correct unit key for all files.
nalor
3rd February 2017, 22:22
Release 0.51 - includes 2 bug fixes that can be relevant in case you're using either testmode-simple or testmode-advanced
Hironimo
27th February 2017, 19:15
Hey there, Nalor.
I just recently noticed your tool that was partially inspired by me (blush), I only accidentally found it.
I tried it out after another tool to decrypt the disk produced a main file that was garbled with decoding errors.
It seems now that I tried to decode with your tool that it is a BD+ disc, and that is probably the cause.
I noticed an issue when handling a disc with BD+ protection (using Pavtube BDMagic):
18:15:25 - Check if disc is BD+ protected
18:15:25 - Disc is BD+ protected!
18:15:25 - BD+ details - Date 2016.04.15 Gen 254
18:15:25 - Matching BDPLUS table file found >C:\Users\<username redacted>\.bdkeys\257B5EEC855AB389582B5C934D0C9D06\table< - Format: Pavtube
18:15:25 - ERROR! bluray_bdpfixuptable-BRFUT_ConvertPavtube2Convtab - ERROR! Cannot create directory >C:\Users\<username redacted>\AppData\Roaming\bdplus\convtab\<
18:15:25 - WARN! Converting of PAVTUBE to CONVTAB failed - carry on with pavtube file. Error >#FUT_ERR_DIR_CREATE (-807)
18:15:25 - ERROR! Couldn't get a matching fixup table - error >#FUT_ERR_DIR_CREATE (-807)
I did this with a console with administrative privileges, just to be sure.
After I created the directory in question myself, the process created the file in the directory and proceeded with execution.
I noticed some inconveniences of your tool:
When trying mode 3 or 4 it does not seem to be possible to provide an m2ts file, or even a drive letter that contains the necessary data but is not a BD drive, for that matter.
Mode 2 seems to work however. I don't understand what the difference between mode 2 and mode 4 is, though, as mode 2 scans and apparently decrypts the file too,
and that works, and 3 and 4 do not. Or did I understand something wrong?
It will either complain
18:52:56 - >> Mode >2<
18:52:56 - >> DecryptDest >C:\Temp\<
18:52:56 - List of files being processed:
18:52:56 - Detected File >C:\Temp\Deadpool_encrypted\BDMV\STREAM\02577.m2ts<
18:52:56 - VolumeName: Main Win10
18:52:56 - Disc is not AACS protected (there's no AACS folder on the disc)
18:52:56 - INFO! no AACS folder on disc, so there's no decryption possible/necessary!
I'd like that it is possible to work on a BD content that I copied over to a directory on harddrive/SSD, and not available as disc directly or as ISO.
Btw, what is the tool of your choice to read the original BD into an ISO? I'd like a simple one that does the job but without being completely embedded in some GUI.
On another note, I got interested about he background workings of BD.
Can you explain what you know about blu-rays that are BD+ encrypted? How does it work?
Does that mean that basically any BD+ discs are not supported fully when you just have the VUK?
Also, is there good documentation that documents how Blu-ray Encryption and thus Encryption works,
preferably for someone who knows how to code, possibly interested to decrypt, but not going into
extreme detail.
I'm currently running a decryption run on one of my discs.
Btw, the disc in question apparently only has BD+ protection on the main m2ts file, the others worked fine just with plain BD decryption.
Is that common?
Hope that works out well, I'll possibly update if I run into more issues.
Hironimo
27th February 2017, 19:54
Update:
I ran through the disc in mode 4 (and later mode 5, see below), providing the drive letter of the drive.
The log seems fine (just the section of the main file, plus the one before and after):
2017-02-27 18:19:30 # 22835412 # [I] main / legacy / Duration >0:00:01<
2017-02-27 18:19:30 # 22835413 # [I] main / legacy / #############################################################################
2017-02-27 18:19:30 # 22835414 # [I] main / legacy / On Drive >G< - 97/156 - File >G:\BDMV\STREAM\01741.m2ts< Mode >Decrypt - ContinueOnError<
2017-02-27 18:19:30 # 22835414 # [I] main / legacy / Bluray_TestDecryptFile - SrcFile >G:\BDMV\STREAM\01741.m2ts< DstFile >C:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool\01741.m2ts<
2017-02-27 18:20:16 # 22881511 # [I] main / legacy / Filename >G:\BDMV\STREAM\01741.m2ts< Size GB > 0.28< Unit_Enc > 49397< Unit_Unenc > 0< Unit_Err > 0< Duration >0:00:46< DECC
2017-02-27 18:20:16 # 22881533 # [I] main / legacy / Duration >0:00:46<
2017-02-27 18:20:16 # 22881534 # [I] main / legacy / #############################################################################
2017-02-27 18:20:16 # 22881535 # [I] main / legacy / On Drive >G< - 98/156 - File >G:\BDMV\STREAM\02577.m2ts< Mode >Decrypt - ContinueOnError<
2017-02-27 18:20:16 # 22881535 # [I] main / legacy / Bluray_TestDecryptFile - SrcFile >G:\BDMV\STREAM\02577.m2ts< DstFile >C:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool\02577.m2ts<
2017-02-27 19:42:14 # 27799621 # [I] main / legacy / Filename >G:\BDMV\STREAM\02577.m2ts< Size GB > 27.11< Unit_Enc > 4737773< Unit_Unenc > 0< Unit_Err > 0< Duration >1:21:58< DECC
2017-02-27 19:42:14 # 27799642 # [I] main / legacy / Duration >1:21:58<
2017-02-27 19:42:14 # 27799642 # [I] main / legacy / #############################################################################
2017-02-27 19:42:14 # 27799643 # [I] main / legacy / On Drive >G< - 99/156 - File >G:\BDMV\STREAM\02616.m2ts< Mode >Decrypt - ContinueOnError<
2017-02-27 19:42:14 # 27799643 # [I] main / legacy / Bluray_TestDecryptFile - SrcFile >G:\BDMV\STREAM\02616.m2ts< DstFile >C:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool\02616.m2ts<
2017-02-27 19:42:34 # 27819353 # [I] main / legacy / Filename >G:\BDMV\STREAM\02616.m2ts< Size GB > 0.12< Unit_Enc > 21820< Unit_Unenc > 0< Unit_Err > 0< Duration >0:00:19< DECC
2017-02-27 19:42:34 # 27819363 # [I] main / legacy / Duration >0:00:19<
2017-02-27 19:42:34 # 27819363 # [I] main / legacy / #############################################################################
However the generated file, while playable, still has the issues that video is garbled (you can see it is deadpool, but cannot enjoy it) the same way it was with the tool I previously used (Blu-ray Disc Ripper 1.5).
Maybe BD+ repair is only applied in mode 5?
If so, i think it would make sense to repair it - if possible - in any mode that produces decrypted output, unless specified in the ini BD+ repair is not wanted.
Since I thought I give mode 5 a try I created an ISO file of the disk and let it run with mode 5.
I might note that there were 37 sectors that it could not read properly, but I think that should not account for the below issues.
It ran through without real errors, except at the end when it was finished but waiting to finish.
This is the last part of the log (the whole is much too long to post):
2017-02-27 22:59:45 # 39650624 # [D] bluray_aacs / BRAACS_AutoDetectUnitKey / readable unit found
2017-02-27 22:59:45 # 39650624 # [D] bluray_aacs / BRAACS_AutoDetectUnitKey / Select UnitKey >1<
2017-02-27 22:59:45 # 39650624 # [D] bluray_aacs / BRAACS_AutoDetectUnitKey / Correct UnitKey found! >1<
2017-02-27 22:59:45 # 39650626 # [I] bluray_udf / UDF_ReadLogicalBlock / ###################### BLOCK 24356992 # 0x0000000B9D440000 LEN 216 ######################
2017-02-27 22:59:45 # 39650634 # [I] bluray_udf / UDF_WriteLogicalBlock / ++++++++++++++++++++++ WRITE-BLOCK 24356992 LEN 216++++++++++++++++++++++
2017-02-27 22:59:45 # 39650634 # [I] main / legacy / ++ COPY ++ Pct >100.00< StartBlock >24357208< BlockLen >00001000<
2017-02-27 22:59:45 # 39650640 # [I] bluray_udf / UDF_ReadLogicalBlock / ###################### BLOCK 24357208 # 0x0000000B9D4AC000 LEN 1000 ######################
2017-02-27 22:59:45 # 39650641 # [I] bluray_udf / UDF_WriteLogicalBlock / ++++++++++++++++++++++ WRITE-BLOCK 24357208 LEN 1000++++++++++++++++++++++
2017-02-27 22:59:45 # 39650642 # [I] main / legacy / ++ COPY ++ Pct >100.00< StartBlock >24358208< BlockLen >00000075<
2017-02-27 22:59:45 # 39650642 # [I] bluray_udf / UDF_ReadLogicalBlock / ###################### BLOCK 24358208 # 0x0000000B9D6A0000 LEN 75 ######################
2017-02-27 22:59:45 # 39650642 # [I] bluray_udf / UDF_WriteLogicalBlock / ++++++++++++++++++++++ WRITE-BLOCK 24358208 LEN 75++++++++++++++++++++++
2017-02-27 22:59:45 # 39650642 # [I] bluray_udf / UDF_CloseIso /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ BRUDF_CloseIso ++++ File >c:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool.iso< ++++
++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650645 # [I] main / legacy / All blocks copied into >C:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool_decrypted.iso< - rename AACS folder to BTD! now
2017-02-27 22:59:45 # 39650645 # [I] bluray_udf / UDF_File_Rename /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ BRUDF_File_Rename ++++ Filename >\AACS< NewFilename >BTD!<++++
++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650645 # [I] bluray_udf / _UDF_readFileIdentifierDescriptor /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ _UDF_readFileIdentifierDescriptor ++++ Filename >\AACS< iAllowFidType >0< ++++\n++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650645 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ _UDF_readwriteFileIdentifierDescriptor ++++ Filename >\AACS< *FidToWrite >0< AllowFidType >0< ++++\n++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650645 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / File >\AACS< Size >0< FID/Part >1< FID\Block >2< FID\Offset >84< FID\Length >224<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / UDF_ReadLogicalBlock / ###################### BLOCK 322 # 0x00000000000A1000 LEN 0.109375 ######################
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / ++++ File Identifier Descriptor ++++
2017-02-27 22:59:45 # 39650647 # [D] bluray_udf / _UDF_readwriteFileIdentifierDescriptor /
>>> ICB Location >1129< PartRefNr >1< Length >2048<
LengthOfFileIdentifier >5<
LengthOfImplementationUse >0<
FileVersionNumber >1<
FileCharacteristics >2<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / FileIdentifier >AACS<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / Correct file found - read mode
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / UDF_File_Rename / FileIdentifier changed in memory to >BTD!<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_writeFileIdentifierDescriptor /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ _UDF_writeFileIdentifierDescriptor ++++ Filename >\AACS< *FidToWrite >11370064< iAllowFidType >0< ++++\n++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor /
++++++++++++++++++++++++++++++++++++++++++++++++++
++++ _UDF_readwriteFileIdentifierDescriptor ++++ Filename >\AACS< *FidToWrite >11370064< AllowFidType >0< ++++\n++++++++++++++++++++++++++++++++++++++++++++++++++
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / File >\AACS< Size >0< FID/Part >1< FID\Block >2< FID\Offset >84< FID\Length >224<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / UDF_ReadLogicalBlock / ###################### BLOCK 322 # 0x00000000000A1000 LEN 0.109375 ######################
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / ++++ File Identifier Descriptor ++++
2017-02-27 22:59:45 # 39650647 # [D] bluray_udf / _UDF_readwriteFileIdentifierDescriptor /
>>> ICB Location >1129< PartRefNr >1< Length >2048<
LengthOfFileIdentifier >5<
LengthOfImplementationUse >0<
FileVersionNumber >1<
FileCharacteristics >2<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / FileIdentifier >AACS<
2017-02-27 22:59:45 # 39650647 # [I] bluray_udf / _UDF_readwriteFileIdentifierDescriptor / Correct file found - write mode
2017-02-27 23:00:49 # 39714764 # [I] main / legacy / A program error was detected:
Error Message: Invalid memory access
Error Code: -1073741819
Code Address: 1957864770
Target Address: 11370496
Sourcecode line: 1170
Sourcecode file: U:\PUREBASIC\~MODULE\mod.bluray_udf.pbi
It says there on the command line:
22:59:45 - All blocks copied into >C:\Temp\7C6BA7769B9FFCB4583F703B14C5072D85BD9E94_Deadpool_decrypted.iso< - rename AACS folder to BTD! now
However I have no idea what to actually do (can't rename a folder on a read-only disk, and I thought I can't access/change anything on an ISO file.
So I just hit return (or was it escape?) and the program ended and I got the error in the log.
The iso file is mountable and the result of the m2ts files is the same: looked at others by random beside the main one and it seemed fine, but the main file is garbled (lots of h264 decode errors).
Can you help?
nalor
28th February 2017, 09:47
Hi! I already fixed the InvalidMemoryAccess error a while ago - but haven't posted a new release in the meantime.. will post my current release this evening when I'm back home again.
I'll change the code to support also support simple file-copies of discs in subdirectories - I already though about this in the past, but as nobody ever complained about it and I don't need it I never changed the code to support it ;)
Regarding BD+:
I watched IndependenceDay2 on saturday and first I got the BD+ repair file from Leawo BlurayPlayer but the result after the repair hasn't been correct... same distortions as before the repair.
Next I got the repair file from Pavtube and this one worked correctly and when I compared both files I noticed they're completely different.
The Problem with repairing BD+ errors is that I don't know a way to check if the file is 'really' repaired or even more destroyed.... the repair files simply contain file offsets with data that needs to be written at this offsets... so the result needs to be checked manually ... (but usually you only need to check a few seconds of the movie...)
VUK is not enough to remove BD+, they're completely unrelated.
nalor
28th February 2017, 09:53
And I use a simple tool called Iso Recorder to create ISO files from blurays:
ISO Recorder (http://isorecorder.alexfeinman.com/isorecorder.htm)
But I use the GUI of the tool...
nalor
28th February 2017, 21:23
Released 0.53 - it fixes the IMA error when decrypting an iso and adds a progress information in the title
Hironimo
1st March 2017, 00:05
Hi.
I tried again, this time with the latest version 0.53 and by getting the table from Leawo BlurayPlayer.
The .bin files are different, and the result with that one is a bit better, but there are still artefacts.
However Leawo BlurayPlayer plays the video correctly without artefacts, which leads me to believe that the table it uses is correct.
I tried to convert the video within Pavtube but that fails (says finished within seconds and the file is just a few kb, or with other options there is an error), so my impression on that tool is not good.
Could it be that you somehow use the data from the memory dump incorrectly?
candela
1st March 2017, 00:30
Hi.
I tried again, this time with the latest version 0.53 and by getting the table from Leawo BlurayPlayer.
The .bin files are different, and the result with that one is a bit better, but there are still artefacts.
However Leawo BlurayPlayer plays the video correctly without artefacts, which leads me to believe that the table it uses is correct.
I tried to convert the video within Pavtube but that fails (says finished within seconds and the file is just a few kb, or with other options there is an error), so my impression on that tool is not good.
Could it be that you somehow use the data from the memory dump incorrectly?
Rip only the m2ts file so you can easily check with a hex editor if BlurayTestAndDecrypt is patching the correct addresses and data in the BD+ table. Open the BD+ table in ConvTableView to see the addresses and patch data
Btw, the Pavtube table for your Deadpool release matches the table for a different Deadpool release which uses the same title keys. So it seems unlikely the table is bad (although possible). Can you maybe post the leawo table on tinyupload?
Hironimo
1st March 2017, 16:02
Rip only the m2ts file so you can easily check with a hex editor if BlurayTestAndDecrypt is patching the correct addresses and data in the BD+ table. Open the BD+ table in ConvTableView to see the addresses and patch data
Btw, the Pavtube table for your Deadpool release matches the table for a different Deadpool release which uses the same title keys. So it seems unlikely the table is bad (although possible). Can you maybe post the leawo table on tinyupload?
Thanx for the comment. I took a look (the original link to ConvTableView did not work, but i managed to find it elsewhere).
I did not get to analyze the resulting file however, since in the end it worked:
I found out that apparently mode 4 does not apply the BD+ correction table, but mode 5 does (even though I was sure I tried mode 5 before, and it did not work the first time... oh well).
Anyway, I uploaded the data for you to take a look anyway.
I find it strange that the data from the Leawo player appears to be similar (at least it is indeed about the same blu-ray and you can see many matches), however there are some errors since there are invalid descriptor types 0 and 3 defined in that file.
@Nalor: Maybe you can make sure the fix-up table is applied in modes other than 5?
I tested mode 4 several times and it does not produce a version that is ok.
Here is the File:
http://s000.tinyupload.com/?file_id=01058085668919539554
candela
1st March 2017, 19:15
You simply need to use mode 3 instead of 4 if you want BD+. It clearly says so in the options
I checked the tables and the Pavtube and Leawo table is identical in terms of patches. The descriptor types in Leawo tables are always invalid. They have to be ignored and all patches need to be applied
nalor
2nd March 2017, 23:17
I'd like that it is possible to work on a BD content that I copied over to a directory on harddrive/SSD, and not available as disc directly or as ISO.
Changed the code to support file copies of discs - please test 0.54 and report all findings..
I quickly checked and I think it should work ;)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.