I have two dvd burners on computer and was wondering if i can burn straight from disc to disc
really? doesnt clovedvd copy it to a temp file first, then burn it, then delete the temp files? so how would that be different than ripping it first? does it actually copy on the fly. not that its a big deal i guess just curious.
really? doesnt clovedvd copy it to a temp file first, then burn it, then delete the temp files?
Why? Assuming you have quality drives and media and a clean system without extraneous processes running then copy on the fly should not produce poor quality burns.Yeah, you can using "Write Existing Data", but that's a great way to produce poor quality burns.
Why? Assuming you have quality drives and media and a clean system without extraneous processes running then copy on the fly should not produce poor quality burns.
Makes sense. I have a burner on a SATA (Master) channel and a burner (Master) and a rom (slave) on IDE - they are all UDMA5 devices. I wouldn't try using the devices sharing the IDE channel, but I might try using both masters as an experiment. I have a fast and clean system and use quality media (Singapore Verbatim). Saving 15 minutes sounds attractive (but not at the expense of quality burns)No. It can, especially when using ide/atapi burners on the same ide channel. Only one device on any ide channel can be active at one time. As such, this increases the likelihood of engaging buffer underrun protection in your burner if the destination and source drives are on the same ide channel. Starting and stopping the burn process repeatedly is a great method for producing poor quality burns. What I described doesn't apply to Sata ODDs, but there's still a greater chance for errors to occur when burning on the fly.
but I might try using both masters as an experiment
LOL - max is 16x for my LG GGC-H20L SATA drive, 18x for my Pioneer 112 IDE drive, and that always gives iffy results in DvdInfoPro. 12x or 8x is enough even on MKM-004 Singapore Verbatim, I think, and only a couple of minutes slower because of CAV writingThat should be fine, provided you're not burning at 22x or something
On the fly from one disc to another?never had a bad burn (8x) with "write existing data".