"There appears to been an ISO write error" [Archive]

View Full Version : "There appears to been an ISO write error"

rack04

21st March 2007, 04:19

I was trying to encode "Rocky Balboa" using DVD Rebuilder v1.23.1 but got the following error:

[20:06:18] One Click encoding activated...
-----------------
[20:06:37] Phase I, PREPARATION started.
- DVD-RB v1.23.1
- AVISYNTH 2.5.6.0
- CCE 2.70.2.9 encoder selected.
- "Movie and Menus Only" mode is enabled.
- Source: ROCKY BALBOA
- VTS_01: 341,673 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 31,990 frames.
-- Building .AVS and .ECL files
- VTS_02: 23,856 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2,753 frames.
-- Building .AVS and .ECL files
- VTS_03: 29,525 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2,799 frames.
-- Building .AVS and .ECL files
- VTS_04: 151,144 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 13,588 frames.
-- Building .AVS and .ECL files
- VTS_05: 2,015,479 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 146,456 frames.
-- Building .AVS and .ECL files
- VTS_06: 324,342 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 37,378 frames.
-- Building .AVS and .ECL files
- VTS_07: 361,625 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 41,863 frames.
-- Building .AVS and .ECL files
- VTS_08: 51,224 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,573 frames.
-- Building .AVS and .ECL files
- VTS_09: 51,061 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,575 frames.
-- Building .AVS and .ECL files
- VTS_10: 45,547 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,185 frames.
-- Building .AVS and .ECL files
- VTS_11: 42,042 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 3,823 frames.
-- Building .AVS and .ECL files
- VTS_12: 51,611 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,635 frames.
-- Building .AVS and .ECL files
- VTS_13: 51,681 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,695 frames.
-- Building .AVS and .ECL files
- VTS_14: 50,743 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,545 frames.
-- Building .AVS and .ECL files
- VTS_15: 48,319 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,380 frames.
-- Building .AVS and .ECL files
- VTS_16: 38,839 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 3,463 frames.
-- Building .AVS and .ECL files
- VTS_17: 22,232 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 1,587 frames.
-- Building .AVS and .ECL files
- VTS_18: 51,392 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,575 frames.
-- Building .AVS and .ECL files
- VTS_19: 49,765 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,423 frames.
-- Building .AVS and .ECL files
- VTS_20: 1,612 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 244 frames.
-- Building .AVS and .ECL files
- VTS_89: 10 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 1 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 57.6%
- Overall Bitrate : 2,819/2,255Kbs
- Space for Video : 3,749,394KB
- Blanking all EXTRA Segments
-- Feature before/after: 2,423 / 5,284 Kbs
-- FEATURE does not require reencoding.
[20:10:17] Phase I, PREPARATION completed in 4 minutes.
[20:10:17] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
- Creating M2V for VTS_04 segment 2
- Creating M2V for VTS_04 segment 3
- Creating M2V for VTS_04 segment 4
- Creating M2V for VTS_04 segment 5
- Extracting Video for VTS_05 segment 0
- Creating M2V for VTS_05 segment 1
- Creating M2V for VTS_05 segment 2
- Creating M2V for VTS_05 segment 3
- Creating M2V for VTS_05 segment 4
- Creating M2V for VTS_05 segment 5
- Creating M2V for VTS_05 segment 6
- Creating M2V for VTS_05 segment 7
- Creating M2V for VTS_05 segment 8
- Creating M2V for VTS_05 segment 9
- Creating M2V for VTS_05 segment 10
- Creating M2V for VTS_05 segment 11
- Creating M2V for VTS_05 segment 12
- Creating M2V for VTS_05 segment 13
- Creating M2V for VTS_05 segment 14
- Creating M2V for VTS_05 segment 15
- Creating M2V for VTS_05 segment 16
- Creating M2V for VTS_05 segment 17
- Creating M2V for VTS_05 segment 18
- Creating M2V for VTS_05 segment 19
- Creating M2V for VTS_05 segment 20
- Creating M2V for VTS_05 segment 21
- Creating M2V for VTS_05 segment 22
- Creating M2V for VTS_05 segment 23
- Creating M2V for VTS_05 segment 24
- Creating M2V for VTS_05 segment 25
- Creating M2V for VTS_05 segment 26
- Creating M2V for VTS_05 segment 27
- Creating M2V for VTS_05 segment 28
- Extracting Video for VTS_05 segment 29
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Creating M2V for VTS_06 segment 3
- Creating M2V for VTS_07 segment 0
- Creating M2V for VTS_07 segment 1
- Creating M2V for VTS_07 segment 2
- Creating M2V for VTS_07 segment 3
- Creating M2V for VTS_07 segment 4
- Creating M2V for VTS_07 segment 5
- Creating M2V for VTS_07 segment 6
- Creating M2V for VTS_07 segment 7
- Creating M2V for VTS_07 segment 8
- Creating M2V for VTS_07 segment 9
- Creating M2V for VTS_07 segment 10
- Creating M2V for VTS_07 segment 11
- Creating M2V for VTS_07 segment 12
- Creating M2V for VTS_07 segment 13
- Creating M2V for VTS_07 segment 14
- Creating M2V for VTS_07 segment 15
- Creating M2V for VTS_08 segment 0
- Creating M2V for VTS_08 segment 1
- Creating M2V for VTS_09 segment 0
- Creating M2V for VTS_09 segment 1
- Creating M2V for VTS_10 segment 0
- Creating M2V for VTS_10 segment 1
- Creating M2V for VTS_11 segment 0
- Creating M2V for VTS_11 segment 1
- Creating M2V for VTS_12 segment 0
- Creating M2V for VTS_12 segment 1
- Creating M2V for VTS_13 segment 0
- Creating M2V for VTS_13 segment 1
- Creating M2V for VTS_14 segment 0
- Creating M2V for VTS_14 segment 1
- Creating M2V for VTS_15 segment 0
- Creating M2V for VTS_15 segment 1
- Creating M2V for VTS_16 segment 0
- Creating M2V for VTS_16 segment 1
- Creating M2V for VTS_17 segment 0
- Creating M2V for VTS_17 segment 1
- Creating M2V for VTS_18 segment 0
- Creating M2V for VTS_18 segment 1
- Creating M2V for VTS_19 segment 0
- Creating M2V for VTS_19 segment 1
- Creating M2V for VTS_20 segment 0
- Creating M2V for VTS_20 segment 1
- Extracting STILLS for VTS_89 segment 0
[22:08:15] Phase II ENCODING completed in 118 minutes.
[22:08:15] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Processing VTS_03
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Processing VTS_04
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 2 VOBID 2 CELLID 1
- Rebuilding seg 3 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 4 VOBID 3 CELLID 1
- Rebuilding seg 5 VOBID 3 CELLID 2
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Processing VTS_05
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Rebuilding seg 2 VOBID 2 CELLID 2
- Rebuilding seg 3 VOBID 2 CELLID 3
- Rebuilding seg 4 VOBID 2 CELLID 4
- Rebuilding seg 5 VOBID 2 CELLID 5
- Rebuilding seg 6 VOBID 2 CELLID 6
- Rebuilding seg 7 VOBID 2 CELLID 7
- Rebuilding seg 8 VOBID 2 CELLID 8
- Rebuilding seg 9 VOBID 2 CELLID 9
- Rebuilding seg 10 VOBID 2 CELLID 10
- Rebuilding seg 11 VOBID 2 CELLID 11
- Rebuilding seg 12 VOBID 2 CELLID 12
- Rebuilding seg 13 VOBID 2 CELLID 13
- Rebuilding seg 14 VOBID 2 CELLID 14
- Rebuilding seg 15 VOBID 2 CELLID 15
- Rebuilding seg 16 VOBID 2 CELLID 16
- Rebuilding seg 17 VOBID 2 CELLID 17
- Rebuilding seg 18 VOBID 2 CELLID 18
- Rebuilding seg 19 VOBID 2 CELLID 19
- Rebuilding seg 20 VOBID 2 CELLID 20
- Rebuilding seg 21 VOBID 2 CELLID 21
- Rebuilding seg 22 VOBID 2 CELLID 22
- Rebuilding seg 23 VOBID 2 CELLID 23
- Rebuilding seg 24 VOBID 2 CELLID 24
- Rebuilding seg 25 VOBID 2 CELLID 25
- Rebuilding seg 26 VOBID 2 CELLID 26
- Rebuilding seg 27 VOBID 2 CELLID 27
- Rebuilding seg 28 VOBID 2 CELLID 28
- Rebuilding seg 29 VOBID 2 CELLID 29
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
- Updating TMAP table...
- Processing VTS_06
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 2 VOBID 2 CELLID 1
- Rebuilding seg 3 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Updating TMAP table...
- Processing VTS_07
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 2 VOBID 2 CELLID 1
- Rebuilding seg 3 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 4 VOBID 3 CELLID 1
- Rebuilding seg 5 VOBID 3 CELLID 2
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 6 VOBID 4 CELLID 1
- Rebuilding seg 7 VOBID 4 CELLID 2
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 8 VOBID 5 CELLID 1
- Rebuilding seg 9 VOBID 5 CELLID 2
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 10 VOBID 6 CELLID 1
- Rebuilding seg 11 VOBID 6 CELLID 2
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 12 VOBID 7 CELLID 1
- Rebuilding seg 13 VOBID 7 CELLID 2
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 14 VOBID 8 CELLID 1
- Rebuilding seg 15 VOBID 8 CELLID 2
- Updating NAVPACKS for VOBID_08
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
- Processing VTS_09
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_09_0.IFO
- Updating TMAP table...
- Processing VTS_10
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_10_0.IFO
- Updating TMAP table...
- Processing VTS_11
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_11_0.IFO
- Updating TMAP table...
- Processing VTS_12
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_12_0.IFO
- Updating TMAP table...
- Processing VTS_13
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_13_0.IFO
- Updating TMAP table...
- Processing VTS_14
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_14_0.IFO
- Updating TMAP table...
- Processing VTS_15
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_15_0.IFO
- Updating TMAP table...
- Processing VTS_16
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_16_0.IFO
- Updating TMAP table...
- Processing VTS_17
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_17_0.IFO
- Updating TMAP table...
- Processing VTS_18
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_18_0.IFO
- Updating TMAP table...
- Processing VTS_19
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_19_0.IFO
- Updating TMAP table...
- Processing VTS_20
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_20_0.IFO
- Updating TMAP table...
- Processing VTS_89
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_89_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- There appears to have been an ISO write error.
- ISO Image WAS NOT successfully created.
- DVD Files WERE NOT removed.
[22:19:18] Phase III, REBUILD completed in 11 minutes.

