Question about OPV HCEnc

[nwg]

I just upgraded to the Pro version to make use of the One Pass encode for HC.

However, it still takes a very long time due to the analysis. Has anyone noticed this?

I thought it would do a quick analysis and then do one pass encode. I have a homemade DVD (4 VTS at 42 minutes each). It took an hour to just do the analysis on one VTS. I was hoping it would do it in a two or three hours max. A normal 2 pass at defult quality for me takes six hours.

The reduction level is only 77% so I didn't want 2 passes but still use HC.

As it was still taking so long. I have now decided to use Quenc one pass for this DVD.

[blutach]

How long was the whole process nwg (all VTSs)? Or did you just do a movie only. If so, an hour is just fine.

Regards

[nwg]

I didn't complete the whole process.

It took an hour each to analysis VTS 1 and VTS 2 before I cancelled it. It looked like it would then take four hours as there is 4 separate VTS and that was before the encoding started.

I had to cancel as I ran out of time and needed to do other things.

The disc is 5.41GB with a simple menu done in TDA.

[UncasMS]

the last time i used opv was with some 160min of material to analyse and convert

preparation took 17 min on my machine:

[01:18:44] Phase I, PREPARATION completed in 17 minutes.

here's the log:

[01:00:59] One Click encoding activated...
-----------------
[01:01:00] Phase I, PREPARATION started.
- HC encoder selected 
- "Steal Space from Extras" mode is enabled.
- "One Pass VBR (w/analysis)" mode is enabled.
- VTS_01: 3.007.885 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 189.243 frames.
-- Building .AVS and .ECL files
- VTS_02: 72.371 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.570 frames.
-- Building .AVS and .ECL files
- VTS_03: 98.411 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 8.492 frames.
-- Building .AVS and .ECL files
- VTS_04: 175.293 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 15.058 frames.
-- Building .AVS and .ECL files
- VTS_05: 98.804 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 6.741 frames.
-- Building .AVS and .ECL files
- VTS_06: 175.553 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 15.225 frames.
-- Building .AVS and .ECL files
- VTS_07: 51.693 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.001 frames.
-- Building .AVS and .ECL files
- VTS_11: 96.292 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 8.427 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 43,9%
- Overall Bitrate : 2.236Kbs
- Space for Video : 2.770.248KB
- Analyzing VTS_01 for optimal CQ factor.
  -- TargetSize (sectors):1.162.151
  -- Sampling 3792 of 189243 frames.
  -- Predicted size (sectors) at CQ=4,2: 2.305.206
  -- Predicted size (sectors) at CQ=8,3: 1.209.246
  -- Predicted size (sectors) at CQ=8,6: 1.140.471
  -- Predicted size (sectors) at CQ=8,4: 1.188.575
  -- Predicted size (sectors) at CQ=8,5: 1.164.542
- CQ Value selected: 8,6
- Analyzing VTS_02 for optimal CQ factor.
  -- TargetSize (sectors):23.098
  -- Sampling 120 of 5570 frames.
  -- Predicted size (sectors) at CQ=6,2: 15.302
  -- Predicted size (sectors) at CQ=4,1: 23.215
- CQ Value selected: 4,2
- Analyzing VTS_03 for optimal CQ factor.
  -- TargetSize (sectors):31.233
  -- Sampling 180 of 8492 frames.
  -- Predicted size (sectors) at CQ=7,0: 42.820
  -- Predicted size (sectors) at CQ=9,5: 28.124
  -- Predicted size (sectors) at CQ=8,5: 33.854
  -- Predicted size (sectors) at CQ=9,2: 29.813
  -- Predicted size (sectors) at CQ=8,7: 32.547
  -- Predicted size (sectors) at CQ=9,0: 30.848
  -- Predicted size (sectors) at CQ=8,8: 31.860
  -- Predicted size (sectors) at CQ=8,9: 31.386
- CQ Value selected: 9,0
- Analyzing VTS_04 for optimal CQ factor.
  -- TargetSize (sectors):55.543
  -- Sampling 312 of 15058 frames.
  -- Predicted size (sectors) at CQ=6,9: 61.820
  -- Predicted size (sectors) at CQ=7,6: 57.071
  -- Predicted size (sectors) at CQ=7,8: 56.029
- CQ Value selected: 7,9
- Analyzing VTS_05 for optimal CQ factor.
  -- TargetSize (sectors):31.506
  -- Sampling 144 of 6741 frames.
  -- Predicted size (sectors) at CQ=5,5: 58.186
  -- Predicted size (sectors) at CQ=10,1: 29.931
  -- Predicted size (sectors) at CQ=9,5: 33.054
  -- Predicted size (sectors) at CQ=9,9: 30.876
  -- Predicted size (sectors) at CQ=9,7: 31.967
  -- Predicted size (sectors) at CQ=9,8: 31.341
- CQ Value selected: 9,8
- Analyzing VTS_06 for optimal CQ factor.
  -- TargetSize (sectors):55.598
  -- Sampling 312 of 15225 frames.
  -- Predicted size (sectors) at CQ=7,0: 62.694
  -- Predicted size (sectors) at CQ=7,8: 56.809
  -- Predicted size (sectors) at CQ=7,9: 56.288
- CQ Value selected: 8,0
- Analyzing VTS_07 for optimal CQ factor.
  -- TargetSize (sectors):16.273
  -- Sampling 108 of 5001 frames.
  -- Predicted size (sectors) at CQ=7,9: 15.471
  -- Predicted size (sectors) at CQ=7,5: 15.998
  -- Predicted size (sectors) at CQ=7,3: 16.376
- CQ Value selected: 7,4
- Analyzing VTS_11 for optimal CQ factor.
  -- TargetSize (sectors):30.500
  -- Sampling 180 of 8427 frames.
  -- Predicted size (sectors) at CQ=7,1: 30.827
