Log in

View Full Version : Confusing Oversizing

Fiebre
21st March 2005, 03:18
I'm sorry if I'm being ignorant, but from what I see in this log Rebuilder seems to be correctly predicting the end sizes and picks one size too big for each of the Q values. The final output was 4.585 GB. Please, if I am being stupid don't hesitate to let me know. Thanks.

Transcoding...
-----------------
[19:25:11] Phase I, PREPARATION started.
- "One Pass VBR (w/analysis)" mode is enabled.
- VTS_01: 2,301,961 sectors.
-- Scanning and writing .D2V file
-- Processed 105,436 frames.
-- Building .AVS and .ECL files
- VTS_02: 369,417 sectors.
-- Scanning and writing .D2V file
-- Processed 23,322 frames.
-- Building .AVS and .ECL files
- VTS_03: 122,996 sectors.
-- Scanning and writing .D2V file
-- Processed 9,580 frames.
-- Building .AVS and .ECL files
- VTS_04: 826,524 sectors.
-- Scanning and writing .D2V file
-- Processed 64,292 frames.
-- Building .AVS and .ECL files
- VTS_05: 85,371 sectors.
-- Scanning and writing .D2V file
-- Processed 6,626 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 49.6%
- Overall Bitrate : 3,131Kbs
- Space for Video : 3,336,228KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):1,012,119
-- Sampling 1056 of 105436 frames.
-- Predicted size (sectors) at Q=27: 1,243,975
-- Predicted size (sectors) at Q=35: 1,065,162
-- Predicted size (sectors) at Q=37: 1,027,882
- Q Value selected: 37
- Analyzing VTS_02 for optimal Q factor.
-- TargetSize (sectors):179,122
-- Sampling 240 of 23322 frames.
-- Predicted size (sectors) at Q=33: 257,205
-- Predicted size (sectors) at Q=52: 186,912
-- Predicted size (sectors) at Q=55: 179,155
- Q Value selected: 55
- Analyzing VTS_03 for optimal Q factor.
-- TargetSize (sectors):59,654
-- Sampling 96 of 9580 frames.
-- Predicted size (sectors) at Q=41: 113,828
-- Predicted size (sectors) at Q=91: 69,711
-- Predicted size (sectors) at Q=111: 59,767
- Q Value selected: 111
- Analyzing VTS_04 for optimal Q factor.
-- TargetSize (sectors):400,879
-- Sampling 648 of 64292 frames.
-- Predicted size (sectors) at Q=41: 509,723
-- Predicted size (sectors) at Q=56: 443,103
-- Predicted size (sectors) at Q=63: 418,916
-- Predicted size (sectors) at Q=66: 409,790
-- Predicted size (sectors) at Q=67: 406,901
-- Predicted size (sectors) at Q=68: 404,133
- Q Value selected: 68
- Analyzing VTS_05 for optimal Q factor.
-- TargetSize (sectors):41,360
-- Sampling 72 of 6626 frames.
-- Predicted size (sectors) at Q=41: 44,992
-- Predicted size (sectors) at Q=45: 42,305
-- Predicted size (sectors) at Q=46: 41,595
- Q Value selected: 46
- HIGH/LOW/AVERAGE Cell Bitrates: 4,162/1,917/3,131 Kbs
[19:33:44] Phase I, PREPARATION completed in 8 minutes.
[19:33:44] 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_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_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
- Creating M2V for VTS_04 segment 6
- Creating M2V for VTS_05 segment 0
[20:48:27] Phase II ENCODING completed in 75 minutes.
[20:48:27] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Rebuilding segment 7 VOBID: 1 CELLID: 8
- Rebuilding segment 8 VOBID: 1 CELLID: 9
- Rebuilding segment 9 VOBID: 1 CELLID: 10
- Rebuilding segment 10 VOBID: 1 CELLID: 11
- Rebuilding segment 11 VOBID: 1 CELLID: 12
- Rebuilding segment 12 VOBID: 1 CELLID: 13
- Rebuilding segment 13 VOBID: 1 CELLID: 14
- Rebuilding segment 14 VOBID: 1 CELLID: 15
- Rebuilding segment 15 VOBID: 1 CELLID: 16
- Rebuilding segment 16 VOBID: 1 CELLID: 17
- Rebuilding segment 17 VOBID: 1 CELLID: 18
- Rebuilding segment 18 VOBID: 1 CELLID: 19
- Rebuilding segment 19 VOBID: 1 CELLID: 20
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 20 VOBID: 2 CELLID: 1
- Rebuilding segment 21 VOBID: 2 CELLID: 2
- Rebuilding segment 22 VOBID: 2 CELLID: 3
- Rebuilding segment 23 VOBID: 2 CELLID: 4
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 24 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Processing VTS_02
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 4 VOBID: 5 CELLID: 1
- Updating NAVPACKS for VOBID_05
- Rebuilding segment 5 VOBID: 6 CELLID: 1
- Updating NAVPACKS for VOBID_06
- Rebuilding segment 6 VOBID: 7 CELLID: 1
- Updating NAVPACKS for VOBID_07
- Rebuilding segment 7 VOBID: 8 CELLID: 1
- Updating NAVPACKS for VOBID_08
- Rebuilding segment 8 VOBID: 9 CELLID: 1
- Updating NAVPACKS for VOBID_09
- Rebuilding segment 9 VOBID: 10 CELLID: 1
- Updating NAVPACKS for VOBID_10
- Rebuilding segment 10 VOBID: 11 CELLID: 1
- Updating NAVPACKS for VOBID_11
- Rebuilding segment 11 VOBID: 12 CELLID: 1
- Updating NAVPACKS for VOBID_12
- Rebuilding segment 12 VOBID: 13 CELLID: 1
- Updating NAVPACKS for VOBID_13
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Processing VTS_03
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Processing VTS_04
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 6 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Processing VTS_05
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
Correcting VTS Sectors...
[21:01:53] Phase III, REBUILD completed in 13 minutes.

Done.
jdobbs
21st March 2005, 04:15
The encodes generally have a tendency to undersize. So when the predicted size is within 1% of the target, and the Q value is over 20 (meaning a single increment/decrement doesn't have a huge impact) it doesn't bring it down to the new lower Q.

As I've warned, OPV predicts well most of the time, but will never be perfect... that's the price you pay for the 50% time reduction (compared to a 2 pass encode).

In one of the next two versions (v0.80/v0.81) I am adding code that will perform a second pass on a segment when the resulting M2V is oversized or is drastically undersized. That should prevent having complete oversizing as has happened in your case.