Log in

View Full Version : Inconvenient Truth - undersizing


archaeo
28th February 2007, 03:04
Haven't had many problems in the past with sizing in DVD-RB, but this one has been stubborn. :confused: I thought perhaps it might have been because I just upgraded to Avisynth 2.5.6, but I went back to 2.54 to test w/ same settings, and it also came out to same size: 4.12 gb. Any help here appreciated.

My steps:
Ripped with Decrypter, and set RB to Full backup, menu encoding enabled. I used undot()deen() in filters, but have never had a problem with these two filters before.. Matrix used is Auto-Q2, also CCEAQM=0, and CCETargetSectors=2246064

here's my log:

[18:37:16] One Click encoding activated...
-----------------
[18:37:17] Phase I, PREPARATION started.
- DVD-RB v1.22
- AVISYNTH 2.5.4.0
- CCE 2.70.2.11 encoder selected.
- AVS Filters are enabled.
- Source: INCONVENIENTTRUTH
- VTSM_02: 51,150 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2,535 frames.
-- Building .AVS and .ECL files
- VTS_02: 2,159,494 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 139,014 frames.
-- Building .AVS and .ECL files
- VTS_03: 76,455 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 6,571 frames.
-- Building .AVS and .ECL files
- VTS_04: 1,019,471 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,312 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 62.6%
- Overall Bitrate : 3,888/3,110Kbs
- Space for Video : 3,585,438KB
- HIGH/LOW/TYPICAL Bitrates: 7,976/1,178/3,110 Kbs
[18:50:03] Phase I, PREPARATION completed in 13 minutes.
[18:50:03] Phase II ENCODING started
- Creating M2V for VTSM_02 segment 0
- Creating M2V for VTSM_02 segment 1
- Extracting STILLS for VTSM_02 segment 2
- Extracting STILLS for VTSM_02 segment 3
- Extracting STILLS for VTSM_02 segment 4
- Extracting STILLS for VTSM_02 segment 5
- Extracting STILLS for VTSM_02 segment 6
- Extracting STILLS for VTSM_02 segment 7
- Extracting STILLS for VTSM_02 segment 8
- Extracting STILLS for VTSM_02 segment 9
- 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
- Extracting STILLS for VTS_02 segment 44
- Creating M2V for VTS_03 segment 0
- Extracting STILLS 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_04 segment 7
- Creating M2V for VTS_04 segment 8
- Creating M2V for VTS_04 segment 9
- Creating M2V for VTS_04 segment 10
- Creating M2V for VTS_04 segment 11
- Creating M2V for VTS_04 segment 12
- Extracting STILLS for VTS_04 segment 13
- Extracting STILLS for VTS_04 segment 14
[02:54:36] Phase II ENCODING completed in 484 minutes.
[02:54:37] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_02
- 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
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
- Rebuilding seg 31 VOBID 1 CELLID 32
- Rebuilding seg 32 VOBID 1 CELLID 33
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 33 VOBID 2 CELLID 1
- Rebuilding seg 34 VOBID 2 CELLID 2
- Rebuilding seg 35 VOBID 2 CELLID 3
- Rebuilding seg 36 VOBID 2 CELLID 4
- Rebuilding seg 37 VOBID 2 CELLID 5
- Rebuilding seg 38 VOBID 2 CELLID 6
- Rebuilding seg 39 VOBID 2 CELLID 7
- Rebuilding seg 40 VOBID 2 CELLID 8
- Rebuilding seg 41 VOBID 2 CELLID 9
- Rebuilding seg 42 VOBID 2 CELLID 10
- Rebuilding seg 43 VOBID 2 CELLID 11
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 44 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- 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
- 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
- Rebuilding seg 2 VOBID 1 CELLID 3
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 3 VOBID 2 CELLID 1
- Rebuilding seg 4 VOBID 2 CELLID 2
- Rebuilding seg 5 VOBID 2 CELLID 3
- Rebuilding seg 6 VOBID 2 CELLID 4
- Rebuilding seg 7 VOBID 2 CELLID 5
- Rebuilding seg 8 VOBID 2 CELLID 6
- Rebuilding seg 9 VOBID 2 CELLID 7
- Rebuilding seg 10 VOBID 2 CELLID 8
- Rebuilding seg 11 VOBID 2 CELLID 9
- Rebuilding seg 12 VOBID 2 CELLID 10
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 13 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 14 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Processing VTSM_02
- 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
- Rebuilding seg 5 VOBID 5 CELLID 2
- Rebuilding seg 6 VOBID 5 CELLID 3
- Rebuilding seg 7 VOBID 5 CELLID 4
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 8 VOBID 6 CELLID 1
- Rebuilding seg 9 VOBID 6 CELLID 2
- Updating NAVPACKS for VOBID_06
- Updated VTSM_C_ADT.
- Updated VTSM_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Correcting VTS Sectors...
[03:20:15] Phase III, REBUILD completed in 26 minutes.