- CQ Value selected: 7,2
- Movie improvement from extra reduction = 7,5%
- HIGH/LOW/TYPICAL Bitrates: 2.975/600/2.236 Kbs
[01:18:44] Phase I, PREPARATION completed in 17 minutes.
[01:18: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_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
 - Extracting STILLS for VTS_01 segment 33
 - 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_03 segment 0
 - Extracting STILLS for VTS_03 segment 1
 - Creating M2V for VTS_04 segment 0
 - Extracting STILLS for VTS_04 segment 1
 - Creating M2V for VTS_05 segment 0
 - Creating M2V for VTS_05 segment 1
 - Creating M2V for VTS_05 segment 2
 - Creating M2V for VTS_05 segment 3
 - Creating M2V for VTS_05 segment 4
 - Creating M2V for VTS_05 segment 5
 - Creating M2V for VTS_05 segment 6
 - Creating M2V for VTS_05 segment 7
 - Creating M2V for VTS_05 segment 8
 - Extracting STILLS for VTS_05 segment 9
 - Creating M2V for VTS_06 segment 0
 - Extracting STILLS for VTS_06 segment 1
 - Creating M2V for VTS_07 segment 0
 - Creating M2V for VTS_07 segment 1
 - Extracting STILLS for VTS_07 segment 2
 - Creating M2V for VTS_11 segment 0
 - Creating M2V for VTS_11 segment 1
 - Creating M2V for VTS_11 segment 2
 - Extracting STILLS for VTS_11 segment 3
[03:14:06] Phase II ENCODING completed in  116 minutes.
[03:14:07] 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
  - 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
  - Updating NAVPACKS for VOBID_02
  - 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
  - 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
  - Rebuilding seg 9 VOBID 10 CELLID 1
  - Updating NAVPACKS for VOBID_10
  - Rebuilding seg 10 VOBID 11 CELLID 1
  - Updating NAVPACKS for VOBID_11
  - 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
  - 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_04_0.IFO
  - Updating TMAP table...
- Processing VTS_05
  - 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
  - Updating NAVPACKS for VOBID_01
  - Rebuilding seg 9 VOBID 2 CELLID 1
  - Updating NAVPACKS for VOBID_02
  - Updated VTS_C_ADT.
  - Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
  - Updating TMAP table...
- Processing VTS_06
  - 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_06_0.IFO
  - Updating TMAP table...
- Processing VTS_07
  - 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
  - Updated VTS_C_ADT.
  - Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
  - Updating TMAP table...
- Processing VTS_11
  - 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_11_0.IFO
  - Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- ISO Image successfully created.
- Writing ISO image to DVD...
- ISO Image successfully written.
[03:42:10] Phase III, REBUILD completed in 28 minutes.

Done.
[03:42:10] PREPARE/ENCODE/REBUILD completed in 162 min.

rebuilding took more than the usual 10 min as an iso was created

[nwg]

Thanks.

The prepare stage was cancelled at 2 hours.

I am going to try it with a proper DVD and see if it any different.

[blutach]

Yes, the pre-preocessing with TDA is probably the culprit. jdobbs says eliminate all preprocessing first and then see if there's still problems.

Regards

[nwg]

If it is TDA causing the problem then it is a shame. I often do TV series of the TV and shink episodes to fit on a DVD. Sometimes if the series is good enough, I like to use a encoder instead of Shrink. I was hoping to use HC and do it with one pass. Quenc will do. I just finished the DVD and Quenc one pass took 3 hour to encode.

I am trying a movie only backup with WOTW DVD now.

[jdobbs]

What do you have your sampling percentage set to? Normally 1-2% is all that is necessary. The problem is that if you set it so high levels (say 10%) and it takes an average of 4 sampling passes to hit the target, you can use almost half as much time as a first pass.

Hank315 is also working on an improved 1 pass method completely within HC. I haven't talked to him in a while, not sure how its going.

Normally a one pass prediction PREPARE takes less than 20 minutes.

[nwg]

Hi jdobbs.

I don't know anything about changing the sampling percentages. I assume I am using the default settings.

I did War of the Worlds R2. It was movie only with OPV HC. The results were excellent but only came to a total of 4.13GB.

The prepare stage was done quicker but still 48 minutes. This may be due to me only having a Athlon XP 2000 chip.

[01:53:50] Phase I, PREPARATION started.
- HC encoder selected
- "One Pass VBR (w/analysis)" mode is enabled.
- "Movie Only" mode is enabled.
- VTS_03: 3,033,189 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 167,658 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 81.3%
- Overall Bitrate : 4,954Kbs
- Space for Video : 4,055,598KB
- Analyzing VTS_03 for optimal CQ factor.
-- TargetSize (sectors):2,058,216
-- Sampling 3360 of 167658 frames.
-- Predicted size (sectors) at CQ=2.1: 3,355,848
-- Predicted size (sectors) at CQ=3.4: 2,951,708
-- Predicted size (sectors) at CQ=4.8: 2,401,415
-- Predicted size (sectors) at CQ=5.6: 2,095,370
-- Predicted size (sectors) at CQ=5.7: 2,066,926
- CQ Value selected: 5.8
- HIGH/LOW/TYPICAL Bitrates: 5,287/3,407/4,954 Kbs
[02:41:27] Phase I, PREPARATION completed in 48 minutes.

The encoding was done in 265 minutes.

[jdobbs]

Hi.

I'll take a look at the prediction algorithm for HC. It took 5 passes to hit the right value for you -- I try to make it average 3. The problem is that it changes so much depending upon the movie.

You're at the default value of 2%.

4.13GB is probably within the expected size (maybe a little under). One disadvantage in OPV is that you're calculating the end result based upon a small sampling -- and it's always going to be off a little one way or the other.

Some people use a method that leans toward oversizing and then use a within-the-compressed-domain program to bring it down to size if it gets too big. I've thought about putting in an option to do that with ReJig (you've probably heard of that program, eh? ).

265 minutes for a single pass encode sure seems like a lot, even for an Athlon XP 2000... how are you set for memory and hard drive on that system?

[nwg]

265 minutes for a single pass encode sure seems like a lot, even for an Athlon XP 2000... how are you set for memory and hard drive on that system?

I wouldn't worry about changing it. I am happy with using Quenc single pass mode. I get good sizing with that with most of the time being 4.30GB and higher.

It is probably my computer at fault. Even when using Shrink it can seem a little slow. The average 2 pass encode is 6 -8 hours depending on the DVD and the reduction level.

My computer has 512MB RAM and the hard disk I used had 20GB free on it at the time.