1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

What kinda processor is the fastest for DVD-RB

Discussion in 'DVD / BD-Rebuilder forum' started by AndreL, Apr 25, 2006.

Page 6 of 7
  1. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    ok feller's got two towers done here.
    7.59gb rebuilt to 4.32b not to shabby on a dual core CPU. might even say its given them Quads a run for the money...lol just joken guys...
    not bad im impressed.

    how ya like this skin?
    figured it was the correct one for the job.
    [​IMG]

    [11:28:43] One Click encoding activated...
    -----------------
    [11:28:43] Phase I, PREPARATION started.
    - DVD-RB v1.26.0
    - AVISYNTH 2.5.6.0
    - CCE 2.70.2.4 encoder selected.
    - Source: LOTR 2
    - VTS_01: 3,769,071 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 258,043 frames.
    -- Building .AVS and .ECL files
    - Reduction Level for DVD-5: 50.7%
    - Overall Bitrate : 3,202/2,562Kbs
    - Space for Video : 3,365,608KB
    - HIGH/LOW/TYPICAL Bitrates: 4,059/786/2,562 Kbs
    [11:30:53] Phase I, PREPARATION completed in 2 minutes.
    [11:30:53] 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
    - Creating M2V for VTS_01 segment 33
    - Creating M2V for VTS_01 segment 34
    - Creating M2V for VTS_01 segment 35
    - Creating M2V for VTS_01 segment 36
    - Creating M2V for VTS_01 segment 37
    - Creating M2V for VTS_01 segment 38
    - Creating M2V for VTS_01 segment 39
    - Creating M2V for VTS_01 segment 40
    - Creating M2V for VTS_01 segment 41
    - Creating M2V for VTS_01 segment 42
    - Creating M2V for VTS_01 segment 43
    - Creating M2V for VTS_01 segment 44
    - Creating M2V for VTS_01 segment 45
    - Creating M2V for VTS_01 segment 46
    - Creating M2V for VTS_01 segment 47
    - Creating M2V for VTS_01 segment 48
    - Creating M2V for VTS_01 segment 49
    - Creating M2V for VTS_01 segment 50
    - Creating M2V for VTS_01 segment 51
    - Creating M2V for VTS_01 segment 52
    - Creating M2V for VTS_01 segment 53
    - Creating M2V for VTS_01 segment 54
    - Extracting STILLS for VTS_01 segment 55
    [12:06:00] Phase II ENCODING completed in 36 minutes.
    [12:06:00] 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
    - Rebuilding seg 33 VOBID 1 CELLID 34
    - Rebuilding seg 34 VOBID 1 CELLID 35
    - Rebuilding seg 35 VOBID 1 CELLID 36
    - Rebuilding seg 36 VOBID 1 CELLID 37
    - Rebuilding seg 37 VOBID 1 CELLID 38
    - Rebuilding seg 38 VOBID 1 CELLID 39
    - Rebuilding seg 39 VOBID 1 CELLID 40
    - Rebuilding seg 40 VOBID 1 CELLID 41
    - Rebuilding seg 41 VOBID 1 CELLID 42
    - Rebuilding seg 42 VOBID 1 CELLID 43
    - Rebuilding seg 43 VOBID 1 CELLID 44
    - Rebuilding seg 44 VOBID 1 CELLID 45
    - Rebuilding seg 45 VOBID 1 CELLID 46
    - Rebuilding seg 46 VOBID 1 CELLID 47
    - Rebuilding seg 47 VOBID 1 CELLID 48
    - Rebuilding seg 48 VOBID 1 CELLID 49
    - Rebuilding seg 49 VOBID 1 CELLID 50
    - Rebuilding seg 50 VOBID 1 CELLID 51
    - Rebuilding seg 51 VOBID 1 CELLID 52
    - Rebuilding seg 52 VOBID 1 CELLID 53
    - Rebuilding seg 53 VOBID 1 CELLID 54
    - Rebuilding seg 54 VOBID 1 CELLID 55
    - Updating NAVPACKS for VOBID_01
    - Rebuilding seg 55 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...
    - Correcting VTS Sectors...
    [12:16:42] Phase III, REBUILD completed in 10 minutes.

    Done.
    [12:16:42] PREPARE/ENCODE/REBUILD completed in 48 min.

    now ill burn it and post the scan over in the scan thread and then link to it from here.
     
    cincyrob, Jun 19, 2008
    #101
  2. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    Nice skin, though i personally prefer the standard one myself; ps Rebuilder's up to v1.27.3 now. Plus have you tried HC encoder ?, it's at 0.23 now, and is (cringe) to quote Bill & Ted, 'most excellent'
     
    Last edited: Jun 19, 2008
    creaky, Jun 19, 2008
    #102
  3. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    no i havent used any other encoder other than CCE. i do know hanks uses all 4 cores of the Quads. so id say you guys with the quads thats the one to use.

    i had 1.26.6 of dvd-rebuild but i like the 1.26version a little better. i had some loading issues. might have been me but, ya gotta go with what ya feel good with...
    might give hanks a try now. o have the bonus disc im gonna do also
     
    cincyrob, Jun 19, 2008
    #103
  4. ZoSoIV

    ZoSoIV Active member

    Joined:
    Oct 24, 2007
    Messages:
    3,454
    Likes Received:
    0
    Trophy Points:
    66
    looks like thats what i will be using(HC encoder) once i get my system up and running with my new Q9450 CPU
     
    ZoSoIV, Jun 21, 2008
    #104
  5. Mort81

    Mort81 Senior member

    Joined:
    Jun 10, 2004
    Messages:
    4,030
    Likes Received:
    0
    Trophy Points:
    116
    I think you will find that CCE is faster even tho it doesn't fully utilize all 4 cores.
     
    Mort81, Jun 21, 2008
    #105
  6. ZoSoIV

    ZoSoIV Active member

    Joined:
    Oct 24, 2007
    Messages:
    3,454
    Likes Received:
    0
    Trophy Points:
    66
    humm really ,thanks for the info Mort
     
    ZoSoIV, Jun 21, 2008
    #106
  7. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    I've found HC to be on par with CCE speed-wise, and quality wise too. In fact i ditched CCE altogether a while back, no need for it now that HC is doing so well.
     
    creaky, Jun 21, 2008
    #107
  8. mord

    mord Regular member

    Joined:
    Sep 9, 2005
    Messages:
    123
    Likes Received:
    0
    Trophy Points:
    26
    i did that too...but i went back to cce when i re-encoded a dvd with lots of action and about 55% compression...the hc encoder result had a lot more pixeltation than the cce result had...
     
    mord, Jun 30, 2008
    #108
  9. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    Strange, I've not yet had any pixelation in any movies/episodics/concerts i've done with Rebuilder, regardless of whether i used CCE or HC. The only slightly negative thing i'll say is that dark scenes aren't perfect. I know there are tweaks that can be done but i can't be doing with all that, i'm more than happy with the results Rebuilder can do, and i'm liking HC more, the more i use it. Let's be honest, the results of a 48% or whatever encode is amazing, even if a little fuzzy in dark scenes. Saying that, all my encodes of Battlestar Galactica seasons were around 48% or so, and lots of dark scenes as to expected from a series like that. But still amazing results whichever way you look at it :)

    ..but as i say i've never had pixellation in any encodes i've done..
     
    creaky, Jun 30, 2008
    #109
  10. mord

    mord Regular member

    Joined:
    Sep 9, 2005
    Messages:
    123
    Likes Received:
    0
    Trophy Points:
    26
    the dvd already had a low bitrate and it was dark...thats the only time i wasnt happy with hc encoder...i think hc encoder will do fine on all newer dvds, but i was backing up a lot of old UFC dvds and the picture is kind of dark and a little grainy...hc encoder did good on the new ufc dvds which has a lot clearer/cleaner picture and not as dark
     
    mord, Jun 30, 2008
    #110
  11. mord

    mord Regular member

    Joined:
    Sep 9, 2005
    Messages:
    123
    Likes Received:
    0
    Trophy Points:
    26
    looks like if i set the luminance gain to 2 or 3 for hc encoder it will do better in dark scenes...i'll re-do an encode and see if it helps :)
     
    mord, Jul 1, 2008
    #111
  12. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    Luminance gain, that's the one :)
    as i say i've never used it, but i may try it out next time i have a dark dvd to encode.
     
    creaky, Jul 1, 2008
    #112
  13. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    well heres a little update to the thread.
    WOW 27 mins for a 8gb movie!!!!!!!!!!!!!!!!!!!!!!
    movie and menu only on this
    heres the log.

    [09:51:44] Phase I, PREPARATION started.
    - DVD-RB v1.26.0
    - AVISYNTH 2.5.6.0
    - HC v0.21.0.0 encoder selected
    - "Movie and Menus Only" mode is enabled.
    - Source: PAUL BLART MALL COP
    - VTS_01: 1,780,696 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 130,996 frames.
    -- Building .AVS and .ECL files
    - VTS_02: 174,066 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 16,090 frames.
    -- Building .AVS and .ECL files
    - VTS_03: 10,828 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1,238 frames.
    -- Building .AVS and .ECL files
    - VTS_04: 770,408 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 88,174 frames.
    -- Building .AVS and .ECL files
    - VTS_05: 23,985 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,130 frames.
    -- Building .AVS and .ECL files
    - VTS_06: 37,861 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,366 frames.
    -- Building .AVS and .ECL files
    - VTS_07: 32,684 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,154 frames.
    -- Building .AVS and .ECL files
    - VTS_08: 9,751 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 913 frames.
    -- Building .AVS and .ECL files
    - VTS_09: 42,056 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,766 frames.
    -- Building .AVS and .ECL files
    - VTS_10: 32,105 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,854 frames.
    -- Building .AVS and .ECL files
    - VTS_11: 44,344 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,926 frames.
    -- Building .AVS and .ECL files
    - VTS_12: 51,544 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 4,576 frames.
    -- Building .AVS and .ECL files
    - VTS_13: 27,502 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,560 frames.
    -- Building .AVS and .ECL files
    - VTS_14: 19,763 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1,880 frames.
    -- Building .AVS and .ECL files
    - VTS_15: 22,587 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,181 frames.
    -- Building .AVS and .ECL files
    - VTS_16: 34,158 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,036 frames.
    -- Building .AVS and .ECL files
    - VTS_17: 55,533 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,692 frames.
    -- Building .AVS and .ECL files
    - VTS_18: 4,975 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 357 frames.
    -- Building .AVS and .ECL files
    - VTS_19: 1,978 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 285 frames.
    -- Building .AVS and .ECL files
    - VTS_20: 3,949 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 474 frames.
    -- Building .AVS and .ECL files
    - VTS_21: 3,181 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 580 frames.
    -- Building .AVS and .ECL files
    - VTS_22: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_23: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_24: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_25: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_26: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_27: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - Reduction Level for DVD-5: 46.1%
    - Overall Bitrate : 2,230/1,784Kbs
    - Space for Video : 2,500,418KB
    - Blanking all EXTRA Segments
    -- Feature before/after: 1,907 / 3,948 Kbs
    [09:53:34] Phase I, PREPARATION completed in 2 minutes.
    [09:53:34] Phase II ENCODING started
    - Extracting Video 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
    - Extracting Video for VTS_01 segment 31
    - 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_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_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
    - Creating M2V for VTS_04 segment 13
    - Creating M2V for VTS_05 segment 0
    - Creating M2V for VTS_05 segment 1
    - Creating M2V for VTS_06 segment 0
    - Creating M2V for VTS_06 segment 1
    - Creating M2V for VTS_07 segment 0
    - Creating M2V for VTS_07 segment 1
    - Creating M2V for VTS_08 segment 0
    - Creating M2V for VTS_08 segment 1
    - Creating M2V for VTS_09 segment 0
    - Creating M2V for VTS_09 segment 1
    - Creating M2V for VTS_10 segment 0
    - Creating M2V for VTS_10 segment 1
    - Creating M2V for VTS_11 segment 0
    - Creating M2V for VTS_11 segment 1
    - Creating M2V for VTS_12 segment 0
    - Creating M2V for VTS_12 segment 1
    - Creating M2V for VTS_13 segment 0
    - Creating M2V for VTS_13 segment 1
    - Creating M2V for VTS_14 segment 0
    - Creating M2V for VTS_14 segment 1
    - Creating M2V for VTS_15 segment 0
    - Creating M2V for VTS_15 segment 1
    - Creating M2V for VTS_16 segment 0
    - Creating M2V for VTS_16 segment 1
    - Creating M2V for VTS_17 segment 0
    - Creating M2V for VTS_17 segment 1
    - Creating M2V for VTS_18 segment 0
    - Creating M2V for VTS_18 segment 1
    - Creating M2V for VTS_19 segment 0
    - Creating M2V for VTS_19 segment 1
    - Creating M2V for VTS_20 segment 0
    - Creating M2V for VTS_21 segment 0
    - Creating M2V for VTS_21 segment 1
    - Extracting STILLS for VTS_22 segment 0
    - Extracting STILLS for VTS_23 segment 0
    - Extracting STILLS for VTS_24 segment 0
    - Extracting STILLS for VTS_25 segment 0
    - Extracting STILLS for VTS_26 segment 0
    - Extracting STILLS for VTS_27 segment 0
    [10:08:33] Phase II ENCODING completed in 15 minutes.
    [10:08:33] 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - 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
    - 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_07_0.IFO
    - Updating TMAP table...
    - Processing VTS_08
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_08_0.IFO
    - Updating TMAP table...
    - Processing VTS_09
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_09_0.IFO
    - Updating TMAP table...
    - Processing VTS_10
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_10_0.IFO
    - Updating TMAP table...
    - Processing VTS_11
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_11_0.IFO
    - Updating TMAP table...
    - Processing VTS_12
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_12_0.IFO
    - Updating TMAP table...
    - Processing VTS_13
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_13_0.IFO
    - Updating TMAP table...
    - Processing VTS_14
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_14_0.IFO
    - Updating TMAP table...
    - Processing VTS_15
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_15_0.IFO
    - Updating TMAP table...
    - Processing VTS_16
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_16_0.IFO
    - Updating TMAP table...
    - Processing VTS_17
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_17_0.IFO
    - Updating TMAP table...
    - Processing VTS_18
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_18_0.IFO
    - Updating TMAP table...
    - Processing VTS_19
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_19_0.IFO
    - Updating TMAP table...
    - Processing VTS_20
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_20_0.IFO
    - Updating TMAP table...
    - Processing VTS_21
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_21_0.IFO
    - Updating TMAP table...
    - Processing VTS_22
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_22_0.IFO
    - Updating TMAP table...
    - Processing VTS_23
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_23_0.IFO
    - Updating TMAP table...
    - Processing VTS_24
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_24_0.IFO
    - Updating TMAP table...
    - Processing VTS_25
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_25_0.IFO
    - Updating TMAP table...
    - Processing VTS_26
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_26_0.IFO
    - Updating TMAP table...
    - Processing VTS_27
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_27_0.IFO
    - Updating TMAP table...
    - Correcting VTS Sectors...
    - Building ISO Image...
    - ISO Image successfully created.
    [10:18:02] Phase III, REBUILD completed in 10 minutes.

    Done.
    [10:18:02] PREPARE/ENCODE/REBUILD completed in 27 min.
     
    cincyrob, Jul 15, 2009
    #113
  14. PCH_Dude

    PCH_Dude Member

    Joined:
    Apr 15, 2009
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    16
    27 minutes for an 8GB movie, that's insanely fast! It takes me on average 225 minutes to complete movies that are about 7GB in size.

    I use:
    DVD Rebulder 0.98.2 (Freeware) and HCencoder 024.
    My system:
    Intel Core 2 Duo T8100 2.1GHZ
    4GB DDR2 RAM
    320GB 5400RPM w/ 100GB free space.

    Is there something wrong here, can I make this go any faster?

    Excerpt:

    [17:20:43] One Click encoding activated...
    -----------------
    [17:20:43] Phase I, PREPARATION started.
    - VTS_02: 3,110,569 sectors.
    -- Scanning and writing .D2V file
    -- Processed 251,560 frames.
    -- Building .AVS and .ECL files
    - Reduction Level for DVD-5: 64.2%
    - Overall Bitrate : 2,866Kbs
    - Space for Video : 3,671,168KB
    - HIGH/LOW/AVERAGE Cell Bitrates: 2,868/2,864/2,866 Kbs
    [17:27:36] Phase I, PREPARATION completed in 7 minutes.

    [17:27:36] Phase II ENCODING started...
    ...

    [20:41:14] Phase II ENCODING completed in 194 minutes.
    ...

    [20:41:14] Phase III, REBUILD started.
    - Copying IFO, BUP, and unaltered files...

    [21:03:34] Phase III, REBUILD completed in 22 minutes.
    ...

    Done.
    [21:03:34] PREPARE/ENCODE/REBUILD completed in 223 min.
     
    PCH_Dude, Jul 17, 2009
    #114
  15. Sophocles

    Sophocles Senior member

    Joined:
    Mar 1, 2003
    Messages:
    5,953
    Likes Received:
    66
    Trophy Points:
    128
    The physical size of a movie has nothing to do with encode speeds. Provided that all settings are the same on a specific DVD movie the determining factor in encode times has more to do with the number of frames in the movie. Encoders work video frame by frame so the length of the movie will affect the outcome more. Physical size also involves sound tracks which are generally not reencoded. Some DVDs have several sound tracks which can increase the storage size considerably and of which all but one are removed. If a movie contains an LPCM or DTS sound tracks even more storage is required. If you want to compare reencode speeds of DVDs then you will need to use the same DVD and version because a Director's cut will differ in size to a pre-release. Make all things equal and then compare.
     
    Sophocles, Jul 17, 2009
    #115
  16. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    as Soph stated ya kinda need to use the same dvd to judge this by. hence i will be doing twin towers again and i will post my results. i am kinda curious as to how my new Q9550 will compare to my old E8400 that i did up above????
     
    cincyrob, Jul 17, 2009
    #116
  17. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    well this isnt LOR two towers that will be later today when i do that. but look at this puppy here. this is about 7.3gb movie after taking out the junk i didnt want. did this one is some nice time!!!!!!

    [09:10:49] One Click encoding activated...
    -----------------
    [09:10:49] Phase I, PREPARATION started.
    - DVD-RB v1.26.0
    - AVISYNTH 2.5.6.0
    - HC v0.21.0.0 encoder selected
    - "Steal Space from Extras" mode (50%) is enabled.
    - "Movie and Menus Only" mode is enabled.
    - Source: NEW IN TOWN
    - VTS_01: 2,608,715 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 139,385 frames.
    -- Building .AVS and .ECL files
    - VTS_02: 351,867 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 32,570 frames.
    -- Building .AVS and .ECL files
    - VTS_03: 118,100 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 10,910 frames.
    -- Building .AVS and .ECL files
    - VTS_04: 150,168 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 13,905 frames.
    -- Building .AVS and .ECL files
    - VTS_05: 286,702 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 26,979 frames.
    -- Building .AVS and .ECL files
    - VTS_06: 32,247 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,985 frames.
    -- Building .AVS and .ECL files
    - VTS_07: 36,285 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 3,353 frames.
    -- Building .AVS and .ECL files
    - VTS_08: 26,397 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 2,450 frames.
    -- Building .AVS and .ECL files
    - VTS_09: 15,794 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1,463 frames.
    -- Building .AVS and .ECL files
    - VTS_10: 1,810 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 440 frames.
    -- Building .AVS and .ECL files
    - VTS_11: 7,477 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 558 frames.
    -- Building .AVS and .ECL files
    - VTS_12: 1,395 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 275 frames.
    -- Building .AVS and .ECL files
    - VTS_13: 7,477 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 558 frames.
    -- Building .AVS and .ECL files
    - VTS_14: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_15: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_16: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_17: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_18: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - VTS_19: 4 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 1 frames.
    -- Building .AVS and .ECL files
    - Reduction Level for DVD-5: 56.2%
    - Overall Bitrate : 3,845/3,076Kbs
    - Space for Video : 3,693,394KB
    - Movie improvement from extra reduction = 21.3%
    - Blanking all EXTRA Segments
    -- Feature before/after: 4,411 / 5,304 Kbs
    [09:12:29] Phase I, PREPARATION completed in 2 minutes.
    [09:12:29] Phase II ENCODING started
    - Extracting Video 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
    - Extracting Video for VTS_01 segment 26
    - Extracting Video for VTS_01 segment 27
    - Creating M2V for VTS_02 segment 0
    - Creating M2V for VTS_02 segment 1
    - 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_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
    - Creating M2V for VTS_05 segment 9
    - Creating M2V for VTS_05 segment 10
    - Creating M2V for VTS_05 segment 11
    - Creating M2V for VTS_05 segment 12
    - Creating M2V for VTS_06 segment 0
    - Creating M2V for VTS_06 segment 1
    - Creating M2V for VTS_07 segment 0
    - Creating M2V for VTS_07 segment 1
    - Creating M2V for VTS_08 segment 0
    - Creating M2V for VTS_08 segment 1
    - Creating M2V for VTS_09 segment 0
    - Creating M2V for VTS_09 segment 1
    - Creating M2V for VTS_10 segment 0
    - Creating M2V for VTS_11 segment 0
    - Creating M2V for VTS_12 segment 0
    - Creating M2V for VTS_13 segment 0
    - Extracting STILLS for VTS_14 segment 0
    - Extracting STILLS for VTS_15 segment 0
    - Extracting STILLS for VTS_16 segment 0
    - Extracting STILLS for VTS_17 segment 0
    - Extracting STILLS for VTS_18 segment 0
    - Extracting STILLS for VTS_19 segment 0
    [09:23:38] Phase II ENCODING completed in 11 minutes.
    [09:23:39] 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - 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
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - 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
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_07_0.IFO
    - Updating TMAP table...
    - Processing VTS_08
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_08_0.IFO
    - Updating TMAP table...
    - Processing VTS_09
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Rebuilding seg 1 VOBID 1 CELLID 2
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_09_0.IFO
    - Updating TMAP table...
    - Processing VTS_10
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_10_0.IFO
    - Updating TMAP table...
    - Processing VTS_11
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_11_0.IFO
    - Updating TMAP table...
    - Processing VTS_12
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_12_0.IFO
    - Updating TMAP table...
    - Processing VTS_13
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_13_0.IFO
    - Updating TMAP table...
    - Processing VTS_14
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_14_0.IFO
    - Updating TMAP table...
    - Processing VTS_15
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_15_0.IFO
    - Updating TMAP table...
    - Processing VTS_16
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_16_0.IFO
    - Updating TMAP table...
    - Processing VTS_17
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_17_0.IFO
    - Updating TMAP table...
    - Processing VTS_18
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_18_0.IFO
    - Updating TMAP table...
    - Processing VTS_19
    - Reading/processing TMAP table...
    - Rebuilding seg 0 VOBID 1 CELLID 1
    - Updating NAVPACKS for VOBID_01
    - Updated VTS_C_ADT.
    - Updated VTS_VOBU_ADMAP.
    - Updated IFO: VTS_19_0.IFO
    - Updating TMAP table...
    - Correcting VTS Sectors...
    [09:31:51] Phase III, REBUILD completed in 8 minutes.

    Done.
    [09:31:51] PREPARE/ENCODE/REBUILD completed in 21 min.

    encodeing only took 11 mins that is awesome. this is nice time frame for this but i am wanting to do two towers badly if i can cut that time in half from my E8400 times(48 min) that would make it 24mins for the top dog of movies to rebuild.... that i would brag about...lol
     
    cincyrob, Jul 18, 2009
    #117
  18. Sophocles

    Sophocles Senior member

    Joined:
    Mar 1, 2003
    Messages:
    5,953
    Likes Received:
    66
    Trophy Points:
    128
    I would like to make another suggestion regarding posting results. Unless one is experiencing difficulties there is no need to post the entire log, and besides who's going to read it all anyway. Also a log can be edited in Notepad. All that one really needs to verify their results is a screenshot of prepare/encode/rebuild at the end since it gives the total time to do all three and can't be edited. I haven't done many standard DVD's in quite a while but here's an example.


    [​IMG]


    Now if you guys really want to test some speeds come on over to the BD RB thread.
     
    Sophocles, Jul 18, 2009
    #118
  19. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    [11:27:36] Phase I, PREPARATION started.
    - DVD-RB v1.26.0
    - AVISYNTH 2.5.6.0
    - HC v0.21.0.0 encoder selected
    - "Steal Space from Extras" mode (50%) is enabled.
    - "Movie and Menus Only" mode is enabled.
    - Source: TWO_TOWERS
    - VTS_01: 3,720,941 sectors.
    -- Scanning and writing .D2V & .AVS files
    -- Processed 258,043 frames.
    -- Building .AVS and .ECL files
    - Reduction Level for DVD-5: 51.3%
    - Overall Bitrate : 3,192/2,553Kbs
    - Space for Video : 3,354,688KB
    - Blanking all EXTRA Segments
    [11:29:21] Phase I, PREPARATION completed in 2 minutes.
    [11:53:13] Phase II ENCODING completed in 24 minutes.
    [11:53:14] Phase III, REBUILD started.
    [12:02:40] Phase III, REBUILD completed in 9 minutes.

    Done.
    [12:02:40] PREPARE/ENCODE/REBUILD completed in 35 min.


    well it isnt what i thought i would get but i did cut 13 mins from my previous times.
     
    cincyrob, Jul 18, 2009
    #119
  20. Sophocles

    Sophocles Senior member

    Joined:
    Mar 1, 2003
    Messages:
    5,953
    Likes Received:
    66
    Trophy Points:
    128
    Rob

    A change in processor to an updated version is going to give some better results but, having 2 or 4 cores really only makes a difference if the applications can use them.

    Avisynth is a single threaded application to it will run only as fast as the fastest single core available. The rebuild portion is also a single threaded process so again only 1 of your 4 cores will get used. The encoding part however is a different story and it's where you have the potential to see some real speed gains, but even that depends on the encoder. Cinema Craft Encoder used by RB can only run two threads at once. A third thread however occurs probably in response to a concurrent application running at the same time. HC encoder can use all 4 cores but it's not optimized to do so and this has the effect of speeding things up for those using HC encoder but not as much as one would like. So the fact that you're not getting the speeds that you desire is purely a matter of how effectively the software used can communicate with your processors cores.
     
    Sophocles, Jul 18, 2009
    #120
Page 6 of 7

Share This Page