DVD Rebuilder + ILVU / angle movie - big problem!

[kabster]

I try to backup american gangster wich is an multi angle movie "several" times btw in several ways. But some "EXACT SAME" scenes at the exact same timeframe keep playing in loops= repeating themselves!!!

Just to make clear its not the source from the movie thats at stake, ive managed succesfully to re-encode or rather transcode the movie through either DVDshrink as through RECODE3 (nero) aswell whitout any playback problems afterwards !!

The problem persists in dvd-rb 1.27 aswell as in 1.28.2 !!

This is the movie its logfile:

[03:01:22] Phase I, PREPARATION started.
- DVD-RB v1.28.2
- AVISYNTH 2.5.6.0
- CCE 2.70.2.12 encoder selected.
- Source: AMERICAN GANGSTER REMAKE
- VTS_01: 3.784.599 sectors.
-- ANGLE and/or INTERLEAVING is present.
-- Scanning and writing .D2V & .AVS files
- Processed 70,2MB ILVU section...
- Processed 79,3MB ILVU section...
- Processed 29,1MB ILVU section...
- Processed 137,1MB ILVU section...
- Processed 178,3MB ILVU section...
- Processed 113,4MB ILVU section...
- Processed 74,1MB ILVU section...
- Processed 34,2MB ILVU section...
- Processed 55,0MB ILVU section...
- Processed 165,0MB ILVU section...
- Processed 95,4MB ILVU section...
- Processed 80,7MB ILVU section...
- Processed 160,8MB ILVU section...
-- Processed 264.156 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 60,3%
- Overall Bitrate : 2.910Kbs
- Space for Video : 3.753.404KB
- Redistributing using Base_Q: 35
- HIGH/LOW/TYPICAL Bitrates: 4.497/965/2.910 Kbs
[03:13:11] Phase I, PREPARATION completed in 12 minutes.
[03:13:11] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
- Creating M2V for VTS_01 segment 43
- Creating M2V for VTS_01 segment 44
- Creating M2V for VTS_01 segment 45
- Creating M2V for VTS_01 segment 46
- Creating M2V for VTS_01 segment 47
- Creating M2V for VTS_01 segment 48
- Creating M2V for VTS_01 segment 49
- Creating M2V for VTS_01 segment 50
- Creating M2V for VTS_01 segment 51
- Creating M2V for VTS_01 segment 52
- Creating M2V for VTS_01 segment 53
- Creating M2V for VTS_01 segment 54
- Creating M2V for VTS_01 segment 55
- Creating M2V for VTS_01 segment 56
- Creating M2V for VTS_01 segment 57
- Creating M2V for VTS_01 segment 58
- Creating M2V for VTS_01 segment 59
- Creating M2V for VTS_01 segment 60
- Creating M2V for VTS_01 segment 61
- Creating M2V for VTS_01 segment 62
- Creating M2V for VTS_01 segment 63
- Creating M2V for VTS_01 segment 64
- Creating M2V for VTS_01 segment 65
- Creating M2V for VTS_01 segment 66
- Creating M2V for VTS_01 segment 67
- Creating M2V for VTS_01 segment 68
- Creating M2V for VTS_01 segment 69
- Creating M2V for VTS_01 segment 70
- Creating M2V for VTS_01 segment 71
- Creating M2V for VTS_01 segment 72
- Creating M2V for VTS_01 segment 73
[06:16:31] Phase II ENCODING completed in 183 minutes.
[06:16:31] 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
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Processed 70,2MB ILVU section...
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 4 VOBID 2 CELLID 1
- Rebuilding seg 5 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 6 VOBID 4 CELLID 1
- Rebuilding seg 7 VOBID 4 CELLID 2
- Rebuilding seg 8 VOBID 4 CELLID 3
- Rebuilding seg 9 VOBID 4 CELLID 4
- Rebuilding seg 10 VOBID 4 CELLID 5
- Rebuilding seg 11 VOBID 4 CELLID 6
- Rebuilding seg 12 VOBID 4 CELLID 7
- Processed 79,3MB ILVU section...
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 13 VOBID 5 CELLID 1
- Rebuilding seg 14 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_05
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 15 VOBID 7 CELLID 1
- Rebuilding seg 16 VOBID 7 CELLID 2
- Processed 29,1MB ILVU section...
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 17 VOBID 8 CELLID 1
- Rebuilding seg 18 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_08
- Updating NAVPACKS for VOBID_09
- Rebuilding seg 19 VOBID 10 CELLID 1
- Rebuilding seg 20 VOBID 10 CELLID 2
- Rebuilding seg 21 VOBID 10 CELLID 3
- Processed 137,1MB ILVU section...
- Updating NAVPACKS for VOBID_10
- Rebuilding seg 22 VOBID 11 CELLID 1
- Rebuilding seg 23 VOBID 12 CELLID 1
- Updating NAVPACKS for VOBID_11
- Updating NAVPACKS for VOBID_12
- Rebuilding seg 24 VOBID 13 CELLID 1
- Processed 178,3MB ILVU section...
- Updating NAVPACKS for VOBID_13
- Rebuilding seg 25 VOBID 14 CELLID 1
- Rebuilding seg 26 VOBID 15 CELLID 1
- Updating NAVPACKS for VOBID_14
- Updating NAVPACKS for VOBID_15
- Rebuilding seg 27 VOBID 16 CELLID 1
- Processed 113,4MB ILVU section...
- Updating NAVPACKS for VOBID_16
- Rebuilding seg 28 VOBID 17 CELLID 1
- Rebuilding seg 29 VOBID 18 CELLID 1
- Updating NAVPACKS for VOBID_17
- Updating NAVPACKS for VOBID_18
- Rebuilding seg 30 VOBID 19 CELLID 1
- Processed 74,1MB ILVU section...
- Updating NAVPACKS for VOBID_19
- Rebuilding seg 31 VOBID 20 CELLID 1
- Rebuilding seg 32 VOBID 20 CELLID 2
- Rebuilding seg 33 VOBID 21 CELLID 1
- Rebuilding seg 34 VOBID 21 CELLID 2
- Updating NAVPACKS for VOBID_20
- Updating NAVPACKS for VOBID_21
- Rebuilding seg 35 VOBID 22 CELLID 1
- Rebuilding seg 36 VOBID 22 CELLID 2
- Updating NAVPACKS for VOBID_22
- Rebuilding seg 37 VOBID 23 CELLID 1
- Rebuilding seg 38 VOBID 23 CELLID 2
- Rebuilding seg 39 VOBID 23 CELLID 3
- Rebuilding seg 40 VOBID 23 CELLID 4
- Processed 34,2MB ILVU section...
- Updating NAVPACKS for VOBID_23
- Rebuilding seg 41 VOBID 24 CELLID 1
- Rebuilding seg 42 VOBID 25 CELLID 1
- Updating NAVPACKS for VOBID_24
- Updating NAVPACKS for VOBID_25
- Rebuilding seg 43 VOBID 26 CELLID 1
- Processed 55,0MB ILVU section...
- Updating NAVPACKS for VOBID_26
- Rebuilding seg 44 VOBID 27 CELLID 1
- Rebuilding seg 45 VOBID 27 CELLID 2
- Rebuilding seg 46 VOBID 28 CELLID 1
- Rebuilding seg 47 VOBID 28 CELLID 2
- Updating NAVPACKS for VOBID_27
- Updating NAVPACKS for VOBID_28
- Rebuilding seg 48 VOBID 29 CELLID 1
- Processed 165,0MB ILVU section...
- Updating NAVPACKS for VOBID_29
- Rebuilding seg 49 VOBID 30 CELLID 1
- Rebuilding seg 50 VOBID 31 CELLID 1
- Updating NAVPACKS for VOBID_30
- Updating NAVPACKS for VOBID_31
- Rebuilding seg 51 VOBID 32 CELLID 1
- Processed 95,4MB ILVU section...
- Updating NAVPACKS for VOBID_32
- Rebuilding seg 52 VOBID 33 CELLID 1
- Rebuilding seg 53 VOBID 34 CELLID 1
- Updating NAVPACKS for VOBID_33
- Updating NAVPACKS for VOBID_34
- Rebuilding seg 54 VOBID 35 CELLID 1
- Rebuilding seg 55 VOBID 35 CELLID 2
- Processed 80,7MB ILVU section...
- Updating NAVPACKS for VOBID_35
- Rebuilding seg 56 VOBID 36 CELLID 1
- Rebuilding seg 57 VOBID 37 CELLID 1
- Updating NAVPACKS for VOBID_36
- Updating NAVPACKS for VOBID_37
- Rebuilding seg 58 VOBID 38 CELLID 1
- Rebuilding seg 59 VOBID 38 CELLID 2
- Rebuilding seg 60 VOBID 38 CELLID 3
- Rebuilding seg 61 VOBID 38 CELLID 4
- Rebuilding seg 62 VOBID 38 CELLID 5
- Rebuilding seg 63 VOBID 38 CELLID 6
- Rebuilding seg 64 VOBID 38 CELLID 7
- Rebuilding seg 65 VOBID 38 CELLID 8
- Rebuilding seg 66 VOBID 38 CELLID 9
- Processed 160,8MB ILVU section...
- Updating NAVPACKS for VOBID_38
- Rebuilding seg 67 VOBID 39 CELLID 1
- Rebuilding seg 68 VOBID 39 CELLID 2
- Rebuilding seg 69 VOBID 40 CELLID 1
- Rebuilding seg 70 VOBID 40 CELLID 2
- Updating NAVPACKS for VOBID_39
- Updating NAVPACKS for VOBID_40
- Rebuilding seg 71 VOBID 41 CELLID 1
- Rebuilding seg 72 VOBID 41 CELLID 2
- Rebuilding seg 73 VOBID 41 CELLID 3
- Updating NAVPACKS for VOBID_41
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[06:30:27] Phase III, REBUILD completed in 14 minutes.

