From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: DVD-cd usage
Date: Fri, 22 Jul 2005 18:13:46 +0000 (UTC) [thread overview]
Message-ID: <loom.20050722T200433-239@post.gmane.org> (raw)
In-Reply-To: 42DFE231.8010401@planet.nl
Holly Bostick <motub <at> planet.nl> writes:
> > cdrecord -dao dev=ATAPI:0,0,0 -eject speed=2 -pad -data -v README
> > TOC Type: 1 = CD-ROM
> > scsidev: 'ATAPI:0,0,0'
> > devname: 'ATAPI'
> > scsibus: 0 target: 0 lun: 0
> > Warning: Using ATA Packet interface.
> > Warning: The related Linux kernel interface code seems to be unmaintained.
> > Warning: There is absolutely NO DMA, operations thus are slow.
> > Using libscg version 'schily-0.8'.
> > SCSI buffer size: 64512
> > atapi: 1
> > Device type : Removable CD-ROM
> > Version : 0
> > Response Format: 2
> > Capabilities :
> > Vendor_info : 'TOSHIBA '
> > Identifikation : 'DVD-ROM SD-R2412'
> > Revision : '1015'
> > Device seems to be: Generic mmc2 DVD-ROM.
> > Current: 0x0009
> > Profile: 0x0010
> > Profile: 0x0008
> > Profile: 0x0009 (current)
> > Profile: 0x000A
> > Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
> > Driver flags : MMC-3 SWABAUDIO BURNFREE
> > Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
> > Drive buf size : 1791936 = 1749 KB
> > FIFO size : 4194304 = 4096 KB
> > Track 01: data 0 MB padsize: 596 KB
> > Total size: 0 MB (00:04.00) = 300 sectors
> > Lout start: 1 MB (00:06/00) = 300 sectors
> > Current Secsize: 2048
> > ATIP info from disk:
> > Indicated writing power: 4
> > Is not unrestricted
> > Is not erasable
> > Disk sub type: Medium Type A, low Beta category (A-) (2)
> > ATIP start of lead in: -12508 (97:15/17)
> > ATIP start of lead out: 359845 (79:59/70)
> > Disk type: Short strategy type (Phthalocyanine or similar)
> > Manuf. index: 22
> > Manufacturer: Ritek Co.
> > Blocks total: 359845 Blocks current: 359845 Blocks remaining: 359545
> > Starting to write CD/DVD at speed 4 in real SAO mode for single session.
> > Last chance to quit, starting real write 2 seconds.
> > cdrecord: fifo had 1 puts and 0 gets.
> > cdrecord: fifo was 0 times empty and 0 times full, min fill was 0%.
> Which seems to bring us back to where I at least was a bit ago---
> 1. There's nothing wrong with the device *per se*, or with cdrecord,
> having now proved that it is capable of burning a file to CD (I assume
> the file was correctly burned, but with a file as small as a README,
> you're not going to get any noticeable buffer use)
> 2. The error that cdrecord was previously giving is to greater or lesser
> degree accurate--
> *there's something wonky about the files you're trying to burn*
> I don't know what that might be, but it seems to me that one possible
> chain of logic is:
> a) no matter whether you use --audio or --data (or rename the file with
> a new extension), cdrecord detects the file as audio and automatically
> uses the --audio switch;
> b) cdrecord has requirements for the encoding of a file using --audio
> (as specified in man cdrecord, earlier quoted)
> c) your file, which must be burned with the --audio switch, does not
> meet the specifications that the --audio switch requires (as shown when
> you posted the file specs gleaned from mPlayer).
> The problem might be something else entirely, of course; this is just a
> theory. But since we don't know what the problem actually is (and I
> don't so much have the time atm to specify how to make sure all the
> components from the kernel to cdrecord to your file are all in proper
> working order), it's worth further investigation.
> On that note, three questions:
> 1) the USE flags for cdrtools are:
>
> on-the-fly-crypt -
> unicode - Adds support for Unicode
> crypt - Add support for encryption -- using mcrypt or gpg where
> applicable
> dvdr - Adds support for DVD writer hardware (e.g. in xcdroast)
Dunno. I just discovered that there is a cdrecord man page (see last
response to Dave). I need to read up on cdrecord and learn the basics
of using a/the cdwrite features...
> Which ones did you use? Maybe you have a functionality needed that you
> don't have enabled?
Where are these flags set?
/etc/make.conf has these USE flags:
"-gtk -gnome java qt kde dvd cdr sse mmx 3dnow alsa
apache2 calendar cups divx4linux encode ethereal acc
jack perl php postgres spell ssl tiff xv java ffmpeg
mplayer v4l dvdr jpeg lm_sensors quicktime xmms xvid
mozilla mpeg scanner doc xine theora"
> 2) Have you tried re-encoding the audio file to the cdrecord
> specifications, and *then* burning it?
I need to learn how to use any simple cdrecording commands
(syntax challeged user here) first. Then I can worry about
all sorts of fancy file types/formats. I'd be better off
downloading a know file to write to the device (ascii text?)
or something on the gentoo system, just to build a little
confidence. I need a newbie 'how to cd burn' before I worry
about the intricacies of audio recording files on CDs.
> 3) (Thanks for the idea, Dave Nebinger) Have you tried making an ISO of
> all the audio files (unaltered) that you want to burn to CD, using
> mkisofs, and then burning the ISO instead of the files?
I'm going to read the cdrecord man pages. simple syntax examples
or a link to a document to any cd burning software is what
I need.
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-22 18:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 17:11 [gentoo-user] DVD-cd usage James
2005-07-18 17:25 ` Daniel da Veiga
2005-07-18 18:57 ` [gentoo-user] " James
2005-07-18 19:37 ` Daniel da Veiga
2005-07-18 20:36 ` James
2005-07-18 21:09 ` Daniel da Veiga
2005-07-18 21:22 ` James
2005-07-18 21:22 ` Nick Rout
2005-07-18 22:01 ` James
2005-07-18 22:28 ` Nick Rout
2005-07-18 23:03 ` James
2005-07-18 23:32 ` Nick Rout
2005-07-18 23:54 ` James
2005-07-19 0:02 ` Nick Rout
2005-07-19 0:47 ` James
2005-07-19 1:25 ` Holly Bostick
2005-07-19 19:51 ` James
2005-07-19 20:44 ` Holly Bostick
2005-07-20 5:38 ` Rumen Yotov
2005-07-20 18:40 ` James
2005-07-21 4:25 ` Zac Medico
2005-07-21 16:38 ` James
2005-07-21 12:26 ` James Hiscock
2005-07-21 16:42 ` James
2005-07-21 17:40 ` Rumen Yotov
2005-07-19 0:07 ` James
2005-07-21 17:23 ` James
2005-07-21 17:38 ` Dave Nebinger
2005-07-22 17:50 ` James
2005-07-22 18:20 ` Dave Nebinger
2005-07-23 0:32 ` Bob Sanders
2005-07-21 17:58 ` Holly Bostick
2005-07-22 18:13 ` James [this message]
2005-07-23 6:13 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20050722T200433-239@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox