From: Sebastian <sebastian_ml@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Digital Audio Extraction with ATAPI drives far from perfect
Date: Sat, 7 Jan 2006 11:39:01 +0100 [thread overview]
Message-ID: <20060107103901.GA17833@section_eight.mops.rwth-aachen.de> (raw)
In-Reply-To: <5bdc1c8b0601061530l3a8f4378o3b9cb96c187a6049@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Hi everybody,
On Fr, Jan 06, 2006 at 03:30:47 -0800, Mark Knecht wrote:
> On 1/6/06, Sebastian <sebastian_ml@gmx.net> wrote:
> > Hi all!
> > On Fri, Jan 06, 2006 at 12:06:15AM -0800, Joshua Kwan wrote:
> > > Hi Sebastian,
> > >
> > > On 01/03/2006 02:20 PM, Sebastian wrote:
> > > > The second series was ripped with deprecated ide-scsi emulation and yielded the
> > > > same results as EAC.
> > >
> > > What were you using? cdparanoia? cdda2wav? (Are there actually that many
> > > other options on Linux?)
> > I use cdparanoia.
>
> Try cdparanoia -Bvz
>
> This will cause the rip to be extremely careful and make sure
> everything is exactly right. It works well for me and was recommended
> by someone I trust. I hop it works for you..
>
> Cheers,
> Mark
>
I used cdparanoia -BzX -O48 for every rip.
Just to be clear, I'm not writing to this list because I have problems
with an application. :) Rather I like to know where to fix this problem, in
kernelland or userspace, like, should I start getting into cdparanoia or
reading the o'Reilly book about kernel drivers?
Thanks
Sebastian
--
"When the going gets weird, the weird turn pro." (HST)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-07 10:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 22:20 Sebastian
2006-01-04 9:20 ` Jens Axboe
2006-01-04 9:24 ` Jens Axboe
2006-01-04 15:08 ` Mark Lord
2006-01-04 15:13 ` Jens Axboe
2006-01-04 15:50 ` Sebastian
2006-01-04 19:36 ` Alistair John Strachan
2006-01-04 21:54 ` Sebastian
2006-01-06 13:39 ` jerome lacoste
2006-01-05 6:43 ` Sebastian
2006-01-06 8:06 ` Joshua Kwan
2006-01-06 23:25 ` Sebastian
2006-01-06 23:30 ` Mark Knecht
2006-01-07 10:39 ` Sebastian [this message]
2006-01-07 10:56 ` Jens Axboe
2006-01-07 11:00 ` Jens Axboe
2006-01-07 11:53 ` Sebastian
2006-01-07 11:57 ` Jens Axboe
[not found] ` <20060107112443.GA18749@section_eight.mops.rwth-aachen.de>
[not found] ` <20060107115340.GW3389@suse.de>
[not found] ` <20060107115449.GB20748@section_eight.mops.rwth-aachen.de>
[not found] ` <20060107115947.GY3389@suse.de>
2006-01-07 14:08 ` Sebastian
2006-01-07 14:22 ` Jens Axboe
2006-01-07 16:06 ` Sebastian
2006-01-07 17:44 ` Brad Campbell
2006-01-07 18:02 ` Sebastian
2006-01-07 18:39 ` Lee Revell
2006-01-07 18:45 ` Brad Campbell
2006-01-09 9:30 ` Jens Axboe
2006-01-09 9:49 ` Sebastian
2006-01-09 10:03 ` Jens Axboe
2006-01-10 22:43 ` Rene Herman
2006-01-10 22:52 ` Lee Revell
2006-01-10 23:05 ` Rene Herman
2006-01-07 17:24 ` Sebastian
2006-01-07 19:18 ` Alan Cox
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=20060107103901.GA17833@section_eight.mops.rwth-aachen.de \
--to=sebastian_ml@gmx.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®