public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva•net>
To: Henry Worth <haworth@ncal•verio.com>, <linuxppc-dev@lists•linuxppc.org>
Subject: Re: CDDA playback on Pismo (and other newer models)
Date: Fri, 4 Aug 2000 14:57:50 +0200	[thread overview]
Message-ID: <20000804125750.16864@mailhost.mipsys.com> (raw)


>
>Using the ATAPI CD drivers there are underruns with significant
>dropouts every couple of seconds. Various hdparms and cdparanoia
>parms were tried with no significant change. These include various
>transfers modes and cdparanoia's buffer (-n) and speed (-S)
>parms and various data formats. Piping cdparanoia out to /dev/null
>showed data rates of 46 sectors/sec at -S1, 65sps at -S8, and
>133sps at -S12 and above (also the default and no significant
>changes with different transfer modes and -n values). At the higher
>speeds (>-S11) there is a high-level of continuous head-seek noise,
>suggesting a lot of overruns and reseeks on the CD i/f side.
>
>Rebuilding the kernel to use SCSI generic devices with IDE SCSI
>emulation produced much better, even usable, results. At startup
>there are still a couple of dropouts in the first few seconds,
>but after that the playback is clean across multiple tracks (even
>with a concurrent kernel compile). Piping cdparanoia to /dev/null
>shows data rates of 187sectors/sec at all -S settings (and default).
>From the the drive's spin-up sounds it seems to always be in
>high-speed mode, but unlike the ATAPI driver, there is little
>head movement noise.

I think the problem is more with cdparanoia. I think it's more or less
synchronous, it doesn't have a thread that collects datas while another
outputs sounds. I've looked at cdparanoia sources some time ago, and I
think and intermediate step of buffering is necessary.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-08-04 12:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-04 12:57 Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-08 22:19 CDDA playback on Pismo (and other newer models) Henry Worth
2000-08-07 19:35 Iain Sandoe
2000-08-07 21:49 ` Henry Worth
2000-08-07  9:03 Iain Sandoe
2000-08-07 19:18 ` Henry Worth
2000-08-08  5:02   ` Takashi Oe
2000-08-08  7:01     ` Henry Worth
2000-08-06 21:07 Henry Worth
2000-08-06  9:38 Iain Sandoe
2000-08-06 13:26 ` Takashi Oe
2000-08-06 18:36 ` Henry Worth
2000-08-07  1:25   ` Takashi Oe
2000-08-07  5:02     ` Henry Worth
2000-08-04 13:05 Iain Sandoe
2000-08-04  9:16 Iain Sandoe
2000-08-04 20:40 ` Henry Worth
2000-08-04 21:03   ` Benjamin Herrenschmidt
2000-08-06  8:09 ` Henry Worth
2000-08-04  5:18 Henry Worth
2000-08-04  9:50 ` Michel Dänzer
2000-08-04 15:56 ` Nelson Abramson
2000-08-04 19:45   ` Henry Worth

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=20000804125750.16864@mailhost.mipsys.com \
    --to=bh40@calva$(echo .)net \
    --cc=haworth@ncal$(echo .)verio.com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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