› Foros › Xbox 360 › Grabación
Redline99 escribió:Basically what the problem is, is that the video data that was supposed to be located on layer 1 (the second layer) is being truncated because it is outside of the valid PSN range dictated by the PFI. To correct this the video (VL1) data is actually supposed to be split off from the rest of the video data (VL0) and placed AFTER the game data. This moves it to a PSN location that is visible when the dvd is in a locked state. Currently that data will show as just 00 data, thus looks missing or truncated.Example proper iso build order, Xbox360
000A90 Video L0
01F090 Filler L0 'Actual
- OR -
01F08D Filler L0
000003 PFI, DMI, SS 'Xtreme
1B3880 Game L0
1B3880 Game L1
01F090 Filler L1
00032F Video L1
------
3A5FDF Total (7,834,892,288 Bytes)
| FILLER |
|-------------|------|------------|-------------------------------|----------| L1
VL1E VL1S GL1E GL1S
| FILLER | |
|--------|-----------|--------|PDS|-------------------------------|----------| L0
VL0S VL0E GL0S GLOE
PSN |0x30000
VL0S = Video Layer0 Start
VL0E = Video Layer0 End
VL1S = Video Layer1 Start
VL1E = Video Layer1 End
GL0S = Game Layer0 Start
GL0E = Game Layer0 End
GL1S = Game Layer1 Start
GL1E = Game Layer1 End
PDS = PFI, DMI, SS
Redline99 escribió:1. Why does is still state that "VIDEO IS QUESTIONABLE" after we patch to the new Splitvid format?
Because it was wasn't completely finished as a release feature.2. Why is it NOT patching the splitvid image directly when you intially now do a READ using the 'patched' version of XBC v2.5..the key word here is "initially"
Not sure, it works for me fine. I tested it tonight.
Read Burnout Revenge (Original ISO Format) = 7.05 GB (7,572,881,408 bytes)
Read Burnout Revenge (SplitVid ISO Format) = 7.29 GB (7,834,892,288 bytes)**
Converted Burnout Revenge (Original ISO Format to SplitVid) = 7.29 GB (7,834,892,288 bytes)
So it looks to be working for me, put the Log Level on Debug, do a complete backup using SPlitVid and PM me the log.
**The SplitVid format ISO size can differ slightly depending on the Video partition size
Redline99 escribió:"might conflict....." means that until the final version of the firmware come out, I can't say how it will behave.
The older Xtreme firmware I think were like the Geremia, then Xtreme v3 came out and corrected the pfi issues. But, as of Xtreme52 and 53, I know that it did not read video layer1 correctly. What I did to prove that was patched the inquiry handler to get rid of the 0xC0 vender bits check. That allowed me to boot into Windows without using the enable0800 dvd. So then I should have been in a state that was pretty close to how the Xbox would see the dvd when still locked. Then using IsoBuster to view the sectors, I could see for myself that the bytes returned 00 for all of video layer1. Using the SplitVid format the bytes read as they were supposed to.
Which leads to why is the SplitVid not recommended now... Well the new iXtreme may address this in some fashion but, the way that I implemented the SplitVid probably wont work well with the fix. The main reason for that is my current version of SplitVid removes the out of place Video Layer1 data and relocates it to the "proper" position at the end of the game data. What I should have done to maintain the best compatibility is to leave the errored video layer1 data and placed a copy of it in the proper position. This would double up on that data but provide the best compatibility for both the new iXtreme and the soon to be old Xtreme firmwares.
Redline99 escribió:And if I remember right, C4E mentioned that his firmware took care of this; thus there was no need for the backups to change. So why this change?
Yeah, right. C4e locks the ranges down. So an xtreme 3 and SplitVid disc should appear as the same to the box. This change is mainly implemented to give the opportunity for SplitVid if someday this is needed. This could be also helpful for other hackers, not only users, to do some tests on the original XBOX disc layout. There is definitely no need to get in panic about the new format. The xtreme 3 style images have the same stealthness! So there is no need to reburn all discs.
The ISO format is not "stealthy" on pre iXtreme firmwares. This new SplitVid format with be stealthy on both pre iXtreme (5.3 and lower) and iXtreme firmwares. So this format has the best compatibility as it works for both. If you don't use the iXtreme, Hitachi included, then there is a level of risk. But also I don't know of MS actually looking at the video partition right now anyways. As with anything the choice is yours, we just help provide the options.
Nice work Schtrom, I'll have to check out the new release when I get back... Wink
Redline99 escribió:Before IXtreme came out the firmware didn't really treat the video data correctly. It was cutting half of it out when read by the xbox... The data was there just not in the correct position, that was happening since the very first xtreme firmware and the batch files to build the iso's. When IXtreme came out c4eva fixed the firmware to support the incorrect iso's. So that means anything before IXtreme doesn't read the video data correctly. What splitvid does is copy the video data that it wasn't reading to a position where it will read it correctly.
So now the current splitvid has the data in the correct position for both the old firmware and the new firmwares.
But... it is not a big deal right now because as far as I know the xbox doesn't error out on half of the video data missing. And if you use IXtreme then its been fixed in the firmware anyways. Either way splitvid doesnt hurt anything it adds more compatibility. VDMulleter may not treat the original iso layout as an issue, because its only a possible issue on old firmwares.
Its just an extra precaution that if you use a non IXtreme firmware to play games then you should use splitvid, but you don't have to for any real reason and thats why its an option.
You can upgrade to 2.6 and just turn off the splitvid in the options.
Rossyafk escribió:El tema del Splitvid es una megalocura que esta creando una confusión brutal (yo soy un confundido más), por ello, he ido directamente a una de las fuentes principales, las palabras de Redline99 (creador del Xbox Backup Creator).
Basically what the problem is, is that the video data that was supposed to be located on layer 1 (the second layer) is being truncated because it is outside of the valid PSN range dictated by the PFI. To correct this the video (VL1) data is actually supposed to be split off from the rest of the video data (VL0) and placed AFTER the game data. This moves it to a PSN location that is visible when the dvd is in a locked state. Currently that data will show as just 00 data, thus looks missing or truncated.
1. Why does is still state that "VIDEO IS QUESTIONABLE" after we patch to the new Splitvid format?
Because it was wasn't completely finished as a release feature.2. Why is it NOT patching the splitvid image directly when you intially now do a READ using the 'patched' version of XBC v2.5..the key word here is "initially"
Not sure, it works for me fine. I tested it tonight.
Read Burnout Revenge (Original ISO Format) = 7.05 GB (7,572,881,408 bytes)
Read Burnout Revenge (SplitVid ISO Format) = 7.29 GB (7,834,892,288 bytes)**
Converted Burnout Revenge (Original ISO Format to SplitVid) = 7.29 GB (7,834,892,288 bytes)
So it looks to be working for me, put the Log Level on Debug, do a complete backup using SPlitVid and PM me the log.
**The SplitVid format ISO size can differ slightly depending on the Video partition size
1. ¿Por qué, aún después de haber parcheado con el nuevo formato de Splitvid, indica "VIDEO IS QUESTIONABLE"?
2. ¿Por qué no se parchea la imagen Splitvid directamente cuando inicialmente haces una lectura usando una versión previamente parcheada de Xbox Backup Creator v2.5? (Aquí la palabra clave es inicialmente)
"might conflict....." means that until the final version of the firmware come out, I can't say how it will behave.
The older Xtreme firmware I think were like the Geremia, then Xtreme v3 came out and corrected the pfi issues. But, as of Xtreme52 and 53, I know that it did not read video layer1 correctly. What I did to prove that was patched the inquiry handler to get rid of the 0xC0 vender bits check. That allowed me to boot into Windows without using the enable0800 dvd. So then I should have been in a state that was pretty close to how the Xbox would see the dvd when still locked. Then using IsoBuster to view the sectors, I could see for myself that the bytes returned 00 for all of video layer1. Using the SplitVid format the bytes read as they were supposed to.
Which leads to why is the SplitVid not recommended now... Well the new iXtreme may address this in some fashion but, the way that I implemented the SplitVid probably wont work well with the fix. The main reason for that is my current version of SplitVid removes the out of place Video Layer1 data and relocates it to the "proper" position at the end of the game data. What I should have done to maintain the best compatibility is to leave the errored video layer1 data and placed a copy of it in the proper position. This would double up on that data but provide the best compatibility for both the new iXtreme and the soon to be old Xtreme firmwares.
And if I remember right, C4E mentioned that his firmware took care of this; thus there was no need for the backups to change. So why this change?
Yeah, right. C4e locks the ranges down. So an xtreme 3 and SplitVid disc should appear as the same to the box. This change is mainly implemented to give the opportunity for SplitVid if someday this is needed. This could be also helpful for other hackers, not only users, to do some tests on the original XBOX disc layout. There is definitely no need to get in panic about the new format. The xtreme 3 style images have the same stealthness! So there is no need to reburn all discs.
The ISO format is not "stealthy" on pre iXtreme firmwares. This new SplitVid format with be stealthy on both pre iXtreme (5.3 and lower) and iXtreme firmwares. So this format has the best compatibility as it works for both. If you don't use the iXtreme, Hitachi included, then there is a level of risk. But also I don't know of MS actually looking at the video partition right now anyways. As with anything the choice is yours, we just help provide the options.
Nice work Schtrom, I'll have to check out the new release when I get back... Wink
Si no recuerdo mal, C4E mencionó que su firmware se hacía cargo de esto, entonces no había necesidad alguna de cambiar los backups. ¿Por qué cambiarlos ahora?
Cierto, C4E bloquea los rangos. Por lo tanto, en un Xtreme 3 y un disco Splitvid podrían parecer lo mismo para la consola. Este cambio fue implementado, principalmente para dar la oportunidad al Splitvid si algún día era necesario. Esto también podría ayudar a otros hackers, no solamente usuarios, para hacer pruebas en la estructura de los discos originales de Xbox. Definitivamente, no es necesario precipitarse sobre este nuevo formato. ¡El estilo de formato de Xtreme 3 tiene las mismas capacidades de ocultación! Por lo que no es necesario de regrabar odos los discos.
Before IXtreme came out the firmware didn't really treat the video data correctly. It was cutting half of it out when read by the xbox... The data was there just not in the correct position, that was happening since the very first xtreme firmware and the batch files to build the iso's. When IXtreme came out c4eva fixed the firmware to support the incorrect iso's. So that means anything before IXtreme doesn't read the video data correctly. What splitvid does is copy the video data that it wasn't reading to a position where it will read it correctly.
So now the current splitvid has the data in the correct position for both the old firmware and the new firmwares.
But... it is not a big deal right now because as far as I know the xbox doesn't error out on half of the video data missing. And if you use IXtreme then its been fixed in the firmware anyways. Either way splitvid doesnt hurt anything it adds more compatibility. smile_XDVDMulleter may not treat the original iso layout as an issue, because its only a possible issue on old firmwares.
Its just an extra precaution that if you use a non IXtreme firmware to play games then you should use splitvid, but you don't have to for any real reason and thats why its an option.
You can upgrade to 2.6 and just turn off the splitvid in the options.
pinaculo escribió:gracias Mithrandir0x, esa pedazo de traducción.
lo que saco de resumen es que no es malo meter los splitvid en los firmware ixtreme, que es una compatibilidad más.
pero que sí es necesario en los firm anteriores al ixtreme.
mmmm, de momento lo que se estaba diciendo.
yo por si acaso todas las copias nuevas las estoy sacando con el splitvid, así tendrá todo lo compatible.
igual me banean por dar demasiada información
otra vez más, gracias titán
pinaculo escribió:el problema es que los juegos los extraes con el splitvid o sin él.
por lo que yo he leido nada lee un juego como viene originalmente, y este es el mayor problema.