PDA

View Full Version : Yet another dvd output size issue


vwpassion
17th July 2007, 21:16
Following scenario:

Source: 4,42 GB (preprocessed with VobBlanker)
Goal: Keeping all chapters untouched except the last one.

Encoder used was CCE SP2, 3 passes.

After loading the source I hit prepare, then switched to the Segment Editor / Preview, ticked 'No Reencode' on all chapters except the last one. For the last one I used 40% compression to hit a size within the Target Sectors (it showed 4,36GB). I then hit Encode/Rebuild and then final output size I got was only 4.31GB.

Things I noticed: In the preview / Segment Editor I noticed that when i moved the slider to the very right, it showed me a size of 4.48GB (remember: the source is only 4.42GB).

CCETargetSectors is set to 2254000 by the way. Another option that I used is CCEAQM=1.

This really puzzles me.. Why is DVDRB showing me a size of 4.48 in the preview (when I use no compression at all), and why is the output size (when encoding only the last chapter) 4.30GB instead of 4.36 (which was the size DVDRB calculated in the segment editor)?

Thanks for help in advance. :)

PS: I included the logfile.


-----------------
[21:02:54] Phase I, PREPARATION started.
- DVD-RB v1.26.2
- AVISYNTH 2.5.5.0
- CCE 1.0.0.10 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- Source: STRIPPED
- VTS_02: 2.309.093 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 184.190 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 96,7%
- Overall Bitrate : 4.143Kbs
- Space for Video : 3.726.158KB
- HIGH/LOW/TYPICAL Bitrates: 5.871/410/4.143 Kbs
[21:04:13] Phase I, PREPARATION completed in 2 minutes.
[21:05:23] Phase II ENCODING started
- Extracting Video for VTS_02 segment 0
- Extracting Video for VTS_02 segment 1
- Extracting Video for VTS_02 segment 2
- Extracting Video for VTS_02 segment 3
- Extracting Video for VTS_02 segment 4
- Extracting Video for VTS_02 segment 5
- Extracting Video for VTS_02 segment 6
- Extracting Video for VTS_02 segment 7
- Extracting Video for VTS_02 segment 8
- Extracting Video for VTS_02 segment 9
- Extracting Video for VTS_02 segment 10
- Extracting Video for VTS_02 segment 11
- Extracting Video for VTS_02 segment 12
- Extracting Video for VTS_02 segment 13
- Extracting Video for VTS_02 segment 14
- Extracting Video for VTS_02 segment 15
- Extracting Video for VTS_02 segment 16
- Extracting Video for VTS_02 segment 17
- Extracting Video for VTS_02 segment 18
- Extracting Video for VTS_02 segment 19
- Extracting Video for VTS_02 segment 20
- Extracting Video for VTS_02 segment 21
- Extracting Video for VTS_02 segment 22
- Extracting Video for VTS_02 segment 23
- Extracting Video for VTS_02 segment 24
- Extracting Video for VTS_02 segment 25
- Extracting Video for VTS_02 segment 26
- Extracting Video for VTS_02 segment 27
- Extracting Video for VTS_02 segment 28
- Extracting Video for VTS_02 segment 29
- Creating M2V for VTS_02 segment 30
- Extracting Video for VTS_02 segment 31
[21:10:09] Phase II ENCODING completed in 5 minutes.
[21:10:13] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- 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
- 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
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 18 VOBID 3 CELLID 1
- Rebuilding seg 19 VOBID 3 CELLID 2
- Rebuilding seg 20 VOBID 3 CELLID 3
- Rebuilding seg 21 VOBID 3 CELLID 4
- Rebuilding seg 22 VOBID 3 CELLID 5
- Rebuilding seg 23 VOBID 3 CELLID 6
- Rebuilding seg 24 VOBID 3 CELLID 7
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 25 VOBID 4 CELLID 1
- Rebuilding seg 26 VOBID 4 CELLID 2
- Rebuilding seg 27 VOBID 4 CELLID 3
- Rebuilding seg 28 VOBID 4 CELLID 4
- Rebuilding seg 29 VOBID 4 CELLID 5
- Rebuilding seg 30 VOBID 4 CELLID 6
- Rebuilding seg 31 VOBID 4 CELLID 7
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[21:14:56] Phase III, REBUILD completed in 4 minutes.

Done.

mc2man
17th July 2007, 23:23
Vobblanker is unnecessary Try without preprocessing

vwpassion
18th July 2007, 00:46
Vobblanker is unnecessary Try without preprocessing

I don't see why that would matter though. I did only blank some menu cells which I didn't need anymore. Anyway, I have tried either way and I keep getting the same unsatisfying results.

mc2man
18th July 2007, 01:41
are you using movie only mode?

blutach
18th July 2007, 02:42
This has nothing to do with VobBlanker (http://jsoto.posunplugged.com/vobblanker.htm). It has to do with encoder overhead (about 1.3%) and variability.

This happens a lot. You have answered yourself in a way. Recognise the source only needs to be lowered to 4.42Gb in the previewer, ignore the oversize warning, and away you go.

Just as a guide, I use HCTargetSectors=2262500 and TargetSectors=2265000 (for Procoder) and the encodes always work out at 4.36-4.37Gb (about 0.06Gb less than indicated by the target sectors - which coincidentally enough, is the difference you are seeing).

Regards

nashcity
18th July 2007, 05:23
This is the same issue I've already mentioned a few times.

http://forum.doom9.org/showthread.php?p=1008190#post1008190

Its a bit annoying. I just set my final output size to 4.41 g or so and it usually comes out to 4.35 g. It would definitely be nice if the output matched the size specified in the segment editor.

vwpassion
18th July 2007, 17:31
Ok guys, thanks for the feedback. It did work just fine when I set the output to 4.41GB. This really puzzled me. Would indeed be nice if the output matched the size specified in the segment editor.