Post your DISC quality scans here 2

bigwill68,

Not that I'm aware of! As far as I know Verbs are made by Mitsubishi, not ProDisk! I don't know of any other DVD manufacturer called MCC!

http://www.m-kagaku.co.jp/index_en.htm

Best Regards,
Russ

 

Well... Not the best first example of an MCC 003. But I guess it could be worse considering the iHAS424 (which is an Optiarc 7241S) is better at high speed burning, than lower speeds. I bet the LH-20A1H/S do a better job Probably even the 7200S.

 

MCC (Mitsubishi Chemical Corp) outsources manufacturing of some of their discs.... Prodisc and CMC MAG are 2 companies that I know produce discs for them.. they are made to MCC's standards and use their "methods" of production and chemicals.

I'll look for the link that addresses this but I'm 99.999% sure I'm right about this.

hth....

 

@GM

Have you seen these b4 greens? Would you think these are using the MCC Coating as well sense Windata disc's has it's hands in the cookie jar as well.I have some Windata's with MCC coating

Prodisc site

http://www.cdrdvdrmedia.com/prodisc-blank-dvd-r-media.html

Features:

•Certified by DVD Forum
•Adapts the same playback characteristics as a DVD-ROM disc.
•Ideal for high-volume data recording, archiving and video pre-mastering.
•High-performance long-life azo dye

they use Azo Dyes So is Mitsubishi Chemicals Corp Or Cyanine dye

Azo Dye

http://www.chm.bris.ac.uk/webprojects2002/price/azo.htm

Cyanine dye

http://www.mtarget.com/mtti/cyanines.html

who ready for science class?

@russ

your theory on the dvd rebuilder seprating the working path & the output path on 2 different drives maybe right.I just did 6.19gb in 22 mins.I don't know if that's the average time for a disc of that size in 2 passes but that's the fastest.Ive ever done.Lol. I got it setup like you now to see what happen's with bigger size movie next time around

[19:07:10] One Click encoding activated...
-----------------
[19:07:10] Phase I, PREPARATION started.
- DVD-RB v1.28.2
- AVISYNTH 2.5.8.0
- CCE 2.70.2.4 encoder selected.
- Source: THE OMEGA MAN 1971
- VTS_01: 2,223,882 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 145,937 frames.
-- Building .AVS and .ECL files
- VTS_02: 294,700 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 21,483 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 87.9%
- Overall Bitrate : 6,063/4,851Kbs
- Space for Video : 4,134,590KB
- HIGH/LOW/TYPICAL Bitrates: 5,767/1,178/4,851 Kbs
[19:08:23] Phase I, PREPARATION completed in 1 minutes.
[19:08:23] Phase II ENCODING started
- Extracting STILLS 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_02 segment 0
- Creating M2V for VTS_02 segment 1
[19:24:42] Phase II ENCODING completed in 16 minutes.
[19:24:42] 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
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Rebuilding seg 3 VOBID 3 CELLID 2
- Rebuilding seg 4 VOBID 3 CELLID 3
- Rebuilding seg 5 VOBID 3 CELLID 4
- Rebuilding seg 6 VOBID 3 CELLID 5
- Rebuilding seg 7 VOBID 3 CELLID 6
- Rebuilding seg 8 VOBID 3 CELLID 7
- Rebuilding seg 9 VOBID 3 CELLID 8
- Rebuilding seg 10 VOBID 3 CELLID 9
- Rebuilding seg 11 VOBID 3 CELLID 10
- Rebuilding seg 12 VOBID 3 CELLID 11
- Rebuilding seg 13 VOBID 3 CELLID 12
- Rebuilding seg 14 VOBID 3 CELLID 13
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 15 VOBID 4 CELLID 1
- Rebuilding seg 16 VOBID 4 CELLID 2
- Rebuilding seg 17 VOBID 4 CELLID 3
- Rebuilding seg 18 VOBID 4 CELLID 4
- Rebuilding seg 19 VOBID 4 CELLID 5
- Rebuilding seg 20 VOBID 4 CELLID 6
- Rebuilding seg 21 VOBID 4 CELLID 7
- Rebuilding seg 22 VOBID 4 CELLID 8
- Rebuilding seg 23 VOBID 4 CELLID 9
- Rebuilding seg 24 VOBID 4 CELLID 10
- Rebuilding seg 25 VOBID 4 CELLID 11
- Rebuilding seg 26 VOBID 4 CELLID 12
- Rebuilding seg 27 VOBID 4 CELLID 13
- Rebuilding seg 28 VOBID 4 CELLID 14
- Rebuilding seg 29 VOBID 4 CELLID 15
- Rebuilding seg 30 VOBID 4 CELLID 16
- Rebuilding seg 31 VOBID 4 CELLID 17
- Rebuilding seg 32 VOBID 4 CELLID 18
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 33 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 34 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[19:29:06] Phase III, REBUILD completed in 5 minutes.

