Post your DISC quality scans here 2

Litescribe rob? I don't litescribe at all. Its merely coincidence that my drives support it. And since its done extremely well, and is a solid drive, I don't regret purchasing the iHAS424, which is a 7241S by the way Its quite possibly a better drive than the 7200S. I buy the litescribe drives because its logical to assume, they're built to be tough, given the extremely long burning times This may be flawed logic, but since I have a high success rate with my burners...

 

This is why we call Russ "the ODD KILLER"!!! ROFLmao!!!!

 

not saying you do litescribes, just that the last couple drives you have gotten have been litescribe..lol and i like your logic as to why.. might give that a try myself next drive out.

here is a couple i jsut did. i got out some older 8x-r TY's value line. you can tell a big difference in these from the latest ive used.

 

ok guys. i just used dvdrebuilder for the first time in awhile. and used HC encoder. that is the wa to go if you have a Quad core CPU. totally uses all 4 cores to the max.
i did alvin and the chipmunks the squeakqual. 7.34gb in size. only took 19mins and that includes makeing a ISO to burn with using nero cd/dvd speed. here is the log will have scan shortly.

[12:55:04] Phase I, PREPARATION started.
- DVD-RB v1.26.0
- AVISYNTH 2.5.8.0
- HC v0.23.0.0 encoder selected
- "Steal Space from Extras" mode (50%) is enabled.
- "Movie and Menus Only" mode is enabled.
- Source: ALVIN_CHIMPUNKS_THE_SQUEAKQUEL
- VTS_01: 196 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 45 frames.
-- Building .AVS and .ECL files
- VTS_02: 2,617,252 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 127,374 frames.
-- Building .AVS and .ECL files
- VTS_03: 262,901 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 17,177 frames.
-- Building .AVS and .ECL files
- VTS_04: 221,555 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 16,242 frames.
-- Building .AVS and .ECL files
- VTS_05: 29,978 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2,438 frames.
-- Building .AVS and .ECL files
- VTS_06: 199,484 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 13,563 frames.
-- Building .AVS and .ECL files
- VTS_07: 3,882 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 271 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 60.4%
- Overall Bitrate : 4,765/3,812Kbs
- Space for Video : 3,437,130KB
- Movie improvement from extra reduction = 15.3%
- Blanking all EXTRA Segments
-- Feature before/after: 4,676 / 5,436 Kbs
[12:56:42] Phase I, PREPARATION completed in 1 minutes.
[12:56:42] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Creating M2V for VTS_02 segment 3
- Creating M2V for VTS_02 segment 4
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Creating M2V for VTS_02 segment 7
- Creating M2V for VTS_02 segment 8
- Creating M2V for VTS_02 segment 9
- Creating M2V for VTS_02 segment 10
- Creating M2V for VTS_02 segment 11
- Creating M2V for VTS_02 segment 12
- Creating M2V for VTS_02 segment 13
- Creating M2V for VTS_02 segment 14
- Creating M2V for VTS_02 segment 15
- Creating M2V for VTS_02 segment 16
- Creating M2V for VTS_02 segment 17
- Creating M2V for VTS_02 segment 18
- Creating M2V for VTS_02 segment 19
- Creating M2V for VTS_02 segment 20
- Creating M2V for VTS_02 segment 21
- Creating M2V for VTS_02 segment 22
- Creating M2V for VTS_02 segment 23
- Creating M2V for VTS_02 segment 24
- Creating M2V for VTS_02 segment 25
- Creating M2V for VTS_02 segment 26
- Creating M2V for VTS_02 segment 27
- Creating M2V for VTS_02 segment 28
- Creating M2V for VTS_02 segment 29
- Creating M2V for VTS_02 segment 30
- Creating M2V for VTS_02 segment 31
- Creating M2V for VTS_02 segment 32
- Creating M2V for VTS_02 segment 33
- Creating M2V for VTS_02 segment 34
- Extracting STILLS for VTS_02 segment 35
- Extracting STILLS for VTS_02 segment 36
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Creating M2V for VTS_03 segment 3
- Creating M2V for VTS_03 segment 4
- Creating M2V for VTS_03 segment 5
- Creating M2V for VTS_03 segment 6
- Creating M2V for VTS_03 segment 7
- Creating M2V for VTS_03 segment 8
- Creating M2V for VTS_03 segment 9
- Creating M2V for VTS_03 segment 10
- Creating M2V for VTS_03 segment 11
- Extracting STILLS for VTS_03 segment 12
- Extracting STILLS for VTS_03 segment 13
- Extracting STILLS for VTS_03 segment 14
- Extracting STILLS for VTS_03 segment 15
- Extracting STILLS for VTS_03 segment 16
- Extracting STILLS for VTS_03 segment 17
- Extracting STILLS for VTS_03 segment 18
- Extracting STILLS for VTS_03 segment 19
- Extracting STILLS for VTS_03 segment 20
- Extracting STILLS for VTS_03 segment 21
- Extracting STILLS for VTS_03 segment 22
- Extracting STILLS for VTS_03 segment 23
- Extracting STILLS for VTS_03 segment 24
- Extracting STILLS for VTS_03 segment 25
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
- Creating M2V for VTS_04 segment 2
- Extracting STILLS for VTS_04 segment 3
- Extracting STILLS for VTS_04 segment 4
- Extracting STILLS for VTS_04 segment 5
- Extracting STILLS for VTS_04 segment 6
- Creating M2V for VTS_05 segment 0
- Extracting STILLS for VTS_05 segment 1
- Extracting STILLS for VTS_05 segment 2
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Creating M2V for VTS_06 segment 3
- Creating M2V for VTS_06 segment 4
- Extracting STILLS for VTS_06 segment 5
- Creating M2V for VTS_07 segment 0
- Extracting STILLS for VTS_07 segment 1
[13:06:48] Phase II ENCODING completed in 10 minutes.
[13:06:48] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- 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_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
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 19 VOBID 2 CELLID 1
- Rebuilding seg 20 VOBID 2 CELLID 2
- Rebuilding seg 21 VOBID 2 CELLID 3
- Rebuilding seg 22 VOBID 2 CELLID 4
- Rebuilding seg 23 VOBID 2 CELLID 5
- Rebuilding seg 24 VOBID 2 CELLID 6
- Rebuilding seg 25 VOBID 2 CELLID 7
- Rebuilding seg 26 VOBID 2 CELLID 8
- Rebuilding seg 27 VOBID 2 CELLID 9
- Rebuilding seg 28 VOBID 2 CELLID 10
- Rebuilding seg 29 VOBID 2 CELLID 11
- Rebuilding seg 30 VOBID 2 CELLID 12
- Rebuilding seg 31 VOBID 2 CELLID 13
- Rebuilding seg 32 VOBID 2 CELLID 14
- Rebuilding seg 33 VOBID 2 CELLID 15
- Rebuilding seg 34 VOBID 2 CELLID 16
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 35 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 36 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- 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
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 11 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 12 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 13 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 14 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 15 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 16 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 17 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 18 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_09
- Rebuilding seg 19 VOBID 10 CELLID 1
- Updating NAVPACKS for VOBID_10
- Rebuilding seg 20 VOBID 11 CELLID 1
- Updating NAVPACKS for VOBID_11
- Rebuilding seg 21 VOBID 12 CELLID 1
- Updating NAVPACKS for VOBID_12
- Rebuilding seg 22 VOBID 13 CELLID 1
- Updating NAVPACKS for VOBID_13
- Rebuilding seg 23 VOBID 14 CELLID 1
- Updating NAVPACKS for VOBID_14
- Rebuilding seg 24 VOBID 15 CELLID 1
- Updating NAVPACKS for VOBID_15
- Rebuilding seg 25 VOBID 16 CELLID 1
- Updating NAVPACKS for VOBID_16
- 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
- Rebuilding seg 2 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 3 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 4 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 5 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 6 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- 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
- 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_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
- Rebuilding seg 2 VOBID 1 CELLID 3
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 3 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 4 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 5 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- 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
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- Removing DVD files
- ISO Image successfully created.
[13:14:17] Phase III, REBUILD completed in 8 minutes.

