The Matrix Backup

[maxse]

Hi guys. Well now I am trying to backup 'The Matrix' and the bitrate is always rediculously low, unless I do movie only. I just want to keep the menu and the movie...

I used VOB Blanker to blank out the extras (didnt process the main movie VTS because it has angles so vobblanker just skipped it) which got it to a reasonable size of below 5.6 gigs or somewhere close to that. So now when I open it in DVD-RB, DVD-RB only sees the main movie and no menus or anything. ITs as if I selected "movie-only" and when I go fomr "movie-only" to "Full Backup" there is no change, it does not detect the other stuff. Can someone please give me some advice on it, and what I can do to get this movie and movies like this to fit by jus tkeeping the menu. It seems that if I do menus and movie only in DVD-RB the bitrate is still pretty low...

HKT suggested in my Nemo thread to use VOB Blanker which worked fine because I didnt have to use DVD-RB since the size would be perfect, but this is a problem for the Matrix. Any help would be really appreciated. Thanks guys.

*EDIT*
If I chose MOVIE and MENU in DVD-RB I get this:

- Reduction Level for DVD-5: 58.2%
- Overall Bitrate : 2,941/2,353Kbs
- Space for Video : 3,868,702KB
- Blanking all EXTRA Segments
-- Feature before/after: 3,738 / 3,738 Kbs

Now is my bitrate 3.7 or 2.9? I dont get the part that says feature before/after since they are the same values....

[Rippraff]

Hi,So now when I open it in DVD-RB, DVD-RB only sees the main movie and no menus or anything. ITs as if I selected "movie-only" and when I go fomr "movie-only" to "Full Backup" there is no change, it does not detect the other stuff.
what do you expect? ;)
Of course if you blank the extras in front of RB with Vobblanker there isn't anything left to be detect except the main movie.
As RB leaves menus untouched you can't see them but they'll exist in your backup unless you choose "Movie only".
By the way there's also the possibility to blank things inside RB after prepare phase with "Video Segment Editor".
My recommendation is always use fullbackup mode if you blank things in front of RB as you did.

If I chose MOVIE and MENU in DVD-RB I get this:

- Reduction Level for DVD-5: 58.2%
- Overall Bitrate : 2,941/2,353Kbs
- Space for Video : 3,868,702KB
- Blanking all EXTRA Segments
-- Feature before/after: 3,738 / 3,738 Kbs

Now is my bitrate 3.7 or 2.9? I dont get the part that says feature before/after since they are the same values....
Sorry to say but there must be something wrong. Are you sure you opened the Vobblanker result instead of the original? If there's only 5.6 GB left reduction level can't be 58.2%

Edit: And another thing, if there's a DTS audio stream on the DVD, uncheck it, because it needs a lot of space. Take the AC3 stream instead.

Cu Rippraff

[maxse]

I guess I wrote it confusingly. What I posted is the original one not VOBBlanked one. I check the option to blank extras inside DVD-RB so I just want to know if this is the same as using VOBBlanker?

Also I was confused about which bitrate I Was actually getting because I didnt understna dif it was 3.7 after DVD-RB blanked the extras or if its just 2.9?

[maxse]

so does can any1 help me out please and tell me according to the above what is my real bitrate for the movie?

[Rippraff]

