BD Ripper (3D Plus) 8.1.2.2 won't complete pass through normally

[chertens]

This is the same issue I reported for all releases after 8.1.0.0.

On Bluray rips using pass through the rip will not complete normally. The user must press cancel to stop the application.

The resulting ripped file is incomplete now as well, at least it is a smaller file size than under 8.1.0.0 or even 8.1.2.1.

I have seen another report with the same response that the problem has been found and it will be fixed immediately.

When the fix is in a beta, can it be specifically called out so I know when to try again?

The BD ROM that causes this consistently is Heartbreak Ridge from the two disc set also including Firefox.

I have to admit I am a bit frustrated at this point and will provide any additional information that might help.

[jbinkley60]

8.1.2.2 won't complete pass through normally

I am seeing the same thing with 8.1.2.2 beta. I just ripped the first disk of Star Wars with m2ts passthrough and it never finishes. The rip completes by DVDfab but never posts a finished message. I cancelled the rip and the file plays fine though. The same Blu-Ray rips fine with the AC3 high quality remux profile and posts a finished message.

DVDFab 8.1.2.2 (2011/09/27 02:35:28)

0m 00.96s: Qt Translator file load success
0m 01.37s: option dvd2dvd 1 dvd2mobile 1 bluray2bluray 1 bd2mobile 1 bd23d 1 bd2dvd 1 file2mobile 1 filemover 1
0m 45.56s: detected blu-ray
0m 45.56s: drive X
0m 45.56s: blu-ray type 1
0m 45.56s: volume label THE_PHANTOM_MENACE
0m 50.01s: aacs 1 bd+ 1
0m 54.24s: got discinfo
0m 54.42s: got bdmv
0m 54.44s: Vendor: ATAPI
0m 54.44s: Product: iHBS212 2
0m 54.44s: Revision: 5L06
0m 54.44s: Vendor specific: 2010/09/09 15:55
0m 54.44s: AACS version: 1
0m 54.44s: Number of concurrent AGIDs: 2
0m 54.44s: Supports bus encryption: NO
0m 54.44s: Supports binding nonce generation: NO
0m 54.44s: Supports Hybrid discs: NO
0m 54.44s: got agid 0
0m 54.50s: sent host cert chal
0m 54.50s: got drive cert chal
0m 54.50s: BEC 0
0m 54.50s: DRIVE_VENDOR 0x0128
0m 54.58s: got drive key
0m 54.78s: got host key signature
0m 54.78s: verified drive signature
0m 54.78s: verified host signature
0m 54.86s: sent host signature and key point
0m 54.86s: got bus key
0m 54.88s: got agid 0
0m 54.94s: sent host cert chal
0m 54.94s: got drive cert chal
0m 54.94s: BEC 0
0m 54.94s: DRIVE_VENDOR 0x0128
0m 55.02s: got drive key
0m 55.02s: got host key signature
0m 55.02s: verified drive signature
0m 55.02s: verified host signature
0m 55.10s: sent host signature and key point
0m 55.10s: got bus key
0m 57.23s: got volume id
0m 57.23s: got volume id mac
0m 57.23s: volume id is correct
0m 57.23s: got vid
0m 58.15s: blu-ray 855D3D6592D2D0BAB12B4CB31F860ED6091A42BB
0m 58.67s: cert BEE=0x00 same
1m 02.13s: D 5F7D6A77
1m 06.50s: got vuk
1m 06.50s: got fut
1m 06.83s: got unit key 7
1m 16.78s: got extended bdinfo
1m 16.78s: opened blu-ray
1m 51.29s:

------ begin mobile work(1/1) ------


1m 51.29s: info: create config(5)
1m 51.29s: info: convert profile(m2ts.passthrough)
1m 51.29s: info: bluray playlist(800),angle(1),chapter(1->51),3D(0)
1m 51.29s: info: streams((4113.1)(4353.1)(4608.16)(4618.16)(4619.16 )(4636.16)(4637.16)(4638.16))
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: info: subpicture preset(2), mode(2)
1m 51.30s: subpicture(4608) mode(2)
1m 51.32s: info: processing source(00882.m2ts)
2m 30.32s: info: processing source(00800.m2ts)
201m 18.08s:

[willarias]

I have the same problem with DVDFab holding at 100% and forcing cancellation (files play fine as far as I can tell).

This has been happening to me since 8.1.1.8 and the problem continues with the latest non-beta version 8.1.2.0. This occurs when ripping both Bluray and DVD to my preferred profile (Xbox).

It's worth noting that in a separate thread on this issue, a DVDFab moderator indicated on Sept 23rd that they were aware of the bug and working on a fix. Thread is closed so I'm not sure what the timeline is for the fix.

[terry5]

Hi，
We have found this issue and dealing with it. Please wait for the fixed release.

Thanks.
terry5