Done.
[19:29:06] PREPARE/ENCODE/REBUILD completed in 22 min.


Check the source ( the omega man 1971) hint,hint, somebody's name here

 

LOL! I've been asked that before. If I chose my screen name because of that movie. I chose my screen name when I was on AOL, back in 2003 I believe. Possibly earlier. I chose it because I am the beginning and the end...LOL! Nah, I chose it to remind me that I could do anything that I set my mind to

 

Will,
Credit has to go to creaky, not me. He's the one who steered me to using three drives! I had only split it between the boot drive and a second physical hard drive before I decided on three drives! It's worth a about 2 to 3 minutes saved, on an average flick!

Russ

 

Been doing it since the start Its only logical to save time with multiple drives. If only one is used, then it has to read AND write at the same time. Hindering performance significantly...

 

Here's a burn done with smart burn. While much better than the one I tossed the other day, it's low in PI Errors, but very high in PI Failures!



Here's the same flick burned on a -R Verb. Same settings, same drive! Much higher PI Errors, but much lower PI Failures! I would call it a better scan!



I only forgot to turn off Book Type for the -R and burned the first one as a coaster! LOL!!

Russ

 

Lite-on's are best scanned at 4X. For comparison purposes though, I suppose 8X will work. You'll find that if you scan at a slower speed, it will find lower errors/failures. My LH-20A1H is getting kind of old. Sometimes, I'll get a very high spike right at the start. But if I try try try again, it goes away. Or scan at 2X. But I don't make a habit of scanning at THAT slow a speed LOL!

Ritek blew it for me though. I got an extremely ugly looking batch of CD's one time. Completely inexcusable.

 

Oman7,
I burn at 12x and scan at 8x. That's what has always worked best for me!

Russ

 

4X is simply a guideline for Lite-on's russ. Cdfreaks will confirm that. But it DOES amount to what works best for you as well

That's a strange error creaky. Never had that one occur...

another MCC 003 coming up. Not as good as I expected. But it is an aging burner

 

Rather unusual, that a 4x and 8x scan closely resemble one another. If they resembled each other more often, I might consider sticking with 8X. 4X is awfully slow LOL!
7200S 8X. This burner has seen a great deal of discs. When I first got it, I started to rely on it heavily LOL! It's quite possible that it's seen more than the 7200A's now. And i've had them longer...

 

@creaky..

I know you didn't ask for anything but that error is strange as Oman7 said.

I'd do a search at CDF for CK's edition of Nero CD/DVD Speed. It's 4.7.7.16 and will work with iHAS drives in case you have one of those Liteons. AFAIK the LG drives DON'T do a scan with Nero. Not a big deal as you have some Liteons I"m sure. Good luck to you if you choose to accept this mission.

 

U is a funny man!

 

If by "Wasting laser power" you mean wearing a burner out, Im glad to do it LOL! If a burner can't last a year, no matter what is done, and how it's used, it has no business archiving peoples precious data! The industry needs to take a lot more pride into the technology they're producing. Imagine if the FBI were to get a lemon. If it were the IRS it wouldn't bother me, but the FBI...LOL! Machines don't cause DOA's/RMA's. People do. If we put even a little more pride into our production, we'd start to see mankind at a peak of our evolution...

JM2C

 

Best one i've seen yet. Always did like those 7200A's. Verbatim tries soo hard, but they just can't beat TY

 

Here's an 8x burn I just finished. It's only 3.2GB but it's still a decent scan.



Right after I scanned it, the drive went belly up! It won't burn a DVD anymore. It burns the disk and finalizes it, but when you click OK, it locks up Nero. You can't even close the program until you remove the DVD from the burner. It will play, bit it won't record! Very strange. I even tried a couple of new data cables, and it does the same thing. I even replaced the firmware, but it still does the same thing!

Now if this don't beat all! Here's a burn made on the "Bad" drive at 12x and scanned at 8x.



Yet, it won't burn at 8x! Nero says the burn is complete, but when you click OK to continue, the drive sits there flickering, and locks up Nero until you eject the DVD! It's not playable!

Oman7,
Remember I said that mine works best burned at 12x and scanned at 8x. Well I was wrong! It works best burning at 12x and scanning at 4x! Not by a lot, but still better!



Why it does that burning at 8x, is beyond me! They burn fine at 8x in the other drive.

Russ

 

Ha ha! Not bad at all. This is from my other 7200A, 1Z2 Firmware @ 8X via Imgburn. Booktyped -Rom. Oddly, it took the BD/Dvd upscaler time to load the disc. At least 30 Sec. Much more than im used to. The only difference between this disc and the others is that this one is a MCC 003, where as the 004's load quicker. Now this could be an isolated incident. Other burns may work ok. The BD/Dvd upscaler im referring to is the BD-P1590 Samsung. Love that little devil So far, despite not officially supporting burned media, IT DOES! Including TY-R discs.