By the way, maxse, this forum has a search function. ;) This (http://forum.doom9.org/showthread.php?p=720063#post720063) is one result. :)

And if you can't see any extras for blanking then you probably have a lot of VTS which are less than 50 MB?
If so, open your Rebuilder.ini copy and paste the following line under [Options]
vts_min_size=0

Cu Rippraff

[maxse]

Thanks ripraff again. I did search and found that but its a little confusing so I just wanted to make sure.

Because the Feature Before/After values are the same so how can that be? Because the feature before it says 2.9!!
SO Im still not sure. In this case what is my final bitrate?

Also I am using PGCEdit right now to get rid of the buttons but it is not working! For some reason, when I go to scene selection and then back to menu I can still select the "extras" even though disabled them in pgcedit. Any clue as to why this is happening? Thanks so much ripraff you are a great help.

[Rippraff]

Because the Feature Before/After values are the same so how can that be?
As you said, there are no extras to be seen so RB can't blank them. If I understand this correctly, you're right, it's a little bit confusing.

Also I am using PGCEdit right now to get rid of the buttons but it is not working! For some reason, when I go to scene selection and then back to menu I can still select the "extras" even though disabled them in pgcedit. Any clue as to why this is happening?
You often have more than one screen with button selection in a DVD menu.
In PgcEdit look for all entries in the left frame which say 2, 3, 4... b. and check them with the green Menu icon on top. If you have more buttons shown in the left frame than can be seen in the preview, click on the rectangle "VTSM..." on top in Menu buttons preview.

Cu Rippraff

[Rippraff]

Okay, I don't know how many times I've read your first post but I'm pretty sure now this is a big misunderstanding. :rolleyes:
You were talking about Vobblanker but as you said, you didn't use it. You were also talking about So now when I open it in DVD-RB, DVD-RB only sees the main movie and no menus or anything.
How do you find this out?
It would have been easier if you haven't cut your logfile:
- Reduction Level for DVD-5: 58.2%
- Overall Bitrate : 2,941/2,353Kbs
- Space for Video : 3,868,702KB
- Blanking all EXTRA Segments
-- Feature before/after: 3,738 / 3,738 Kbs

There must be other VTS beside the largest which represents your main movie.
To be frank I'm not dealing with movie only, movie and menu only mode just full backups.
But I've made a test now and can tell you how RB is working in movie and menu only mode: It checks all the VTS which are present, at the end of prepare it blanks the extras.
[21:27:04] Phase I, PREPARATION started.
- CCE SP 2.70.2.1 encoder selected.
- "Movie and Menus Only" mode is enabled.
- VTS_01: 3.121.003 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 165.097 frames.
-- Building .AVS and .ECL files
- VTS_04: 243.742 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 18.891 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 75,5%
- Overall Bitrate : 4.092Kbs
- Space for Video : 3.675.828KB
- Blanking all EXTRA Segments
-- Feature before/after: 4.583 / 4.583 Kbs

If I'ld have done a full backup the average bitrate would have been 4.092Kbs, as RB has blanked VTS 04 the final average bitrate is 4.583Kbs now. I can't tell why the values before/after are the same maybe jdobbs can answer this (I'm pretty sure he can ;))
=> 3,783 kbs is your final average bitrate after blanking the extras!

By the way I'm not sure if you haven't set vts_min_size=0 in your ini, what RB does with all VTS which are smaller than around 50 MB!? If you make a full backup mode these small VTS will be left untouched and copied to your backup folder. In movie and menu only mode I would expect them to be deleted but I'm unsure about this. Maybe jdobbs can point this out.

Cu Rippraff

[maxse]

Okay thaks ripraff. Here is th thing. FORGET ABOUT VOB BLANKER. If I just load the matrix into DVD-RB and select the option for menus and movie only and blank extras WITHIN DVD-RB. And for some reason I get such a low bitrate. I will find the log file right now, perhaps that will better help you help me! Thanks again.

*EDIT* Okay here is the log file:
[03:18:16] Phase I, PREPARATION started.
- CCE SP ECLCCE encoder selected.
- "Movie and Menus Only" mode is enabled.
- VTS_01: 315,295 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 41,292 frames.
-- Building .AVS and .ECL files
- VTS_02: 2,891,752 sectors.
-- ANGLE and/or INTERLEAVING is present.
-- Scanning and writing .D2V & .AVS files
- Processed 30.3MB ILVU section...
- Processed 14.9MB ILVU section...
- Processed 158.5MB ILVU section...
- Processed 15.8MB ILVU section...
- Processed 14.9MB ILVU section...
- Processed 18.5MB ILVU section...
- Processed 47.4MB ILVU section...
- Processed 18.8MB ILVU section...
- Processed 30.1MB ILVU section...
-- Processed 203,239 frames.
-- Building .AVS and .ECL files
- VTS_03: 593,326 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,445 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 58.2%
- Overall Bitrate : 2,941/2,353Kbs
- Space for Video : 3,868,702KB
- Blanking all EXTRA Segments
-- Feature before/after: 3,738 / 3,738 Kbs

[maxse]

[03:25:02] Phase I, PREPARATION completed in 7 minutes.
[03:25:02] 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_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Creating M2V for VTS_02 segment 3
- Creating M2V for VTS_02 segment 4
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Creating M2V for VTS_02 segment 7
- Creating M2V for VTS_02 segment 8
- Creating M2V for VTS_02 segment 9
- Creating M2V for VTS_02 segment 10
- Creating M2V for VTS_02 segment 11
- Creating M2V for VTS_02 segment 12
- Creating M2V for VTS_02 segment 13
- Creating M2V for VTS_02 segment 14
- Creating M2V for VTS_02 segment 15
- Creating M2V for VTS_02 segment 16
- Creating M2V for VTS_02 segment 17
- Creating M2V for VTS_02 segment 18
- Creating M2V for VTS_02 segment 19
- Creating M2V for VTS_02 segment 20
- Creating M2V for VTS_02 segment 21
- Creating M2V for VTS_02 segment 22
- Creating M2V for VTS_02 segment 23
- Creating M2V for VTS_02 segment 24
- Creating M2V for VTS_02 segment 25
- Creating M2V for VTS_02 segment 26
- Creating M2V for VTS_02 segment 27
- Creating M2V for VTS_02 segment 28
- Creating M2V for VTS_02 segment 29
- Creating M2V for VTS_02 segment 30
- Creating M2V for VTS_02 segment 31
- Creating M2V for VTS_02 segment 32
- Creating M2V for VTS_02 segment 33
- Creating M2V for VTS_02 segment 34
- Creating M2V for VTS_02 segment 35
- Creating M2V for VTS_02 segment 36
- Creating M2V for VTS_02 segment 37
- Creating M2V for VTS_02 segment 38
- Creating M2V for VTS_02 segment 39
- Creating M2V for VTS_02 segment 40
- Creating M2V for VTS_02 segment 41
- Creating M2V for VTS_02 segment 42
- Creating M2V for VTS_02 segment 43
- Creating M2V for VTS_02 segment 44
- Creating M2V for VTS_02 segment 45
- Creating M2V for VTS_02 segment 46
- Creating M2V for VTS_02 segment 47
- Creating M2V for VTS_02 segment 48
- Creating M2V for VTS_02 segment 49
- Creating M2V for VTS_02 segment 50
- Creating M2V for VTS_02 segment 51
- Creating M2V for VTS_02 segment 52
- Creating M2V for VTS_02 segment 53
- Creating M2V for VTS_02 segment 54
- Creating M2V for VTS_02 segment 55
- Creating M2V for VTS_02 segment 56
- Creating M2V for VTS_02 segment 57
- Creating M2V for VTS_02 segment 58
- Creating M2V for VTS_02 segment 59
- Creating M2V for VTS_02 segment 60
- Creating M2V for VTS_02 segment 61
- Creating M2V for VTS_02 segment 62
- Creating M2V for VTS_02 segment 63
- Creating M2V for VTS_02 segment 64
- Creating M2V for VTS_02 segment 65
- Creating M2V for VTS_02 segment 66
- Creating M2V for VTS_02 segment 67
- Creating M2V for VTS_02 segment 68
- Creating M2V for VTS_02 segment 69
- Creating M2V for VTS_02 segment 70
- Creating M2V for VTS_02 segment 71
- Creating M2V for VTS_02 segment 72
- Creating M2V for VTS_02 segment 73
- Creating M2V for VTS_02 segment 74
- Creating M2V for VTS_02 segment 75
- Creating M2V for VTS_02 segment 76
- Creating M2V for VTS_02 segment 77
- Creating M2V for VTS_02 segment 78
- Creating M2V for VTS_02 segment 79
- Creating M2V for VTS_02 segment 80
- Creating M2V for VTS_02 segment 81
- Creating M2V for VTS_02 segment 82
- Creating M2V for VTS_02 segment 83
- Creating M2V for VTS_02 segment 84
- Creating M2V for VTS_02 segment 85
- Creating M2V for VTS_02 segment 86
- Creating M2V for VTS_02 segment 87
- Creating M2V for VTS_02 segment 88
- Creating M2V for VTS_02 segment 89
- Creating M2V for VTS_02 segment 90
- Creating M2V for VTS_02 segment 91
- Creating M2V for VTS_02 segment 92
- Creating M2V for VTS_02 segment 93
- Creating M2V for VTS_02 segment 94
- Creating M2V for VTS_02 segment 95
- Creating M2V for VTS_02 segment 96
- Creating M2V for VTS_02 segment 97
- Creating M2V for VTS_02 segment 98
- Creating M2V for VTS_02 segment 99
- Creating M2V for VTS_02 segment 100
- Creating M2V for VTS_02 segment 101
- Creating M2V for VTS_02 segment 102
- Creating M2V for VTS_02 segment 103
- Creating M2V for VTS_02 segment 104
- Creating M2V for VTS_02 segment 105
- Creating M2V for VTS_02 segment 106
- Creating M2V for VTS_02 segment 107
- Creating M2V for VTS_02 segment 108
- Creating M2V for VTS_02 segment 109
- Creating M2V for VTS_02 segment 110
- Creating M2V for VTS_02 segment 111
- Creating M2V for VTS_02 segment 112
- Creating M2V for VTS_02 segment 113
- Creating M2V for VTS_02 segment 114
- Creating M2V for VTS_02 segment 115
- Creating M2V for VTS_02 segment 116
- Creating M2V for VTS_02 segment 117
- Creating M2V for VTS_02 segment 118
- Creating M2V for VTS_02 segment 119
- Creating M2V for VTS_02 segment 120
- Creating M2V for VTS_02 segment 121
- Creating M2V for VTS_02 segment 122
- Creating M2V for VTS_02 segment 123
- Creating M2V for VTS_02 segment 124
- Creating M2V for VTS_02 segment 125
- Extracting STILLS for VTS_02 segment 126
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Extracting STILLS for VTS_03 segment 3
[07:44:27] Phase II ENCODING completed in 259 minutes.

[maxse]

[07:44:27] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 4 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 5 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 6 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 7 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 8 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_09
- 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
- 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
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 4 VOBID 3 CELLID 1
- Processed 30.3MB ILVU section...
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 5 VOBID 4 CELLID 1
- Rebuilding seg 6 VOBID 4 CELLID 2
- Rebuilding seg 7 VOBID 5 CELLID 1
- Rebuilding seg 8 VOBID 5 CELLID 2
- Updating NAVPACKS for VOBID_04
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 9 VOBID 6 CELLID 1
- Rebuilding seg 10 VOBID 6 CELLID 2
- Rebuilding seg 11 VOBID 6 CELLID 3
- Rebuilding seg 12 VOBID 6 CELLID 4
- Rebuilding seg 13 VOBID 6 CELLID 5
- Rebuilding seg 14 VOBID 6 CELLID 6
- Rebuilding seg 15 VOBID 6 CELLID 7
- Rebuilding seg 16 VOBID 6 CELLID 8
- Rebuilding seg 17 VOBID 6 CELLID 9
- Rebuilding seg 18 VOBID 6 CELLID 10
- Rebuilding seg 19 VOBID 6 CELLID 11
- Rebuilding seg 20 VOBID 6 CELLID 12
- Rebuilding seg 21 VOBID 6 CELLID 13
- Rebuilding seg 22 VOBID 6 CELLID 14
- Rebuilding seg 23 VOBID 6 CELLID 15
- Rebuilding seg 24 VOBID 6 CELLID 16
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 25 VOBID 7 CELLID 1
- Processed 14.9MB ILVU section...
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 26 VOBID 8 CELLID 1
- Rebuilding seg 27 VOBID 8 CELLID 2
- Rebuilding seg 28 VOBID 9 CELLID 1
- Rebuilding seg 29 VOBID 9 CELLID 2
- Updating NAVPACKS for VOBID_08
- Updating NAVPACKS for VOBID_09
- Rebuilding seg 30 VOBID 10 CELLID 1
- Rebuilding seg 31 VOBID 10 CELLID 2
- Rebuilding seg 32 VOBID 10 CELLID 3
- Rebuilding seg 33 VOBID 10 CELLID 4
- Rebuilding seg 34 VOBID 10 CELLID 5
- Rebuilding seg 35 VOBID 10 CELLID 6
- Rebuilding seg 36 VOBID 10 CELLID 7
- Rebuilding seg 37 VOBID 10 CELLID 8
- Rebuilding seg 38 VOBID 10 CELLID 9
- Updating NAVPACKS for VOBID_10
- Rebuilding seg 39 VOBID 11 CELLID 1
- Processed 158.5MB ILVU section...
- Updating NAVPACKS for VOBID_11
- Rebuilding seg 40 VOBID 12 CELLID 1
- Rebuilding seg 41 VOBID 12 CELLID 2
- Rebuilding seg 42 VOBID 13 CELLID 1
- Rebuilding seg 43 VOBID 13 CELLID 2
- Updating NAVPACKS for VOBID_12
- Updating NAVPACKS for VOBID_13
- Rebuilding seg 44 VOBID 14 CELLID 1
- Rebuilding seg 45 VOBID 14 CELLID 2
- Rebuilding seg 46 VOBID 14 CELLID 3
- Rebuilding seg 47 VOBID 14 CELLID 4
- Rebuilding seg 48 VOBID 14 CELLID 5
- Rebuilding seg 49 VOBID 14 CELLID 6
- Rebuilding seg 50 VOBID 14 CELLID 7
- Rebuilding seg 51 VOBID 14 CELLID 8
- Rebuilding seg 52 VOBID 14 CELLID 9
- Rebuilding seg 53 VOBID 14 CELLID 10
- Rebuilding seg 54 VOBID 14 CELLID 11
- Updating NAVPACKS for VOBID_14
- Rebuilding seg 55 VOBID 15 CELLID 1
- Rebuilding seg 56 VOBID 15 CELLID 2
- Rebuilding seg 57 VOBID 15 CELLID 3
- Rebuilding seg 58 VOBID 15 CELLID 4
- Rebuilding seg 59 VOBID 15 CELLID 5
- Rebuilding seg 60 VOBID 15 CELLID 6
- Updating NAVPACKS for VOBID_15
- Rebuilding seg 61 VOBID 16 CELLID 1
- Processed 15.8MB ILVU section...
- Updating NAVPACKS for VOBID_16
- Rebuilding seg 62 VOBID 17 CELLID 1
- Rebuilding seg 63 VOBID 17 CELLID 2
- Rebuilding seg 64 VOBID 18 CELLID 1
- Rebuilding seg 65 VOBID 18 CELLID 2
- Updating NAVPACKS for VOBID_17
- Updating NAVPACKS for VOBID_18
- Rebuilding seg 66 VOBID 19 CELLID 1
- Rebuilding seg 67 VOBID 19 CELLID 2
- Updating NAVPACKS for VOBID_19
- Rebuilding seg 68 VOBID 20 CELLID 1
- Processed 14.9MB ILVU section...
- Updating NAVPACKS for VOBID_20
- Rebuilding seg 69 VOBID 21 CELLID 1
- Rebuilding seg 70 VOBID 21 CELLID 2
- Rebuilding seg 71 VOBID 22 CELLID 1
- Rebuilding seg 72 VOBID 22 CELLID 2
- Updating NAVPACKS for VOBID_21
- Updating NAVPACKS for VOBID_22
- Rebuilding seg 73 VOBID 23 CELLID 1
- Rebuilding seg 74 VOBID 23 CELLID 2
- Rebuilding seg 75 VOBID 23 CELLID 3
- Rebuilding seg 76 VOBID 23 CELLID 4
- Rebuilding seg 77 VOBID 23 CELLID 5
- Rebuilding seg 78 VOBID 23 CELLID 6
- Rebuilding seg 79 VOBID 23 CELLID 7
- Rebuilding seg 80 VOBID 23 CELLID 8
- Rebuilding seg 81 VOBID 23 CELLID 9
- Rebuilding seg 82 VOBID 23 CELLID 10
- Rebuilding seg 83 VOBID 23 CELLID 11
- Updating NAVPACKS for VOBID_23
- Rebuilding seg 84 VOBID 24 CELLID 1
- Processed 18.5MB ILVU section...
- Updating NAVPACKS for VOBID_24
- Rebuilding seg 85 VOBID 25 CELLID 1
- Rebuilding seg 86 VOBID 25 CELLID 2
- Rebuilding seg 87 VOBID 26 CELLID 1
- Rebuilding seg 88 VOBID 26 CELLID 2
- Updating NAVPACKS for VOBID_25
- Updating NAVPACKS for VOBID_26
- Rebuilding seg 89 VOBID 27 CELLID 1
- Rebuilding seg 90 VOBID 27 CELLID 2
- Rebuilding seg 91 VOBID 27 CELLID 3
- Updating NAVPACKS for VOBID_27
- Rebuilding seg 92 VOBID 28 CELLID 1
- Processed 47.4MB ILVU section...
- Updating NAVPACKS for VOBID_28
- Rebuilding seg 93 VOBID 29 CELLID 1
- Rebuilding seg 94 VOBID 29 CELLID 2
- Rebuilding seg 95 VOBID 30 CELLID 1
- Rebuilding seg 96 VOBID 30 CELLID 2
- Updating NAVPACKS for VOBID_29
- Updating NAVPACKS for VOBID_30
- Rebuilding seg 97 VOBID 31 CELLID 1
- Rebuilding seg 98 VOBID 31 CELLID 2
- Rebuilding seg 99 VOBID 31 CELLID 3
- Updating NAVPACKS for VOBID_31
- Rebuilding seg 100 VOBID 32 CELLID 1
- Processed 18.8MB ILVU section...
- Updating NAVPACKS for VOBID_32
- Rebuilding seg 101 VOBID 33 CELLID 1
- Rebuilding seg 102 VOBID 33 CELLID 2
- Rebuilding seg 103 VOBID 34 CELLID 1
- Rebuilding seg 104 VOBID 34 CELLID 2
- Updating NAVPACKS for VOBID_33
- Updating NAVPACKS for VOBID_34
- Rebuilding seg 105 VOBID 35 CELLID 1
- Rebuilding seg 106 VOBID 35 CELLID 2
- Updating NAVPACKS for VOBID_35
- Rebuilding seg 107 VOBID 36 CELLID 1
- Processed 30.1MB ILVU section...
- Updating NAVPACKS for VOBID_36
- Rebuilding seg 108 VOBID 37 CELLID 1
- Rebuilding seg 109 VOBID 37 CELLID 2
- Rebuilding seg 110 VOBID 38 CELLID 1
- Rebuilding seg 111 VOBID 38 CELLID 2
- Updating NAVPACKS for VOBID_37
- Updating NAVPACKS for VOBID_38
- Rebuilding seg 112 VOBID 39 CELLID 1
- Rebuilding seg 113 VOBID 39 CELLID 2
- Rebuilding seg 114 VOBID 39 CELLID 3
- Rebuilding seg 115 VOBID 39 CELLID 4
- Rebuilding seg 116 VOBID 39 CELLID 5
- Rebuilding seg 117 VOBID 39 CELLID 6
- Rebuilding seg 118 VOBID 39 CELLID 7
- Rebuilding seg 119 VOBID 39 CELLID 8
- Rebuilding seg 120 VOBID 39 CELLID 9
- Rebuilding seg 121 VOBID 39 CELLID 10
- Rebuilding seg 122 VOBID 39 CELLID 11
- Rebuilding seg 123 VOBID 39 CELLID 12
- Rebuilding seg 124 VOBID 39 CELLID 13
- Updating NAVPACKS for VOBID_39
- Rebuilding seg 125 VOBID 40 CELLID 1
- Updating NAVPACKS for VOBID_40
- Rebuilding seg 126 VOBID 41 CELLID 1
- Updating NAVPACKS for VOBID_41
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[08:02:36] Phase III, REBUILD completed in 18 minutes.

Done.
[08:02:36] PREPARE/ENCODE/REBUILD completed in 284 min.

IT didnt fit in one post so I had to split it up. Thanks for everyones time and help.

[Rippraff]

FORGET ABOUT VOB BLANKER. If I just load the matrix into DVD-RB and select the option for menus and movie only and blank extras WITHIN DVD-RB.
Nobody hast told you to use Vobblanker, specially when your aim is menu and movie only. ;)
And for some reason I get such a low bitrate.
This isn't a low bitrate for a 131 min movie! :)
Seems to me everything is working okay.

And please use the http://forum.doom9.org/images/editor/code.gif-button next time! Easier to read and it will fit in one post as well. ;)

Cu Rippraff

[maxse]

Rip so is my bitrate 2.0 or 3.7?

And what do you mean by the # button? Thanks.

[Rippraff]

Rip so is my bitrate 2.0 or 3.7?
2.0 :confused:
As I said
=> 3,783 kbs is your final average bitrate after blanking the extras!

And what do you mean by the # button? Thanks.
Go advanced and you will see the button, it's for CODE. ;)

Cu Rippraff

[maxse]

I see... I was conmfused with the bitrate becaue the before and after values where Identical. You have been an awesome help, thanks man. Now if I can only figure out how to disable the menu buttons in pgc edit for the matrix. It worked flawlessly for Finding Nemo but not so for The Matrix. I'll look for the 2,3,4 b as you stated in the pgc edit and see what I get (cant do it right now). Thanks for your help again and hopefully Ill get the disabling menu thing to work.

[Rippraff]

As I mentioned above there is often more than one screen with the same content.
I've just made an example (http://www.Rippraff.de/Stuff/Menu_edit.htm) for you which shows how to blank two buttons for one and the same extra (inside look).
It can be different in your case so check all the button (...b.) entries in the left frame.

Cu Rippraff