BD-RB to compress FULL "The Last Stand"?

[setarip_old]

Among other things, "The Last Stand" Blu-ray contains a whole bunch of VERY LARGE (almost 1Gig each) "JAR" files (undoubtedly, many are dummies), swelling the overall disc size to 49.2Gigs.

When I try to use BD-RB to compress the FULL Disc to 25Gigs, I get a message stating that my source disc is too large to be compressed by BD-RB.

I presume I'm simply overlooking a required setting to accomplish this. Hopefully, someone will be good enough to help me resolve this mystery.

(Yes, I've already made a movie only version of what may actually prove to be "Ahnold's" Last Stand ;>})

Thank you.

[Ch3vr0n]

just a hunch here, but sounds alot like a disc posted on the slysoft forums. Is there a 55555 folder present under the BDMV\JAR folder ?

[setarip_old]

@Ch3vr0n

Nope, you seem to have had a bad hunch. There is no such sub-directory anywhere on the disc.

Exact error (generated by BD-RB) is "Target is too small to continue"

The drive that the "target files would go to has 1/2 terabyte of free space!

LOg: ----------------------
[05/25/13] BD Rebuilder v0.44.09 (beta)
[21:09:17] Source: LASTSTAND
- Input BD size: 49.25 GB
- Approximate total content: [02:07:41.194]
- Target BD size: 22.95 GB
- Windows Version: 6.0 [6002]
- Quality: High-Speed Option (BD-25), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
- Target too small. Encode stopped.

[SquallMX]

Among other things, "The Last Stand" Blu-ray contains a whole bunch of VERY LARGE (almost 1Gig each) "JAR" files (undoubtedly, many are dummies), swelling the overall disc size to 49.2Gigs.

When I try to use BD-RB to compress the FULL Disc to 25Gigs, I get a message stating that my source disc is too large to be compressed by BD-RB.

I presume I'm simply overlooking a required setting to accomplish this. Hopefully, someone will be good enough to help me resolve this mystery.

(Yes, I've already made a movie only version of what may actually prove to be "Ahnold's" Last Stand ;>})

Thank you.

The JAR files are big dummy files, you can remove them without consequences, my backup got an average 14 Mbps bitrate after that.

[setarip_old]

@SquallMX

Hi! The JAR files are big dummy files, you can remove them without consequences, my backup got an average 14 Mbps bitrate after that. That was the first "cure" I attempted - and the result was a static black screen.

Did you remove JUST the Jar Files, the Jar Files and the JAR Directory, or the JAR files, the Jar DIRECTORY and the BACKUP Jar Directory? (In my similar attempt, I only removed the files from the primary JAR directory and left both the [empty] primary Jar DIRECTORY and the BACKUP JAR directory intact)...

What settings did you use for filesize?

[Ch3vr0n]

I'd post on the slysoft forums if i were you. I may not have been correct on that folder name, but i know I'm right about a similar disc with dummy files. Some folder had to be deleted and everything was just peechy then.

Verstuurd van mijn HTC Sensation XE with Beats Audio Z715e met Tapatalk

[jdobbs]

@Ch3vr0n

Nope, you seem to have had a bad hunch. There is no such sub-directory anywhere on the disc.

Exact error (generated by BD-RB) is "Target is too small to continue"

The drive that the "target files would go to has 1/2 terabyte of free space!

LOg: ----------------------
[05/25/13] BD Rebuilder v0.44.09 (beta)
[21:09:17] Source: LASTSTAND
- Input BD size: 49.25 GB
- Approximate total content: [02:07:41.194]
- Target BD size: 22.95 GB
- Windows Version: 6.0 [6002]
- Quality: High-Speed Option (BD-25), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
- Target too small. Encode stopped. It means that the target size you have selected is smaller than the total of the files that have to be copied. Obviously that must be caused by the JAR files.

I have to be very careful not to add anything to BD-RB that might be construed as "circumventing a copyright protection mechanism" -- and this sounds a lot like copy protection.

I'll pick up "The Last Stand" and give it a test.

[Ch3vr0n]

@jdobbs: that's exactly what the folks at slysoft also thought it was. They asked for a few logfile, got them and came to the conclusion that that folder with dummy files served absolutely no purpose but to exceed the maximum capacity of a normal disc to prevent backing up the disc. Simply deleting that 55555 folder with the dummy files worked flawlessley as they were totally unreferenced throughout the entire disc structure otherwise

[jdobbs]

@jdobbs: that's exactly what the folks at slysoft also thought it was. They asked for a few logfile, got them and came to the conclusion that that folder with dummy files served absolutely no purpose but to exceed the maximum capacity of a normal disc to prevent backing up the disc. Simply deleting that 55555 folder with the dummy files worked flawlessley as they were totally unreferenced throughout the entire disc structure otherwiseDid they say they are going to check for unreferenced JAR files in their next version and remove them? I have to leave the ripping mechanisms to them.

[Ch3vr0n]

don't think they have. That disc was a few versions ago already. Probably figured it was a one-off case. Can't seem to find the topic on the forums though.

[Capsbackup]

This form of protection came up a while back on Breaking Dawn Part 2.
By simply deleting the 06000 folder from the JAR folder of that disc lets TMT3 play it back properly, and BD-RB does not throw up the error message!
This was confirmed by Peer as an acceptable fix.
I believe Slysoft is still working on a fix for the several versions of The Last Stand that are available. :(

EDIT: BD-RB made a perfect BD5 test backup once the 06000 JAR folder was deleted.

[Ch3vr0n]

Disregard the first few posts http://forum.slysoft.com/showthread.php?t=56146

[Capsbackup]

AnyDVD HD update 7.2.0.2 beta appears to have fixed the reported problems with correctly ripping this disc.
However, the problem with BD-RB complaining about the source file is too large cannot be removed unless the 06000 JAR folder, which contains the 26.5 GB files, is deleted. So ripping to dvd folders is necessary to be able to delete this folder before running BD-RB. :cool:

[Ch3vr0n]

so jdobbs, doubt you'll be able to implement a routine to check for such files without going into the "grey" area of protection circumvention allowed or not.

[Ghitulescu]

Any particular interest in keeping those JARs?
I mean, are those menus that important, maybe life-saving ;) ? Do you have menus in theatres?

[Ch3vr0n]

The only purpose they serve is to fill up a disc kinda like SSIF does for 3D discs. Rip it to folder structure and it becomes too big to burn back to a blank. In the case of those JAR files they can safely be deleted from the structure. They aren't needed for proper disc playback. They only make it too big to burn.

[Capsbackup]

Any particular interest in keeping those JARs?
I mean, are those menus that important, maybe life-saving ;) ? Do you have menus in theatres?

The only JAR folder deleted is the one that contains the bogus 26.5 GB files. The menu and all original disc structure is preserved.

[jdobbs]

so jdobbs, doubt you'll be able to implement a routine to check for such files without going into the "grey" area of protection circumvention allowed or not.It's completely acceptable to ignore unreferenced content when making a backup -- that happens all the time and is a standard check. The problem for me is how to determine that it is unreferenced. It seems you'd almost have to create a Java emulator to find that.

[setarip_old]

@Ghitulescu

Any particular interest in keeping those JARs? I mean, are those menus that important, maybe life-saving ? Do you have menus in theatres? Is the SOLE use of JAR files on Blu-ray discs to process and generate menus?

[Ghitulescu]

@Ghitulescu

Is the SOLE use of JAR files on Blu-ray discs to process and generate menus?

No, it's not.
But they are not indispensable for the normal playback.

[setarip_old]

I, for one (and I'm sure there are others) prefer to be able to access ALL functions of purchased Blu-rays...

[jdobbs]

Interestingly, if you rename those .JAR files to .M2TS and play them you'll find that they are whole bunch of repeated audio segments.

[setarip_old]

@capsbackup EDIT: BD-RB made a perfect BD5 test backup once the 06000 JAR folder was deleted.Certainly that's not the ONLY protection on the "Last Stand" Blu-ray disc. I say that because ONLY removing the 6000 directory leaves you with a disc that is suddenly limited to two or three chapters and jumps from place to place each time you try to restart it...

[Capsbackup]

@capsbackup Certainly that's not the ONLY protection on the "Last Stand" Blu-ray disc. I say that because ONLY removing the 6000 directory leaves you with a disc that is suddenly limited to two or three chapters and jumps from place to place each time you try to restart it...

After ripping the disc with AnyDvd HD 7.2.0.2 beta, then deleting the 06000 JAR folder, this Blu-ray played back perfectly, no problems like you have described.
BD-RB was then able to do a full disc backup to BD5 once this jar folder was removed, and that played back equally as well.

[setarip_old]

@Capsbackup

JUst a late note to confirm that your post #24 to this thread was 100% correct - Sequence is everything ;>}

Thank you ;>}

[sparkyar]

you´re next has a similar problem, jar folder 05001 (7.31gb), seems like 8 dummy files 936mb each