Done.
[06:30:28] PREPARE/ENCODE/REBUILD completed in 209 min.

currently iam only able to backup that movie succesfully using either dvdshrink or Re-encode3 !!

kabster,

[jdobbs]

Any editing beforehand?

Have you tried it without redistribution?

Any

[kabster]

Any editing beforehand?

Have you tried it without redistribution?

Any

@jdobs,

Frankly, i have edited it yes, just like i edited many other sources aswell!

But just this movie gives me problems!!
I think ive processed this movie whitout redistribution aswell (iam not sure)!

Also, why does editing before hand has anything to do whit it?

Ive edited most of my movies before i process them through rebuilder to save space, even on some multi-angled movies like Blade serries.
Havent had a problem whit those.
Just now and then, rebuilder gives me problems whit certain movies!!
If editing woud cause those problems, woudnt i always have problems then either through the re-encode process or by watching the movie ?
Or are you saying , that editing "may" cause randomly problems whit video sources!!
If thats the cause , why is it dvdshrink nor re-encode give me such an problems!?

Just thinking loudout, because iam using for years this same program for editing my movies !!?
Also, if it where because of editing that movie..
Why dont i see those verry same scenes playing in loops i watch from the source video (the original source "no re-encode")
Ive watched/checked both angles from that edited source... And i couldnt find any problems regarding playback !!!!!!