Done.
[03:20:15] PREPARE/ENCODE/REBUILD completed in 523 min.

Fishman0919
28th February 2007, 03:27
Set CCEAQM=0 to CCEAQM=1 and try 3 passes.

With undot()deen() you are clean up the picture and with Auto-Q2 the encoder is probably having saturation problems. Try CCEAQM=1 and try 3 passes... CCEAQM=1 will help with Auto-Q2 and the saturation... the 3-passes helps with CCEAQM=1 and sizing.

See LINK (http://forum.doom9.org/showthread.php?p=962107#post962107) about Adaptive quantize matrix / CCEAQM

archaeo
28th February 2007, 03:51
Set CCEAQM=0 to CCEAQM=1 and try 3 passes.

With undot()deen() you are clean up the picture and with Auto-Q2 the encoder is probably having saturation problems. Try CCEAQM=1 and try 3 passes... CCEAQM=1 will help with Auto-Q2 and the saturation... the 3-passes helps with CCEAQM=1 and sizing.

See LINK (http://forum.doom9.org/showthread.php?p=962107#post962107) about Adaptive quantize matrix / CCEAQM


Thanks Fishman for the quick response. So it may be that the combination of filtering and Auto-Q2 is skewing the ouput...
Undot()deen() never gave me much increased compression in the past, but I must say that Auto Q2 seems to be pretty effective for compression. I chose it since the predicted overall was approx 3100, but maybe there was a better choice. However, I'll run this overnight with your suggestions, and report back. (I stress tomorrow because you can see that it took all of 8+ hrs)

Mug Funky
28th February 2007, 05:07
this movie is mostly static blackness with a talking person standing still. it'll compress very well.

so yeah, auto matrix in CCE should help you hit the target. i'd drop off some of your filters, too as they're probably not necessary (maybe a deblocker will help things, but the rest should be enough for CCE to handle on it's own).

jdobbs
28th February 2007, 12:17
What kind of Q values are you getting? It's possible that you're hitting encoder saturation on some part of the encode. If that's the case -- it's actually a good thing, because it means you are getting the "best you can get".

archaeo
28th February 2007, 15:45
I'll have to get back with the results tonite - when I left for work this morning, it was only at 75% complete - 3 passes with a Pentium III takes a LOT of patience.

archaeo
1st March 2007, 03:05
Bingo - right on the money at 4.35 gb :)

The Q level of this encode was coming in at around 8, so yes, it looks like saturation was a factor. Surprised to have such a low Q with a 62% compression ratio ... ! But as Mug Funky mentioned, the nature of the film is easily compressible.

Many thanks to everyone for their comments.

Fishman0919
1st March 2007, 14:51
Bingo - right on the money at 4.35 gb :)

The Q level of this encode was coming in at around 8, so yes, it looks like saturation was a factor. Surprised to have such a low Q with a 62% compression ratio ... ! But as Mug Funky mentioned, the nature of the film is easily compressible.

Many thanks to everyone for their comments.


NP, glad everything worked out well. :)