cdrtools
cdrtools (formerly cdrecord) creates home-burned CDs/DVDs with a CDR/CDRW/DVD/BluRay recorder. It works as a burn engine for several applications. It supports CD/DVD/BD recorders from many different vendors; all SCSI-3/mmc- and ATAPI/mmc-compliant drives should also work. Supported features include IDE/ATAPI, parallel port, and SCSI drives; audio CDs, data CDs, and mixed CDs; full multi-session support; CD-RWs, DVD-R/-RW, DVD+R/+RW, BD-R/BD-RE; and TAO, DAO, RAW, and human-readable error messages. cdrtools includes remote SCSI support and can access local or remote CD/DVD/BD writers.
| Tags | Software Distribution Archiving multimedia Sound/Audio CD Audio CD Writing CD Ripping Boot |
|---|---|
| Licenses | CDDL |
| Operating Systems | Windows Windows OS/2 POSIX Mac OS X |
Recent releases
- 02 Jun 2010 11:00
Changes: More than half of the current code is new compared to the last stable 2.01 version. BluRay support was added. The DVD code has been OSS since May 2006. DVD Double Layer support was added. DVD-multi-border support was added. Support for reading and writing hidden audio tracks was added. Cdrecord supports non-standard CUE Files from ExactAudioCopy. SCSI auto-target mode allows operation without dev=. Mkisofs now supports find(1)-like command lines, includes better UDF support, and allows for files up to 8 TB. Readcd allows enhanced CD/DVD quality checks. Support for several new operating systems was added.
- 17 May 2010 23:02
Changes: Maiden BD-RE media is now autoformatted before it is written to. With DVD+RW formatting and cdrecord -v, progress information is printed. Many small improvements have been made to the makefile system. This release will become cdrtools-3.0-final if no bugs are found.
- 27 Apr 2010 21:46
Changes: Many new features have been added to libfind. Mkisofs now gives several better hints on which options to use in order to avoid program aborts that are caused by specifics of the archived data. Mkisofs now implements -data-change-warn in order not to abort when files change their size during archival.
- 01 Mar 2010 16:50
Changes: Small bugs were fixed. cdrecord no longer tries to close a session with BD-RE (BluRay). cdrecord now correctly computes pregap sizes with Exact Audio Copy enhanced CUE sheets.
- 17 Feb 2010 23:33
Changes: This release adds a workaround for a firmware bug in the drive: 'HL-DT-ST' 'BD-RE BH10LS30 ' '1.00' that causes the drive to return zero media size for BluRay media. There are many CUE parser enhancements (e.g. support for Exact Audio Copy variants). Enhanced cdda2ogg and cdda2mp3.
schily
13 Mar 1998 10:32
Heartbeat
- Popularity Score
- 11,187.40
- Vitality Score
- 105.55
- Subscriptions
- 675
- All comments
Recent commentsNot really written for Linux, but tries to force the Solaris way on everybody. Tries to see everything as a SCSI device, which is not particularly user friendly, given that 99% of CD writers nowadays are not SCSI.
With current version of the kernel 2.6.32+ this package will no longer compile cleanly. I am using a current version of LFS and there are numerous errors about headers being incorrect. I am not sure if this is a problem with the program or with its "strange" make system that I have not seen on other projects. I do not have kernel headers in /usr/src/kernel as this is a bad practice. I hate to find an alternative but if this will not compile I have no choice.
Well, jones501 is all wrong.
- cdrtools runs perfectly on linux (better than cdrkit)
- cdrtools supports /dev-devices, it's just a bad idea to use them, better use the scsi-id discovered with ./cdrecord --scanbus (if you have only one burning capable device, you do not even need to tell cdrecord a device, it chooses by itself)
- stuck in 1997? you mean, it still supports OSs which are this old? Why would this be a negative fact?
- if you get a lot of coasters, maybe try another burner or blanks from another vendor ... AND, cdrkit does no better, in contrary it still has lots of bugs which are not present in cdrtools anymore
- UTF-8 problems? Are you sure you used a recent version (like less than 3 years old)
- well, if you have problems with the license (which is your right of course), you can use an old version of cdrecord as well, cdrkit does no better. All they fixed are some typos in the man pages
still crap on linux
still doesn't support real addressing schemes
still stuck in 1997
still burns coasters half the time in TAO
still can't handle utf-8 correctly
and now it's a licensing nightmare, since jorg changed the license on half the code and left it gpl on the other half.
save yourself a lot of trouble and use cdrkit, which works reliably, works right on linux, has a sane license, and isn't managed by a megalomaniac who can't handle criticism and won't accept patches
I cannot change anything on the problems that are all
caused by the hostility of the person who started "cdrkit"
and the original project is just a victim of a hostile
downstream. Many people have been fooled by this
person but more and more people realize that "cdrkit"
is full of bugs that are not fixed since years, so the needs
of the users of "cdrkit" are just ignored by the people behind it.
Fortunately, the original cdrtools project exists and is actively
maintained. The original project has no known problems. This is
because problems reported to the original project are not
ignored but dealt with care in a polite way and fixes are made
available quickly, so nobody is forced to live with the problems
in "cdrkit". All known problems caused by "cdrkit" just go away
if you upgrade to a recent original cdrtools version.
The fact that the original project cdrtools was attacked by a hostile
downstream did not change anything in cdrtools. Everything is done
to the benefit of the users in order to defend the original software
against attacks and to make sure that the original project will stay
freely available under a free, permissive license that is compatible
with the OpenSource definition from the OpenSource initiative.
Since "cdrkit" was given up by it's initiator on May 6th 2007, the original
cdrtools did have 3800 file edits in 1500 putback groups, this is a
sustained average putback rate of 4 file changes per day. Since "cdrtkit"
was started, it did not introduce any new feature but the original software
added many new features in the same time. Users can decide whether
they prefer the unmaintained "cdrkit" that was created from an extremely
outdated cdrtools version by a hostile downstream or whether they prefer
actively maintained original cdrtools software from a cooperative author.
I hope this helps people who hesitate about the state of the original
software.