Thanks anyway jdobbs,

kabster,

[rendez2k]

Editing before hand can screw up DVDs! How do you know that you're editing software hasn't introduced an error?

Test without editing first and see if you still have the problem before blaming DVD-RB!

[jdobbs]

Especially with ILVU... which is why I asked.

I'll pick this one up and run it (NTSC version) just to be sure. But I suspect it will work ok.

[dialysis1]

DVD-RB has no problems with the R1 version of this movie.

[kabster]

Editing before hand can screw up DVDs! How do you know that you're editing software hasn't introduced an error?

Test without editing first and see if you still have the problem before blaming DVD-RB!

Again, i dont seem to have any PLAYBACK problems wotsoever watching that verry same "EDITED" movie either through Windvd 7 or on my stand alone..
I actually have wasted an DL+R to see if its really an editing issue or not..

But even DL+R verbatim plays outstanding!!

Especially with ILVU... which is why I asked.

I'll pick this one up and run it (NTSC version) just to be sure. But I suspect it will work ok.

Just my luck!! The movie in question is an PAL=Region 2= 25fps = 50hz !!


I guess ill have to live whit it!!


kabster,

[kabster]

@bluetach

I like to know why you had to "clean up log presentation" !!?

Just noticed youve edited an post of mine !!?

edit: nevermind me asking , i think i know wot you did and for the right reason ;)


kabster,