cdrecord.man

刻录光盘的程序

CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



NNNNAAAAMMMMEEEE
     cdrecord - record audio or data Compact Discs from a master

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     ccccddddrrrreeeeccccoooorrrrdddd [ _g_e_n_e_r_a_l _o_p_t_i_o_n_s ] ddddeeeevvvv====_d_e_v_i_c_e [  _t_r_a_c_k  _o_p_t_i_o_n_s  ]
     _t_r_a_c_k_1..._t_r_a_c_k_n


DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     CCCCddddrrrreeeeccccoooorrrrdddd is used to record data or audio Compact Discs on an
     Orange Book CD-Recorder.

     The _d_e_v_i_c_e refers to _s_c_s_i_b_u_s/_t_a_r_g_e_t/_l_u_n of the  CD-Recorder.
     Communication  on _S_u_n_O_S is done with the SCSI general driver
     ssssccccgggg.... Other operating systems are using a library  simulation
     of    this    driver.     Possible    syntax    is:     ddddeeeevvvv====
     _s_c_s_i_b_u_s,_t_a_r_g_e_t,_l_u_n or ddddeeeevvvv==== _t_a_r_g_e_t,_l_u_n.  In the latter  case,
     the  CD-Recorder has to be connected to the default SCSI bus
     of  the  machine.   _S_c_s_i_b_u_s,  _t_a_r_g_e_t  and  _l_u_n  are  integer
     numbers.  Some operating systems or SCSI transport implemen-
     tations may require to specify a filename in  addition.   In
     this  case  the  corect  syntax  for  the  device  is:  ddddeeeevvvv====
     _d_e_v_i_c_e_n_a_m_e:_s_c_s_i_b_u_s,_t_a_r_g_e_t,  or  ddddeeeevvvv====  _d_e_v_i_c_e_n_a_m_e:_t_a_r_g_e_t,_l_u_n.
     If  the  name  of the device node that has been specified on
     such a system referres to exactly one SCSI device, a  short-
     hand  in the form ddddeeeevvvv==== _d_e_v_i_c_e_n_a_m_e:@ or ddddeeeevvvv==== _d_e_v_i_c_e_n_a_m_e:@,_l_u_n
     may be used instead of ddddeeeevvvv==== _d_e_v_i_c_e_n_a_m_e:_s_c_s_i_b_u_s,_t_a_r_g_e_t,


     To make ccccddddrrrreeeeccccoooorrrrdddd portable to all UNIX platforms, the  syntax
     ddddeeeevvvv====  _d_e_v_i_c_e_n_a_m_e:_s_c_s_i_b_u_s,_t_a_r_g_e_t, is preferred as is hides OS
     specific knowledge about device  names  from  the  user.   A
     specific  OS must not necessarily support a way to specify a
     real   device   file   name   nor   a   way    to    specify
     _s_c_s_i_b_u_s,_t_a_r_g_e_t,_l_u_n.


     _S_c_s_i_b_u_s 0 is the default SCSI bus on the machine. Watch  the
     boot   messages   for   more   information   or   look  into
     ////vvvvaaaarrrr////aaaaddddmmmm////mmmmeeeessssssssaaaaggggeeeessss for more information about the SCSI confi-
     guration  of  your  machine.  If you have problems to figure
     out what values for _s_c_s_i_b_u_s,_t_a_r_g_e_t,_l_u_n should be  used,  try
     the ----ssssccccaaaannnnbbbbuuuussss option of ccccddddrrrreeeeccccoooorrrrdddd described below.


     If a file /etc/default/cdrecord exists, the parameter to the
     ddddeeeevvvv==== option may also be a drive name label in said file (see
     FILES section).


     On SSSSVVVVrrrr4444 compliant systems, ccccddddrrrreeeeccccoooorrrrdddd uses the the  real  time
     class  to  get  the  highest  scheduling  priotity  that  is



Joerg Schilling     Last change: Version 1.8                    1






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     possible (higher than all  kernel  processes).   On  systems
     with  PPPPOOOOSSSSIIIIXXXX  rrrreeeeaaaallll  ttttiiiimmmmeeee  sssscccchhhheeeedddduuuulllliiiinnnngggg  cdrecord uses real time
     scheduling too, but may not be able to gain a priority  that
     is higher than all kernel processes.

     In _T_r_a_c_k _A_t _O_n_c_e mode, each _t_r_a_c_k corresponds  to  a  single
     file that contains the prepared data for that track.  If the
     argument is `----', standard input is used for that track. Only
     one track may be taken from _s_t_d_i_n.


GGGGEEEENNNNEEEERRRRAAAALLLL OOOOPPPPTTTTIIIIOOOONNNNSSSS
     General options must be before any track file name or  track
     option.

     ----vvvveeeerrrrssssiiiioooonnnn
          Print version information and exit.

     ----vvvv    Increment the level of general verbosity by one.  This
          is  used  e.g.  to  display the progress of the writing
          process.

     ----VVVV    Increment the verbose level in respect of SCSI command
          transport  by one.  This helps to debug problems during
          the writing process, that occur in the CD-Recorder.  If
          you  get incomprehensible error messages you should use
          this flag to get more detailed output.  ----VVVVVVVV  will  show
          data buffer content in addition.  Using ----VVVV or ----VVVVVVVV slows
          down the process and may be the  reason  for  a  buffer
          underrun.  Using

     ----ddddeeeebbbbuuuugggg
          Print additional debug messages. This may help to  find
          out problems with sector sizes and sector types.  Using
          ----ddddeeeebbbbuuuugggg slows down the process and may be the reason for
          a buffer underrun.

     ----ffffoooorrrrcccceeee
          Force  to  continue  on  some  errors.    This   option
          currently implements some tricks that will allow you to
          blank bad CD-RW disks.

     ----dddduuuummmmmmmmyyyy
          The CD-Recorder  will  go  through  all  steps  of  the
          recording  process,  but the laser is turned off during
          this procedure.  It is recommended to run several tests
          before  actually writing to a Compact Disk, if the tim-
          ing and load response of the system is not known.

     ----ddddaaaaoooo  Set DDDDiiiisssskkkk AAAAtttt OOOOnnnncccceeee mmmmooooddddeeee.... This currently only works  with
          MMC drives that support non raw SSSSeeeessssssssiiiioooonnnn AAAAtttt OOOOnnnncccceeee mode.




Joerg Schilling     Last change: Version 1.8                    2






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     ----mmmmuuuullllttttiiii
          Allow multi session CD's to be made. This flag needs to
          be  present  on  all  sessions of a multi session disk,
          except you want to create a session that  will  be  the
          last  session  on the media.  The fixation will be done
          in a way that allows the CD-Recorder  to  append  addi-
          tional sessions later. This is done by generation a TOC
          with a link to the next program area. The so  generated
          media  is  not  100%  compatible  to  manufactured CD's
          (except for CDplus). Use only for  recording  of  multi
          session  CD's.   If this option is present, the default
          track type is CCCCDDDD----RRRROOOOMMMM XXXXAAAA mmmmooooddddeeee 2222.  The _S_o_n_y  drives  have
          no  hardware support for CCCCDDDD----RRRROOOOMMMM XXXXAAAA mmmmooooddddeeee 2222.  You have to
          specify the ----ddddaaaattttaaaa option in order to create multi  ses-
          sion  disks  on these drives.  As long as cdrecord does
          not have a coder for converting data sectors  to  audio
          sectors,  you need to force CCCCDDDD----RRRROOOOMMMM sectors by including
          the ----ddddaaaattttaaaa option if you like to record  a  multisession
          disk  in  DAO/SAO mode.  Not all drives allow multises-
          sion CD's in DAO/SAO mode.

     ----mmmmssssiiiinnnnffffoooo
          Retrieve multi session info  in  a  form  suitable  for
          mmmmkkkkiiiissssooooffffssss----1111....11110000 or later.

          This option makes only sense with a CD that contains at
          least one closed session and is appendable (not finally
          closed yet). Some drives create error messages  if  you
          try  to  get  the multi session info for a disk that is
          not suitable for this operation.

     ----ttttoooocccc  Retrieve and print out the table of content or PMA  of
          a  CD.   With this option, ccccddddrrrreeeeccccoooorrrrdddd will work with CD-R
          drives and with CD-ROM drives.

     ----aaaattttiiiipppp
          Retrieve and print out the ATIP (absolute Time in  Pre-
          groove) info of a CD recordable or CD rewritable media.
          With this option, ccccddddrrrreeeeccccoooorrrrdddd will  try  to  retrieve  the
          ATIP info. If the actual drive does not support to read
          the ATIP info, it may be that only  a  reduced  set  of
          information  records or even nothing is displayed. Only
          a limited number of MMC  compliant  drives  support  to
          read the ATIP info.

          If ccccddddrrrreeeeccccoooorrrrdddd is able to retrieve the lead-in start  time
          for  the first session, it will try to decode and print
          the manufacturer info from the media.

     ----ffffiiiixxxx  The disk will only be fixated (i.e. a TOC  for  a  CD-
          Reader  will be written). This may be used, if for some
          reason the disk has been written but not fixated.  This



Joerg Schilling     Last change: Version 1.8                    3






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



          option currently does not work with TEAC drives.

     ----nnnnooooffffiiiixxxx
          Do not fixate the disk after writing the  tracks.  This
          may  be  used  to create an audio disk in steps. An un-
          fixated disk can usually not be used on a non CD-writer
          type  drive but there are audio CD players that will be
          able to play such a disk.

     ----llllooooaaaadddd
          Load the media and exit. This only works  with  a  tray
          loading mechanism but seems to be useful when using the
          Kodak disk transporter.

     ----eeeejjjjeeeecccctttt
          Eject disk after doing the work.   Some  Devices  (e.g.
          Philips) need to eject the medium before creating a new
          disk. Doing a -dummy test and  immediately  creating  a
          real disk would not work on these devices.

     ssssppppeeeeeeeedddd====####
          Set the speed factor of the writing process to #.  # is
          an integer, representing a multiple of the audio speed.
          This is about 150 KB/s for CD-ROM and  about  172  KB/s
          for  CD-Audio.  If no _s_p_e_e_d option is present, ccccddddrrrreeeeccccoooorrrrdddd
          will try to get the  speed  value  from  the  CCCCDDDDRRRR____SSSSPPPPEEEEEEEEDDDD
          environment.   If  your drive has problems with _s_p_e_e_d=_2
          or _s_p_e_e_d=_4, you should try _s_p_e_e_d=_0.

     bbbbllllaaaannnnkkkk====_t_y_p_e
          Blank a CD-RW and exit or blank a CD-RW before writing.
          The blanking type may be one of:

          help        Display a list of possible blanking types.

          all         Blank the entire disk. This may take a long
                      time.

          fast        Minimally blank the disk. This  results  in
                      erasing the PMA, the TOC and the pregap.

          track       Blank a track.

          unreserve   Unreserve a reserved track.

          trtail      Blank the tail of a track.

          unclose     Unclose last session.

          session     Blank the last session.
     If used together with the ----ffffoooorrrrcccceeee flag, this  option  may  be
     used  to blank CD-RW disks that otherwise cannot be blanked.



Joerg Schilling     Last change: Version 1.8                    4






CDRECORD(1)          Schily's USER COMMANDS           CDRECORD(1)



     Note that you may need to  specify  bbbbllllaaaannnnkkkk====_a_l_l  because  some
     drives  will  not  continue  with certain types of bad CD-RW
     disks. Note also that ccccddddeeeeccccoooorrrrdddd does it's best if the  ---- ffffoooorrrrcccceeee
     flag  is used but it finally depends on the drive's firmware
     whether the blanking operation will succeed or not.

     ffffssss====# Set the fifo (ring buffer) size to #.  You may use  the
          same method as in dddddddd(1), ssssdddddddd(1) or ssssttttaaaarrrr(1).  The number
          representing the size is taken in bytes  unless  other-
          wise  specified.   If  a number is followed directly by
          the letter `b', `k', `m', `s' of `f', the size is  mul-
          tiplied  by 512, 1024, 1024*1024, 2048 or 2352.  If the
          size consists of numbers separated by `x' or `*',  mul-
          tiplication  of  the  two  numbers  is performed.  Thus
          _f_s=_1_0_x_6_3_k will specify a fifo size of 630 kBytes.

          The size specified by the  _f_s=  argument  includes  the
          shared  memory  that is needed for administration. This
          is at least one page of memory.  If no  _f_s=  option  is
          present,  ccccddddrrrreeeeccccoooorrrrdddd  will try to get the fifo size value
          from the CCCCDDDDRRRR____FFFFIIIIFFFFOOOOSSSSIIIIZZZZEEEE environment.   The  default  fifo
          size is currently 4 MB.

          The fifo is used to increase  buffering  for  the  real
          time  writing  process.   It  allows to run a pipe from
          mmmmkkkkiiiissssooooffffssss directly into ccccddddrrrreeeeccccoooorrrrdddd.  If the fifo is  active
          and a pipe from mmmmkkkkiiiissssooooffffssss into ccccddddrrrreeeeccccoooorrrrdddd is used to create
          a CD, ccccddddrrrreeeeccccoooorrrrdddd will abort prior to do any modifications
          on  the  disk if mmmmkkkkiiiissssooooffffssss dies before it starts writing.
          The recommended fifo size is between 4 and  32  MBytes.
          As  a  rule  of thumb, the fifo size should be at least
          equal to the size of the internal  buffer  of  the  CD-
          Recorder  and  no more than half of the physical amount
          of RAM available in the machine.  If the fifo  size  is
          big enough, the fifo statistics will print a fifo empty
          count of zero and the fifo min fill is not  below  20%.
          It  is  not wise to use too much space for the fifo. If
          you need more than 8 MB  to  write  a  CD  on  an  idle
          machine,  your  machine  is  either  underpowered,  has
          hardware problems  or  is  mis-configured.   The  sun4c
          architecture  (e.g. a Sparcstation-2) has only MMU page
          table entries for 16 MBytes  per  process.  Using  more
          than  14  MBytes  for  the fifo may cause the operating
          system in this case to spend much  time  to  constantly
          reload  the  MMU tables. Newer machines from Sun do not
          have this MMU hardware problem. I have  no  information
          on PC-hardware reflecting this problem.

          If you have buffer underruns or  similar  problems  and
          observe  a  zero  _f_i_f_o  _e_m_p_t_y  _c_o_u_n_t, you have hardware
          problems. The fifo size in this case is sufficient.




Joerg Schilling     Last change: Version 1.8                    5