The following sections condense our experience in burning a lot of CDs in various environments.
The process of burning CDs can be smooth and reliable or a complete nightmare. Which it is depends on the entire system you use to burn CDs?processor, memory, operating system, configuration settings, background processes, hard disk type and fragmentation level, source CD-ROM drive and the source CD itself, CD-R(W) drive, firmware revision, application software, and the blank discs themselves. In short, the process of burning CDs is a Black Art rather than a science.
That's less true now than it was even a couple of years ago because systems are faster, CD burners are better, and buffer underrun technologies have pretty much eliminated the danger of making coasters. But it still pays to keep in mind that what counts is not just the CD burner or the blanks, but the entire system. Once you have the system working reliably, making even a minor change to one element can break it. For example, we once added an apparently innocuous Windows NT service to our main CD-R burning system. Suddenly, a system that was formerly rock-solid for burning CDs was no longer reliable. Removing the service cured the problem.
On a properly configured system, you can burn hundreds of CDs uneventfully. On a marginal system with an older CD burner, even the slightest problem or anomaly can result in a ruined CD blank, called a "coaster." Making an occasional coaster is less aggravating now that blanks cost $0.30 each instead of $20 each, but it still wastes time. If your CD writer has buffer underrun protection, you're unlikely to have problems burning CDs regardless of what else the computer happens to be doing at the moment. If your CD writer does not have buffer underrun protection, use the following guidelines to burn CDs reliably:
Regardless of the interface or operating system, take the following steps before recording a CD:
Disable power management, screen savers, schedulers, antivirus utilities, and any other software or service that may interrupt the recording process. In particular, if your PC is configured to answer phone or fax calls, disable that for the duration of the burning session.
When recording from a disk image (writing the source data to the hard drive as an intermediate step rather than doing a direct CD-to-CD copy), defragment the disk drive before starting the burn.
If your PC is on a network and is configured to share its disk or printer, disable sharing before attempting to burn a CD. If another user accesses your disk or printer while the CD is burning, the burn may fail.
In the past, conventional wisdom was that making high-quality reproductions of audio CDs required that both source drive and CD burner be SCSI. That's no longer true in that some recent ATAPI CD-ROM drives are suitable as source drives for high-quality audio duping, but the ATAPI CD-ROM drives common in most PCs of 1998 or earlier vintage are likely not suitable source drives for doing high-quality audio dupes. If your CD-ROM drive is in the latter category, you can still do high-quality audio dupes by using your CD burner as both source drive and destination drive. Doing so requires that your CD copy utility support disc-to-image copying, whereby your burner reads the source CD, writes an image of that CD to your hard drive, and then uses that image as the source.
If the data to be copied resides on a network drive, copy it to the local hard drive before attempting to burn the disc. Writing data from a network drive frequently yields a coaster, even on a 100BaseT network. Note that this caution applies only to writing CD-R discs, which is a synchronous (timing-critical) operation. We have frequently written CD-RW discs from data located on a network drive. Recording CD-RW discs in packet-writing mode is an asynchronous operation, so network delays have no effect on the integrity of the copy.
Broadly speaking, there are three ways to burn a CD-R disc, whether the source data is another CD or a random collection of files on your hard disk:
With this method, data is streamed from the source CD or hard drive, formatting and error-correction data is added in real time, and the resulting data stream is burned to the CD. The advantages of on-the-fly burning are that it is faster than other methods and it requires no extra disk space. The drawback is that on-the-fly burning is the method most likely to create coasters. Most recent systems are fast enough to dupe audio or data CDs on-the-fly successfully, but you may have problems if you attempt to write hundreds or thousands of relatively small files to a CD, as, for example, if you use your CD writer to back up your hard disk.
This method uses a two-step process. Data to be written to the CD is first read and processed to add formatting and error-correction data. That formatted data is then written out to the hard disk as an ISO image file, which is an exact binary representation of the data as it will be written to the CD. The drawbacks to using true image files are that it takes longer and you must have enough free disk space to accommodate the image file, which can be 1 GB or more when you are copying audio data to an 80-minute blank. Against these disadvantages, burning a true image file is by far the most reliable method, particularly on older, slower systems, and those that use an older model CD writer.
This method is similar to using true image files, with the exception that an actual image file is not written to the hard disk. Instead, a virtual image file is created, which contains pointers to the locations of the files to be written to the CD. Because formatting, adding error correction, and all other pre-processing is done before the actual burn starts, using a virtual image file is more reliable than burning on-the-fly. Conversely, because the files to be written must be retrieved from random locations on the hard disk during the burn, using a virtual image file is less reliable than using a true image file. Using virtual image files is slower than burning on-the-fly but faster than using true image files.
If your CD writer has buffer underrun protection, you can use any of these methods successfully. On-the-fly burning is the fastest, so there's normally no reason to use anything else. If your CD writer does not have buffer underrun protection, the best method depends on the capabilities of your system, your CD writer, and your software, as well as the type of data you want to burn to CD. On-the-fly burns usually work well for duping audio or data CDs, and (assuming that you have enough free disk space) using a true image file is best for doing backups and similar operations that require writing many small files to disc. As always, the best way to judge is to try each method and use the fastest one that works reliably for you.
|
A recent CD burner generally works well at its maximum rated speed, at least if you use high-quality blank discs. If you have an older CD burner, don't assume that you can use its fastest speed, even if your burning software tests a disc and claims that it is writable at the highest speed. With older CD burners, burning at higher speeds is generally less reliable than burning at lower speeds, both because faster burning is more likely to generate errors while writing, particularly with marginal discs, and because the CD writer's buffer, whatever its size, empties faster at higher burning speeds. For example, when writing at 12X (1800 KB/s), a 512 KB buffer stores only about one-quarter of a second's worth of data. Any interruption in the data stream longer than that generates a coaster (unless the drive has BURN-Proof or a similar technology). Larger buffers and lower write speeds minimize the chance of buffer underruns and ruined discs.
But slow equals reliable is by no means a universal truth. Burning at a slower speed is sometimes less reliable. For example, we used one no-name 32X CD writer that wrote most discs reliably at 32X or 24X, some discs reliably at 16X, and very few discs reliably at slower than 16X. The optimal burning speed depends on numerous factors, particularly the combination of drive, firmware revision, and disc.
|
In general, when we start with a new batch of media on a given CD writer, we first attempt burns at the highest speed the drive supports, regardless of the speed for which the disc is certified. For example, we had a spindle of Taiyo Yuden 24X certified blanks that burned without errors at 32X and 40X in several burners, although other burners generated errors at anything faster than 24X. In our experience, burning discs faster than their rated speed either works or it doesn't, depending on the particular CD writer and type of disc you're using. That is, if you try it and it works for one disc, it'll probably work for the rest of the spindle as well. If it's not going to work, you'll probably find out when you attempt to burn the first disc. As always, the best solution is to test in your own environment.
|
Overburning simply means writing more data to a CD-R blank than it is nominally designed to store, allowing you to fit more music or data on a standard CD-R disc. This is possible because most CD-R blanks contain more than the necessary number of writable sectors. For example, a 74-minute blank, which must have at least 333,000 sectors to yield 74 minutes of recording time, may actually contain 340,000 sectors, which allows it to record about 75.5 minutes. The number of "extra" sectors varies widely between different brands of CD-R blanks. Some contain only a few extra sectors, while others contain enough extra sectors to allow recording up to 76, 77, or even 78 minutes on a nominal 74-minute blank.
|
In the days before 80-minute blanks became widely available, overburning was a popular way to defeat the ad hoc copy protection used by some game CD makers, who simply pressed CDs that contained more sectors than would fit on a standard 74-minute CD. The widespread availability of overburning-capable software and then 80-minute blanks has almost eliminated the use of this means of copy protection.
|
If for some reason you need to burn CDs larger than 650 MB/74 minutes, keep the following issues in mind:
If your CD writer and/or CD mastering/duplication program does not support overburning 74-minute discs, you may be able to use 80-minute discs instead. Although 80-minute discs are marginally less reliable than 74-minute discs, they are more reliable than overburned 74-minute discs.
|
Some CD writers and software support overburning 74-minute discs but do not support 80-minute discs, some support 80-minute discs but not overburning, some support both, and some support neither. If software is the limiting factor, check the maker's web site. The current versions of most CD-R software support 80-minute discs.
Some CD writers can be upgraded to support 80-minute media by installing a firmware update. Others are physically incapable of writing more than 74 minutes or slightly more.
The media most suitable for overburning, which is to say those with the greatest number of extra sectors, are often otherwise undesirable. If you buy some of these oversized discs for overburning, use them only when you need to overburn something.
Most CD writers that do support overburning do so only in Disc-at-Once mode, which limits you to duplicating an audio or data CD (as opposed to premastering the data, as, for example, when you select a group of files and folders to copy). Some CD mastering software overcomes this problem by allowing you to create an ISO image of the data on your hard disk as a preliminary step, and then burning that image to the CD.
Although it may seem possible to determine the maximum length of an overburn exactly, that is not the case. For example, a CD-R disc utility may report that a blank contains 351,000 sectors, which can be converted mathematically to a burn time of 78:00:00. In reality, though, limitations in your CD writer hardware or firmware will likely place a shorter absolute limit on the actual burn.
Even if your CD burner and software support overburning, don't be surprised to see some pretty horrifying error messages during an overburn, such as Fatal write error, Track following error, or Write emergency. In fact, it's pretty common while doing a long overburn to have the software lock up at or just before the Writing Table of Contents phase. It may appear that you've made a coaster, but it's worth checking to see if the disc is readable. It often is, although by all rights it seems that it shouldn't be.
Even if your CD burner and software support overburning and the process appears to complete normally, you may find that the material past the standard 74-minute length is degraded. Audio tracks may have various artifacts, including hisses, pops, and drop-outs. Datafiles may be corrupted. The more extensive the overburn, the more likely such problems are to occur.
Overburning is a (rather dubious) art rather than a science. Actually, the same can be said in general for burning CDs, but this is particularly true when overburning. Just because you succeed once in overburning a disc doesn't mean that you'll succeed the next time, even with an identical disc and the same data.
Some CD-ROM drives and CD players, particularly older models, cannot handle overburned and/or 80-minute discs. The usual symptom is that the drive or player refuses to accept the CD, simply ejecting it as soon as you insert it. Sometimes, a drive or player reads the first 650 MB/74 minutes and then simply stops reading in the midst of an audio track or file. In general, anytime you burn a CD larger than 650 MB/74 minutes by whatever method, be aware that read problems may result.
All of that said, our general advice is as follows:
Stick to standard 74-minute CDs if at all possible, and don't try to record more than they are designed to hold. Otherwise, expect problems.
If you absolutely, positively need to record more than 74 minutes on a CD, use an 80-minute blank in a CD writer designed to support it.
If for some reason you must overburn a 74-minute blank, first make sure your CD burner supports overburning. Keep the overburn as short as possible, and test the resulting disc in the actual drive that will be used to read it before you assume that the disc will be readable.