Done.
[13:14:17] PREPARE/ENCODE/REBUILD completed in 19 min.

 

first i cant login here and then double posting... i do not like this new setup.
sorry bout that guys.. as if its my fault.lol

 

Rob, you double posted a VERY long post

And actually, in my experience, CCE can utilize less of your CPU, and finish in almost the same time as the HC encoder. CCE is almost faster using less potential. Perhaps that's not everyones experience though.

Plus I find CCE to be slightly better quality. But you can barely see the difference so...

 

well the fastest i have ever done 1 with CCE was 23min i know 4 mins isnt alot but it is 4 mins less. here is the crt and scan from that disc.. check this out the disc wont play. i had nero hang up on me when it started. so i stopped the process and restarted.. i thought the disc was bad but it showed ok, so i went ahead and burnt it.. this is what it looks like.. notice the begining PIE's/



going to redo it and see what it does.

 

Oman7,
I couldn't agree more! I've tried both, and while the HC encoder is slightly faster than the CCE, it's not quite as good, quality wise. Typically, mine takes somewhere between 20 and 30 minutes, depending on the size of the DVD and the number of encoded frames.

Russ

 

Rob,
I swear, I don't know who is worse, You or Will! All we need to see is the Preparation time, the Encode time and the final result. Talk about Blah, Blah, Blah! LOL!! In all fairness, you did leave out your shoe size though! ROFLMSOAO!!

Best Regards,
Russ

 

well i do tend to post everything cause there is some members here that look at it all(loco for 1) and they do inform me of newer update to each part of dvdrebuilder...

 

Rob,
See, now I know why! LOL!! Just funnin with ya! I knew there had to be a reasonable explanation!

Best Regards,
Russ

 

I've finally reached a resolution for my Lite-On iHAS 124-04 drives. The drives do not burn/play consistently, and the tray mechanism sometimes works well, and other times it doesn't. Sometimes it flies open, and other times it goes "Clunk", pauses for a couple of seconds, and then opens very slowly. Sometimes it works normal, but that is getting rarer and rarer!

I spoke to Lite-On, and all they will do is replace them, so that was out. I took the matter up with Newegg, and they have agreed to take both of them back for a full refund. I find it interesting that after I explained the problems, the guy said that "He knew where this is going", and offered me a full refund on them. That makes it pretty obvious to me that these drives have been very troublesome for a number of customers.

I'm going to replace them with Two Lite-On iHAS-324-98 drives.
http://www.newegg.com/Product/Product.aspx?Item=N82E16827106334

If anyone has a better recommendation, I'm all ears!

Best Regards,
Russ

 

Burner or ripper? It matters to me...

I only trust my lite-ons for ripping. And my optiarcs are excellent burners. But I haven't bought a new burner in a long time. My luck with my burners has been highly unusual I think I owe it to the Haf932 case. It keeps literally everything cool!

 

Oman7,
See, that's the thing. Once I started buying Optiarcs, I never had a problem with them, except one, and it failed when a Cheap PSU went out. The only drive series they've ever made that I've never owned was the 7200s. Even the 7220s worked well, but just weren't very long lived, as they lasted only a little over a year. Same with the 7240s!

I'm impressed with the quality results Rob has posted with his iHAS324 drives, and it is a true Lite-On drive, which will do exactly what I am looking for it to do. I have a spare AD7240s and a so-so AD7220s, so I'm going to send them back to Newegg. Once I get the Credit, I'll order a couple of new drives. Based on the results I've seen posted here for the iHAS324s drives, it's the Front runner, at the moment.

Best Regards,
Russ

 

Think i'll buy one myself tonight. If I can locate the exact model

 

Here's a burn from my iHAS424(7241S). Typical burn coming from that verbatim batch. This is a taiwan batch. Not to be confused with the united arab emir discs, which are freakishly good
12X via imgburn.

 

Here's a nice scan I did today. Movie played flawlessly. One of these days I'll get more 98s-close.

 

BTW guys that 324 Lite-On is down to 23.99 at newegg

 

If you had my verbs, you just might get several 98's

 

Ordered It Thanks!