public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Sebastian <sebastian_ml@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Digital Audio Extraction with ATAPI drives far from perfect
Date: Wed, 4 Jan 2006 10:24:44 +0100	[thread overview]
Message-ID: <20060104092443.GO3472@suse.de> (raw)
In-Reply-To: <20060104092058.GN3472@suse.de>

On Wed, Jan 04 2006, Jens Axboe wrote:
> On Tue, Jan 03 2006, Sebastian wrote:
> > Hello all!
> > 
> > I'd be kind if you would cc me in case you reply as I'm not (yet)
> > subscribed to this list.
> > 
> > I'm a music buff :) Well, I guess most people are in one way or the
> > other. But in addition to that I like bitperfect ripping very much.
> > Since some time this doesn't work well with linux anymore.
> > 
> > I'd like to know if there's something in the making already or what
> > could be done to solve this issue. A supporting layer for the ide
> > system, a new driver maybe? I think this can't be fixed in userspace,
> > right?
> > 
> > I ripped an audio disc in different ways and compared the results using
> > md5sum. As you can see the wav data is perfect when using ide-scsi
> > emulation. On the contrary, using ide lead to errors.
> > 
> > Linux version 2.6.15 (root@section_eight) (gcc-Version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8))
> > 
> > In all cases I used the same drive, a NEC ND-4550A dvd writer.
> > 
> > The first series of wav files was ripped with EAC in Windows and is
> > bitperfect:
> > 
> > 8cab5ca4820a753ebb3cb7e3c5c34e6a  01.Man In A Suitcase.wav
> > 187f90f900cffd36ce56e97a3bcf595e  02.Box Of Six.wav
> > 8cc168bb50e80a06693a01a9cd34bbdf  03.Mysterons.wav
> > e82169e5ea1b441b80db96fce12fd109  04.Justified.wav
> > 8d807b7ac19f90049aec6ff177e9b486  05.Department S.wav
> > 130306e9a564c844d5269256f38afca7  06.Area Code 51.wav
> > 96489dbfcab8f97e7e450cf8db2c8aaa  07.Has To Be.wav
> > 4597a6ed75e201916a3479f05eb86405  08.No. 5.wav
> > f978327a98fc6359be2fc25eb865211d  09.Among The Cybermen.wav
> > e316e140b4b0cd66e5822edae22dadb1  10.Unspeakable Elvis.wav
> > 3792a680b1ba729de9185043d331186f  11.Xodiak.wav
> > ba534fd8eb42dd84aa7b59ab3ae6f132  12.Northern Wisdom.wav
> > d6346ab76696dddf735a5b752aa7888b  13.Trinity Road.wav
> > 
> > The second series was ripped with deprecated ide-scsi emulation and yielded the
> > same results as EAC.
> > 
> > The third series was done with ide-cd. Erroneous data is marked
> > with a (!):
> > 
> > e8319ccc20d053557578b9ca3eb368dd  track01.cdda.wav (!)
> > cb978f86ddc18c9df1b7e91705380bc5  track02.cdda.wav (!)
> > 35f1b296d72a8708d03aeb540a3b4f30  track03.cdda.wav (!)
> > e82169e5ea1b441b80db96fce12fd109  track04.cdda.wav
> > 8d807b7ac19f90049aec6ff177e9b486  track05.cdda.wav
> > 02561939763d67aacf23157c09966a89  track06.cdda.wav (!)
> > 9724b0a3e2295084613da9df7397ae6d  track07.cdda.wav (!)
> > c2d85b3d10428aad66664d0fb3e4c71a  track08.cdda.wav (!)
> > 5116b2fae44b8b86fbf40b9bac9a8268  track09.cdda.wav (!)
> > 9e6a5ab2dab76e1677667f586895293a  track10.cdda.wav (!)
> > 3792a680b1ba729de9185043d331186f  track11.cdda.wav
> > ba534fd8eb42dd84aa7b59ab3ae6f132  track12.cdda.wav
> > d6346ab76696dddf735a5b752aa7888b  track13.cdda.wav
> 
> Can you try and see how, say, track01 differ? Is it single bytes, chunks
> of 2352 bytes, or?

Oh, and try and disable DMA on the cd driver and repeat your results
with ide-cd. It uses DMA, where ide-scsi does not. Dunno what Windows
does. It could just be a problem with your drive and DMA enabled rips.

-- 
Jens Axboe


  reply	other threads:[~2006-01-04  9:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 22:20 Digital Audio Extraction with ATAPI drives far from perfect Sebastian
2006-01-04  9:20 ` Jens Axboe
2006-01-04  9:24   ` Jens Axboe [this message]
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
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=20060104092443.GO3472@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian_ml@gmx.net \
    /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