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

Post your DISC quality scans here 2

Discussion in 'Nero discussion' started by cincyrob, Jul 27, 2007.

Page 131 of 224
  1. garmoon

    garmoon Regular member

    Joined:
    Oct 7, 2004
    Messages:
    3,971
    Likes Received:
    0
    Trophy Points:
    46
    In keeping with the long streaks of 95s, here is the very first burn of my optiacr-NEC 7240S, with book typing, firmware from Liggy 1.01bt-rpc1 on so-so medium Ritek F-16 +R burned at 16X with ImgBurn and bit set, of an ISO, made from a back-up, in under 6mins.

    [​IMG]
    Shot at 2009-07-11

    I've had this drive for months though, without bit setting fw. It was too hot to do anything outside today. So I played with drive (Optiarc7240S)that I have had but never used until I got the book type fw today.
     
    Last edited: Jul 12, 2009
    garmoon, Jul 11, 2009
    #2601
  2. garmoon

    garmoon Regular member

    Joined:
    Oct 7, 2004
    Messages:
    3,971
    Likes Received:
    0
    Trophy Points:
    46
    OK Here's a scan on the best TY T02 medium I have, Burned At X8 in Nero Express (not on-the-fly). Seems to love this medium on it's first encounter. I'll take em all this good.

    [​IMG]
    Shot at 2009-07-12
     
    garmoon, Jul 12, 2009
    #2602
  3. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    nice burns moony. im getting one of these after i get my Q9550 tuesday.
     
    cincyrob, Jul 12, 2009
    #2603
  4. omegaman7

    omegaman7 Senior member

    Joined:
    Feb 12, 2008
    Messages:
    6,955
    Likes Received:
    2
    Trophy Points:
    118
    Ha ha! Speaking of Yuden T02's! 8X T02 burned at 12X on iHAP 422. Take this every time :D
    [​IMG]
     
    omegaman7, Jul 14, 2009
    #2604
  5. garmoon

    garmoon Regular member

    Joined:
    Oct 7, 2004
    Messages:
    3,971
    Likes Received:
    0
    Trophy Points:
    46
    @omega

    sometimes I think my Litey 20A1S can burn as well as the Nec-Optis.
     
    garmoon, Jul 14, 2009
    #2605
  6. omegaman7

    omegaman7 Senior member

    Joined:
    Feb 12, 2008
    Messages:
    6,955
    Likes Received:
    2
    Trophy Points:
    118
    Indeed Garmoon. My LH-20A1H does about as good as the optiarcs. Lite-on is far from slouch compared to optiarcs. I'll take them both everyday of the week. Though I don't know about ripping with the optiarcs. I think at least one of them flaked out in that respect. Which is fine! I bought them for burning, not reading. My LH-20A1H and my Sammy's are my readers.

    Though one of the Sammy's may be on the fritz! I plugged one of my brand new movies in to back it up today(Haunting in Connecticut), and it had trouble reading it right at the get go. I could hear it trying, but...NO GO! At first I thought the encryption was causing it. But I stuck it in my other Sammy and then it was fine. Prime example why you never buy just one burner to judge. I try to buy at least 2 identical burners now. No one burner is exactly the same as another.
     
    omegaman7, Jul 15, 2009
    #2606
  7. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    oh how i wish i still had my 20A1S and my 18A1P those were 2 awesome ass drives.and yes i agree they burnt as well as any other drive i have seen, that includes the beloved Benq 1650 and the plextor 716. nothing against those drives but if i had to do it over again i would still get the 20A1S,18A1P. now thats just me...lol

    ok to scans. here is a scan of a ATIVA 16x+r(cmc mag) printable i got these from office depot yesterday. they were on clearance. a 10 pack with jewel case for .89c i couldnt pass them up. i bought all 8 packs they had. TBH this isnt a bad scan for these.

    [​IMG]

    i should do 1 more burn/scan cause this will be the last one my E8400 will see for some time going to install the new Q9550 after this post, would be a shame the last thing the e8400 did is a CMC MAG..lol

    actually i will do a 8x-r TY and post back before the rebuild
     
    cincyrob, Jul 15, 2009
    #2607
  8. theonejrs

    theonejrs Senior member

    Joined:
    Aug 3, 2005
    Messages:
    7,895
    Likes Received:
    1
    Trophy Points:
    116
    Rob,
    Best of luck with the Q9550!

    Russ
     
    theonejrs, Jul 15, 2009
    #2608
  9. greensman

    greensman Regular member

    Joined:
    Dec 7, 2004
    Messages:
    3,275
    Likes Received:
    0
    Trophy Points:
    46
    I have officially decided I don't like you any more!!! Well unless you send me one of those Q9550 for whichever special occasion you feel is worthy. :D

    J/K... hehehe. GOOD LUCK with that install and NEW cpu. ;)

    add: NICE scan too... and the CMC MAG AM3 discs aren't that bad are they?? :)
     
    greensman, Jul 15, 2009
    #2609
  10. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    thats cmc mag mo1...lol
    man running dvd-rebuild right now useing HC Encoder doing a 8.1gb(paul blart mall cop) it has only been runnin a few mins, and is allready 54.4% done...WOW

    heres a few pics of hte new toys.
    [​IMG]
    [​IMG]
    [​IMG]
    [​IMG]

    here is a link to the new build thread. im sure most have seen it allready..lol
    http://forums.afterdawn.com/thread_jump.cfm/683586/4755492

    like a kid in a candy store..lol
     
    cincyrob, Jul 15, 2009
    #2610
  11. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    WOW 27 mins for a 8gb movie!!!!!!!!!!!!!!!!!!!!!!

    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
    #2611
  12. greensman

    greensman Regular member

    Joined:
    Dec 7, 2004
    Messages:
    3,275
    Likes Received:
    0
    Trophy Points:
    46
    Yep... backing to HATIN!!!
     
    greensman, Jul 15, 2009
    #2612
  13. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    Nice one Rob.
    However you could do with a few changes ~
    DVD-RB is now at 1.28.2, i guess your version is fine for you but you could update to the latest, i'm guessing there's nothing left to fix in DVD Rebuilder hence my guess is that it'll stay at 1.28.2 now, plus i guess all development work is geared towards BD Rebuilder instead.
    HC Encoder is now at 0.23, again 0.21 is fine but it'd be daft not to update it
    AVISynth is at 2.5.8.0 now, can't remember but i think that this is updated along with the DVD-RB install, though it can be updated separately.
    I can't say i've ever had any problems with any versions of DVD-RB or HC Encoder, only with Pirates of the Caribbean World's End, and that was DVDFab's fault, not DVD-RB.

    Finally, why on earth is Paul Blart 8GB ?. I see you only have main movie and menu's listed but i don't recall seeing any movie over say 6GB for the longest time, it's not like the movie is packed with CGI or other video-intensive material, that's very strange.

    Other than that, 27 minutes is awesome, i think that's a record on Afterdawn now :)
    ..how's about updating this thread here ~ http://forums.afterdawn.com/thread_view.cfm/335628
     
    creaky, Jul 15, 2009
    #2613
  14. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    well i just finished Paul Blart, and your right it dont seem right it being 8.1gb. but when i used anydvdripper to rip it to my hdd it showed it as 8.1gb. but once i ripped it to my hdd it only was 7.05gb and yes i only did movie and menu heck with all that other junk..lol

    ill have to get to doing some updates on dvd rebuilder stuff. if at 2.83ghz it will do it in 27 mins wonder what 3.83ghz will get me? 21min????lol SMOKIN!!!!!!!!!!!. gonna ripp and rebuild NEW IN TOWN for the wifey.

    ok here we go. in anydvd it shows new in town as 8.1gb heres a screen of it.

    [​IMG]
    ill let ya know what it says once ripped to hdd.
     
    Last edited: Jul 15, 2009
    cincyrob, Jul 15, 2009
    #2614
  15. omegaman7

    omegaman7 Senior member

    Joined:
    Feb 12, 2008
    Messages:
    6,955
    Likes Received:
    2
    Trophy Points:
    118
    My phenom II does 20 - 25 minutes all the time :p

    Ok...perhaps not ALL the time LOL. Ive seen it at least twice though.
     
    Last edited: Jul 15, 2009
    omegaman7, Jul 15, 2009
    #2615
  16. garmoon

    garmoon Regular member

    Joined:
    Oct 7, 2004
    Messages:
    3,971
    Likes Received:
    0
    Trophy Points:
    46
    Not that I know anything about DVDRebuilder, but Paul Blart Mall Cop, the disc I had, was an anydvd and NeroRecode burn, movie only, no menus with Recode, was no compression 100%! Maybe I had an unusual disc. Nice pc tho, Rob. I'm more in the the jealous mode rather than all that hatin' like Mr Greenjeans. Congrats a new afterdawn record!
     
    garmoon, Jul 15, 2009
    #2616
  17. cincyrob

    cincyrob Active member

    Joined:
    Feb 15, 2006
    Messages:
    4,201
    Likes Received:
    0
    Trophy Points:
    96
    i agree 100% about paul blart if you look at that log it only shows the movie and menu part at about 6gb. im gonna have t oget twin towers again and do that again. thats the true test. if i have a so called record i want it to be legit. cant have peeps saying my cpu is on roids...lmao
     
    cincyrob, Jul 15, 2009
    #2617
  18. omegaman7

    omegaman7 Senior member

    Joined:
    Feb 12, 2008
    Messages:
    6,955
    Likes Received:
    2
    Trophy Points:
    118
    LOL! Roids eh? ;)

    30 - 35 minutes is fairly consistent for me. Which is a huge twist from my 60-80 minute dual core. And my quad only averages 50-60% usage!!! Such a shame...if it could only use the rest of that potential. Totally not complaining here. 30 minutes is very acceptable at the moment. But I generally use CCE, not HC. Something about HC turned me off. Don't recall what it was. I'll post another scan soon.
     
    omegaman7, Jul 15, 2009
    #2618
  19. theonejrs

    theonejrs Senior member

    Joined:
    Aug 3, 2005
    Messages:
    7,895
    Likes Received:
    1
    Trophy Points:
    116
    Nope! I posted a large one (7.6GB) a while back that was 24 minutes, and Oman7 has beaten that!

    Best Regards,
    Russ
     
    theonejrs, Jul 15, 2009
    #2619
  20. creaky

    creaky Moderator Staff Member

    Joined:
    Jan 14, 2005
    Messages:
    27,900
    Likes Received:
    1
    Trophy Points:
    96
    Good stuff. It's been a long time since i backed up any new titles though (job market woes), i just backup old ones now.
     
    creaky, Jul 15, 2009
    #2620
Page 131 of 224

Share This Page