Done.
[22:19:18] PREPARE/ENCODE/REBUILD completed in 133 min.

Any idea what is causing this?

blutach

21st March 2007, 07:07

Apart from the error message, (which I know jdobbs will be anxious to get to the bottom of), I have seen that movie and menus of this disk is about 3.5Gb (this from a RipIt4Me M+M rip). I guess I am asking, why bother? (DVD Rebuilder (http://dvd-rb.dvd2go.org/) did tell you there was no need to re-encode).

On the ISO write error, another thread discussing why PgcEdit failed to create an ISO (see here (http://forum.doom9.org/showthread.php?t=123487) and here (http://forum.digital-digest.com/showthread.php?postid=514494#post514494)), found that it failed to create an ISO properly when a title was missing in a VTS. There is another thread running in this subforum about the TT_SRPT table.

You might like to open the final DVDFILES output in PgcEdit and see if every VTS has at least 1 title associated with it. If not, mkisofs (or whatever jdobbs is using to build the ISO) will fail.

Regards

jdobbs

21st March 2007, 10:32

I'll pick up "Rocky Balboa" today and give it a test run.

rack04

21st March 2007, 12:44

You might like to open the final DVDFILES output in PgcEdit and see if every VTS has at least 1 title associated with it. If not, mkisofs (or whatever jdobbs is using to build the ISO) will fail.

Here are the error messages I get when I open the DVDFILES in PgcEdit.

http://i11.photobucket.com/albums/a199/rack04/1.jpg

http://i11.photobucket.com/albums/a199/rack04/2.jpg

blutach

21st March 2007, 13:26

If your ripped files didn't exhibit this behaviour in PgcEdit, it's a fair bet the new routines jdobbs implemented need a bit of tweaking.

A short term solution is to run your rip thru PgcEdit and call the "Delete uncalled PGCs" function. This will clean your project up incredibly and remove unreferenced VTSs, while keeping a perfect structure. And encode after that should see you right.

Alternatively, v1.22 shouldn't damage the structure.

Regards

rack04

21st March 2007, 14:00

setarip_old

21st March 2007, 19:27

@rack04

Hi!

As mentioned previously, if you use RipIt4Me in "Movie plus menu" mode, the resultant rip will be directly small enough to fit on a DVD5 - and there'll be nothing to be gained by further processing with DVD Rebuilder.

You can then use IMGBurn (in "Build" mode) to burn the DVD "package" (.IFOs, .BUPs, .VOBs) created by RipIt4Me...

blutach

21st March 2007, 22:16

Actually I took your advice and re-ripped using RipIt4Me in "Movie+Menu" only mode. I tried using PgcEdit's "Delete uncalled PGCs" function but aborted when it warned that I need to manually fix PGC pointers. I knew that this was over my head so I aborted.Well, that's strange - sounds like the rip is not 100% compliant. But let PgcEdit fix what it wants and finish.

Regards

jdobbs

21st March 2007, 23:01

I think I know what's causing the error. When I wrote the new code I failed to account for the possibility that an unreferenced VTS might fall in the middle of several legitimate VTSs. I thought it was very unlikely and didn't occur on any of the tests I'd run. Based on the IFOs I've received it obviously it wasn't as unlikely as I'd thought.

It only happens on a few new discs that have this goofy anomaly (it just gets weirder every day, doesn't it?) ... sigh...

If you run into this issure, I'd suggest you add this line to the "[Options]" area of REBUILDER.INI:

DISABLE_COMMAND_REFERENCE_CHECK=1

That should get it working -- if not you may need to run FixVTS or rip with RipIt4Me.

In the meantime, I'll write some code to account for yet another case of structural goofiness... there doesn't seem to be any end to these things.

rack04

21st March 2007, 23:14

rack04

22nd March 2007, 00:07

Well, that's strange - sounds like the rip is not 100% compliant. But let PgcEdit fix what it wants and finish.

Regards

http://i11.photobucket.com/albums/a199/rack04/untitled-5.jpg

blutach,

This is the message I was refering to when I said I tried using PgcEdit's "Delete uncalled PGCs" function. I aborted at this step because I knew I didn't know how to manually fix the commands.

blutach

22nd March 2007, 02:28

Say yes. That does not indicate lack of compliance.

Regards

jdobbs

22nd March 2007, 12:29

Hmmm... "Rocky Balboa" doesn't seem to be related to the condition I mentioned above. Has anyone successfully backed up this title? I can do it by massaging it by hand... but that's not a good solution.

blutach

22nd March 2007, 12:37

@jdobbs - from what I have seen, VTS 89 is indeed referenced (the root menu is entered from VMGM 1 and it jumps quickly back). So, it would be a case of a referenced VTS at the end of a whole lotta unreffed ones (VTS 20-88 are unreferenced). The video in VTS 89 is truly junk, however, as the title is never reached.

Regards

rack04

22nd March 2007, 12:40

I'm running another test encode using DVD Rebuilder. One thing I have noticed is that with this encode I now have VTS_20 and VTS_21 instead of VTS_20 and VTS_89. I don't know if this is due to running the RipIt4me output through PgcEdit "Delete uncalled PGCs" function or using the newest beta version of RipIt4Me. I'll report back this evening when I get home.

jdobbs

22nd March 2007, 13:09

The problem in this one is caused by the fact that the "Title Set Starting Sector" for VTS_89 gets set to zero in the VIDEO_TS.IFO's SRPT table. I'm looking into how that happens.

Now that I think about it -- it actually is related to the condition I'd mentioned above...

Scumbag Mark

24th March 2007, 02:15

If you run into this issure, I'd suggest you add this line to the "[Options]" area of REBUILDER.INI:

DISABLE_COMMAND_REFERENCE_CHECK=1
I experienced the same problem with INCONVENIENTTRUTH_UK.
That option fixed the problem. Thankyou.

jdobbs

24th March 2007, 02:29

Hopefully I'll have another version finished for tomorrow. I really need to do some testing first before sending it out though...

SpazzHH

24th March 2007, 16:36

@jdobbs

Whatever new problems were introduced in 1.23.1 may not just be limited to the so far discussed problems. FYI, while trying to back up Wondrous Oblivion-R1 I noticed that 1.23.1 wouldn't recognize VTS 2(603 MB). 1.22 had no problems.
I entered the line "DISABLE_COMMAND_REFERENCE_CHECK=1" into 1.23.1 Rebuilder ini file, and it fixed the problem. There is no real copy protection on this disc.
I'm sure the problem is related somehow, but thought you might want to know.

Spazz

jdobbs

24th March 2007, 17:52

Hmmm... I'll see if I can find that disc and give it a test run. Any chance you could send the original VIDEO_TS.IFO file to dvd-rb@dvd-rb.com so I can take a quick look at it?

Are you positive VTS_02 is referenced?

SpazzHH

24th March 2007, 18:12

I'll send the file ASAP.
Yes the file is referenced. 1.22 has no problem with it. It even shows up in 1.23 after adding the line to the ini file.

P.S. - file sent

jdobbs

24th March 2007, 18:40

That may not necessarily mean it's referenced. The new routines pick up non-referenced material more reliably.

SpazzHH

24th March 2007, 18:49

I'll take your word for it, you know a lot more than me, but the old routines are picking it up, it's the new ones that aren't. This VTS contains all the Extras on the DVD.

P.S. - New file sent.

jdobbs

24th March 2007, 19:48

You say it contains all the extras? Interesting... It didn't look like it was referenced when I first looked at the IFO. I'll look at it again.

jdobbs

24th March 2007, 20:07

@SpazzH

Have you edited this title at all? I'm looking through the VIDEO_TS.IFO and I can't see any method through which control ever gets transferred to VTS_02... of course I guess I could be missing something.

SpazzHH

24th March 2007, 20:15

No editing at all. As a matter of fact, the files I sent were copied straight off the Disc.

jdobbs

24th March 2007, 20:27

Ok... time to go out and find the disc.

Thanks.

jdobbs

24th March 2007, 23:01

No luck with "Wondrous Oblivion". I tried Best Buy, Circuit City, Blockbuster, Hollywood Video, Borders, and Suncoast... looks like this one is going to have to be ordered online -- so it may be a while before I can look at it.

SpazzHH

24th March 2007, 23:40

Hate to hear that. It's a Palm Pictures release I picked up at Hollywood Video.

blutach

25th March 2007, 00:43

@jdobbs - it may be referenced thru a menu in VIDEO_TS.VOB (as oppsoed to the more conventional commands in the IFO).

@SpazzHH - try ripping the disk with RipIt4Me and posting the buttoninfo.txt file

Regards

jdobbs

25th March 2007, 00:59

I'm definitely confused on this one. I'm holding the release of v1.23.2 until I figure this out. This "finding and adjusting for unreferenced" is turning out to be a lot more of a pain than I first anticipated.

Oh, well. I'll start looking through the code for scanning the NAVPACKS -- I should have thought of that...

SpazzHH

25th March 2007, 02:07

@jdobbs - it may be referenced thru a menu in VIDEO_TS.VOB (as oppsoed to the more conventional commands in the IFO).

Regards

Absolutely correct. The movie menu on this disc is in VIDEO_TS.VOB. The menu VOB for VTS_01(The main movie) is just adverts and such. Neither VTS 2 or 3 have any menu VOB's.

jdobbs

25th March 2007, 02:14

Ok. I think I know what's going on now... but I'm burned out for today. I'll work on it in the morning. :)

SpazzHH

25th March 2007, 02:24

That's more than fine. Almost sorry to have had to bring this up, but I know it's for the best. Here's the log Blu asked for, hope it helps.
0 1 2 1 4
[71 04 00 07 00 00 00 0a] 149 204 199 53 4 2 4 2 0 1: Set gprm(7) mov 0 and Link PGC 10
[71 04 00 00 00 01 00 04] 147 260 227 55 1 3 1 3 0 2: Set gprm(0) mov 1 and Link PGC 4
[71 04 00 0a 04 00 00 05] 144 317 206 47 2 4 2 4 0 3: Set gprm(10) mov 1024 and Link PGC 5
[20 04 00 00 00 00 00 06] 137 366 249 62 3 1 3 1 0 4: Link PGC 6
0 1 3 1 4
[71 04 00 07 00 00 00 0a] 149 204 199 53 4 2 4 2 0 1: Set gprm(7) mov 0 and Link PGC 10
[71 04 00 00 00 01 00 04] 147 260 227 55 1 3 1 3 0 2: Set gprm(0) mov 1 and Link PGC 4
[71 04 00 0a 04 00 00 05] 144 317 206 47 2 4 2 4 0 3: Set gprm(10) mov 1024 and Link PGC 5
[20 04 00 00 00 00 00 06] 137 366 249 62 3 1 3 1 0 4: Link PGC 6
0 1 4 1 9
[71 04 00 07 00 01 00 0c] 157 94 134 124 7 4 9 2 0 1: Set gprm(7) mov 1 and Link PGC 12
[71 04 00 07 00 02 00 0c] 298 94 131 127 8 5 1 3 0 2: Set gprm(7) mov 2 and Link PGC 12
[71 04 00 07 00 03 00 0c] 433 92 131 142 9 6 2 4 0 3: Set gprm(7) mov 3 and Link PGC 12
[71 04 00 07 00 04 00 0c] 159 229 133 131 1 7 3 5 0 4: Set gprm(7) mov 4 and Link PGC 12
[71 04 00 07 00 05 00 0c] 295 231 134 144 2 8 4 6 0 5: Set gprm(7) mov 5 and Link PGC 12
[71 04 00 07 00 06 00 0c] 435 234 137 125 3 9 5 7 0 6: Set gprm(7) mov 6 and Link PGC 12
[71 04 00 08 08 00 00 03] 168 380 150 37 4 1 6 8 0 7: Set gprm(8) mov 2048 and Link PGC 3
[20 07 00 00 00 00 04 02] 351 381 76 39 5 2 7 9 0 8: LinkCN Cell 2, button 1
[20 07 00 00 00 00 04 03] 440 381 97 37 6 3 8 1 0 9: LinkCN Cell 3, button 1
0 1 4 2 9
[71 04 00 07 00 07 00 0c] 157 94 134 124 7 4 9 2 0 1: Set gprm(7) mov 7 and Link PGC 12
[71 04 00 07 00 08 00 0c] 298 94 131 127 8 5 1 3 0 2: Set gprm(7) mov 8 and Link PGC 12
[71 04 00 07 00 09 00 0c] 433 92 131 142 9 6 2 4 0 3: Set gprm(7) mov 9 and Link PGC 12
[71 04 00 07 00 0a 00 0c] 159 229 133 131 1 7 3 5 0 4: Set gprm(7) mov 10 and Link PGC 12
[71 04 00 07 00 0b 00 0c] 295 231 134 144 2 8 4 6 0 5: Set gprm(7) mov 11 and Link PGC 12
[71 04 00 07 00 0c 00 0c] 435 234 137 125 3 9 5 7 0 6: Set gprm(7) mov 12 and Link PGC 12
[71 04 00 08 08 00 00 03] 168 380 150 37 4 1 6 8 0 7: Set gprm(8) mov 2048 and Link PGC 3
[20 07 00 00 00 00 04 01] 351 381 76 39 5 2 7 9 0 8: LinkCN Cell 1, button 1
[20 07 00 00 00 00 04 03] 440 381 97 37 6 3 8 1 0 9: LinkCN Cell 3, button 1
0 1 4 3 9
[71 04 00 07 00 0d 00 0c] 157 94 134 124 7 4 9 2 0 1: Set gprm(7) mov 13 and Link PGC 12
[71 04 00 07 00 0e 00 0c] 298 94 131 127 8 5 1 3 0 2: Set gprm(7) mov 14 and Link PGC 12
[71 04 00 07 00 0f 00 0c] 433 92 131 142 9 6 2 4 0 3: Set gprm(7) mov 15 and Link PGC 12
[71 04 00 07 00 10 00 0c] 159 229 133 131 1 7 3 5 0 4: Set gprm(7) mov 16 and Link PGC 12
[71 04 00 07 00 11 00 0c] 295 231 134 144 2 8 4 6 0 5: Set gprm(7) mov 17 and Link PGC 12
[71 04 00 07 00 12 00 0c] 435 234 137 125 3 9 5 7 0 6: Set gprm(7) mov 18 and Link PGC 12
[71 04 00 08 08 00 00 03] 168 380 150 37 4 1 6 8 0 7: Set gprm(8) mov 2048 and Link PGC 3
[20 07 00 00 00 00 04 01] 351 381 76 39 5 2 7 9 0 8: LinkCN Cell 1, button 1
[20 07 00 00 00 00 04 02] 440 381 97 37 6 3 8 1 0 9: LinkCN Cell 2, button 1
0 1 5 1 4
[30 02 00 00 00 02 00 00] 131 124 285 84 4 2 4 2 0 1: JumpTT Jump to title 2
[30 02 00 00 00 03 00 00] 134 227 258 44 1 3 1 3 0 2: JumpTT Jump to title 3
[30 02 00 00 00 04 00 00] 132 292 259 54 2 4 2 4 0 3: JumpTT Jump to title 4
[71 04 00 08 0c 00 00 03] 131 390 232 55 3 1 3 1 0 4: Set gprm(8) mov 3072 and Link PGC 3
0 1 6 1 6
[71 01 00 00 00 0a 04 0d] 117 95 212 60 6 2 6 2 0 1: Set gprm(0) mov 10 and LinkTailPGC, button 1
[71 01 00 00 00 0b 04 0d] 132 165 242 59 1 4 1 3 0 2: Set gprm(0) mov 11 and LinkTailPGC, button 1
[71 01 00 00 00 0c 04 0d] 146 309 56 37 2 5 2 4 0 3: Set gprm(0) mov 12 and LinkTailPGC, button 1
[71 01 00 00 00 0d 04 0d] 202 309 83 39 2 5 3 5 0 4: Set gprm(0) mov 13 and LinkTailPGC, button 1
[20 04 00 00 00 00 00 0b] 152 379 113 28 4 6 4 6 0 5: Link PGC 11
[71 04 00 08 10 00 00 03] 152 407 164 27 5 1 5 1 0 6: Set gprm(8) mov 4096 and Link PGC 3
0 1 9 1 1
[20 04 00 00 00 00 00 01] 109 384 215 57 1 1 1 1 0 1: Link PGC 1

Spazz

blutach

25th March 2007, 02:54

I presume titles 2-4 are the extras and are therefore referenced.

Regards

jdobbs

25th March 2007, 04:46

Titles 2 & 3 are both in VTS_02 -- so, yep, there's the reference...

James35

25th March 2007, 09:59

SpazzHH

25th March 2007, 11:05

VTS_01 - Title 1 (Main Movie)
VTS_02 - Titles 2 & 3 (Making of.. and theatrical trailer)
VTS_03 - Title 4 (Preview)
VTS_04 - Title 5 (Preview)

VIDEO_TS.VOB - Movie Menu and warning screens
VTS_01_0.VOB - Palm Pictures Logo and One.org Promo

jdobbs

25th March 2007, 13:55

@All

I've uploaded a new version (v1.23.2) for testing. Can you please try and see if it fixes the reported problems? You can download it from this link. (http://www.jdobbs.com/4650-5006-3790-4761-9251-5444/DVD-RB_v1.232Pro.exe) Please make sure "DISABLE_COMMAND_REFERENCE_CHECK" is removed from the REBUILDER.INI file if you've added it.

Please let me know if it corrects the reported issues. If it does I will send it out to all VIPs today.

@SpazzHH & James35

I'd be particularly interested in ensuring the problem you reported has been corrected since I haven't been able to get my hands on that DVD as yet.

Thanks.

SpazzHH

25th March 2007, 14:13

That seems to have done the trick.:)
I removed the extra line in the .ini file, put the disc in the drive and RB saw the previously missing VTS.

Thanks !!!

I'll try out a full rebuild, but There shouldn't be any problems with that. The older versions of RB did the disc just fine.

jdobbs

25th March 2007, 14:17

Great news. Thanks for the report and all the help in finding it. :)

James35

25th March 2007, 14:46

Yes it now works fine, Thanks jdobbs

rack04

25th March 2007, 15:28

jdobbs,

The issue I had with "Rocky Balboa" seemed to be releated to the rip. With the latest RipIt4Me and the "Delete uncalled PGCs" function in PgcEdit everthing work great. Thanks.

jdobbs

25th March 2007, 15:32

If you rip with RipIt4Me, it will clean up the unreferenced VTSs itself so DVD-RB won't have to. The main reason I added the routines to DVD-RB is so it will also work with AnyDVD and DVDFab Decrypter.