From: "Jacob Schmude" <jschmude@adelphia.net>
To: "speakup@braille.uwo.ca" <speakup@braille.uwo.ca>
Subject: Re: Burning read writables
Date: Mon, 18 Aug 2003 19:49:13 -0400 [thread overview]
Message-ID: <20030818234902.UXOM1347.mta3.adelphia.net@beavis> (raw)
In-Reply-To: <Pine.LNX.4.44.0308181709490.11091-100000@omnibase.migliorelli.org>
Hi
Actually, this is writer-specific. Many writers can't burn cdrw as fast as cdr disks. I think, but am not positive, that this has something to do with the way in which
the disks are made. The method for writing to an RW is different than the one used to write to a regular recordable. I've got a 52x writer here, but it can only
burn an RW at 24x. There's nothing you can do about this, it's just the way cd burners work.
HTH
On Mon, 18 Aug 2003 17:11:55 -0600 (MDT), Paul Migliorelli (+1 3 0 3 5 4 3 2 3 1 1) wrote:
>Hi all. For the first time I'm using read writables to burn some audio.
>I specify the dash speed equals 12 in cdrecord, but it seems to always
>default to a speed of 4. Is this normal for read writables? Is there a
>way to make it go to 12 like with regular cds?
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Paul Migliorelli (+1 3 0 3 5 4 3 2 3 1 1)
` Jacob Schmude [this message]
` Lorenzo Prince
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=20030818234902.UXOM1347.mta3.adelphia.net@beavis \
--to=jschmude@adelphia.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).