Ripping via 0800 BenQ - xbox 360 AP25 checks

dibbers

Premium Member
Premium Member
Joined
May 18, 2005
Messages
11,797
Reaction score
1,387
Location
Ipswhich
Evening,

(I know they say that the liteons have better success ripping etc than the BenQ's for reading the AP25 sections etc.)

I see that when you do a rip via the new XBC that it checks the AP25 measurements, it's well slow like, just to get it right I do a save and make an ISO? Is there any other settings that I need to do, I notice there's a fill video partition for xtreme etc?

Still I'd rather it take it's time and get it right than rush it along.

Ta.


battlefieldrip.jpg
 
Here's a log so far.......(ah it's created me a .dvd file so happy days)

Space Available on Drive X:\ 372 GB (399,949,492,224 bytes)
Creating SplitVid backup image [E]
Opening image output file
Reading Video Layer0
Opening image output file
Reading Video Layer1
Adding Filler Layer0
Processing AP25 Sector
Processing PFI Sector
Processing DMI Sector
Processing Security Sector
========================================
<-- Security Sector Details -->
Source Drive: VAD6038
----------------------------------------
Game Partition PFI
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
----------------------------------------
Xbox Version: 02
----------------------------------------
Xbox XGD3 Flag: 06
----------------------------------------
TimeStamp of Authoring: 03/10/2011
TimeStamp of Mastering: 07/10/2011 22:21:37
----------------------------------------
Media ID
XXXXXXXXXXXXXXXXXXXXXXX-XXXXXXX
----------------------------------------
CPR_MAI Key
XXXFXXXXX
----------------------------------------
RT CID MOD DATA Drive Response
-- -- -- ------------- -------------------
DATA HERE
--------------------------------------------
Adding Filler Layer0
Unlocking Game Partition
Reading XDVDFS File system
Reading Volume Descriptor
Reading Volume Descriptor
Sorting Section Map
Optimizing Section Map
Reading Game Partition
Setting read speed to 12x

Adding Filler Layer0
Unlocking Game Partition
Reading XDVDFS File system
Reading Volume Descriptor
Reading Volume Descriptor
Sorting Section Map
Optimizing Section Map
Reading Game Partition
Setting read speed to 12x
Setting read speed to 5x
Adding Filler Layer1
Appending Video Layer1
Creating Layer Break File
LayerBreak file saved as: "Battlefield 3 Disk1.dvd"
Getting media info [E]
Media Type: DVD-ROM
Bytes Used: 8.07 GB (8,662,351,872 bytes)
Read completed in 01:13:13
 
Last edited:
Just thought I'd share one error I got there and haven't continued, I wonder if I should get the Liteon out and get it flashed with the 0800 V3 and see if that makes any difference.

xboxreadfail1.jpg

Just to let you know it was a dirty disk, cleaned and then done again, this time with no error's
 
Last edited:
Just to let you know that it is recommended to not take your own topology data as there can be wrong measurements taken depending on laser quality, disc condition etc.. The 2 topolgy files provided have been taken over lots of consoles and discs and average values taken. Several members over at TX forums advised that there is no point in selecting getting AP2.5 data if you have topology patches but were advised by the mods you have to. They then had to do a dramatic u-turn as there is no need to get this data if you have patches and it dramatically reduces backup times.
 
Last edited:
Is there a way to turn it off when it's reading then, I don't see any option...........but I have been ripping in the planning of using the uploaded versions of topoligy just i forgot to patch these 2.

It's probably why they say use a liteon if you want your own AP25
 
heck out the below info which explains things credits to TX forums

Making Your Own Rips
When ripping your own discs with the latest Xbox Backup Creator v2.9 Build 350 you should have "processing AP2.5" unchecked. This adds an extra hour to each game rip and is not required. This option is only used when topology data is being collected for development purposes.

Remember that angle measurements need to be as accurate as possible. If you rip your own you are using just 1 set of measurements. Your laser may be weak or you may have just one measurement out of hundreds that is out of bounds of the accepted values and your disc will error and you will be flagged for an AP2.5 Failure (See point #3)

FYI the accepted values are -/+ 22 (even though originals rarely go above -/+ 2 with a perfect quality laser - the extra is allowed for those that have a poor quality laser)

The median files that are created are the work of HUNDREDS of dumps per game over many different consoles and many different drives. Then using a complex algorithm millions of individual results are then calculated to give the absolute best timing scenario possible. The median files that are provided give a deviation of -/+ 8 (The original target was 9 - so anything below this is considered awesome).

To give you an idea of what we are talking about here is the deviation data when using the median file on an XGD3 title: LT3.0 - Liteon - 14699DAE - Forza 4 BU - New Median - Pastebin.com

As you can see the results are superb and rarely go above -/+ 4 with a maximum of 8 in just one instance.

However if you rip your own you may find that some angles will go up to -/+ 100 which is WAY over the -/2 22 threshold and will give you a bad image.

So when ripping your own images, uncheck Process AP2.5, patch with the given median file and then burn. There may be a simple app coded for you to check the deviation values of your own rips in the near future.

Note: The XGD3 Median Topology file covers ALL current XGD3 games. This includes other languages too. There is no need for you to check the profile of your game at this moment in time. If you are 100% certain that the median file does not work with your XGD3 title then you need to rip the original game using the new XBC and test it again. If it then DOES work then you need to report it with the Profile ID of the game and the AP25 topology file (after checking process AP2.5 of course). If you can't do this then dont bother posting about it.
 
cool that's what i was doing just the long way then, ripping the ap25 when not needed, I was then patching it with the released ones, or not patching it in this case...Thanks for that.
 
Back
Top