Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Dominik Stadler <Dominik.Stadler@apertum.de>
To: linux-sound@vger.kernel.org
Subject: AW: problems with cdda2wav and other audio CDROM ripping software
Date: Tue, 29 Dec 1998 09:44:57 +0000	[thread overview]
Message-ID: <marc-linux-sound-91493029131527@msgid-missing> (raw)


Hi Tony, 

It would be interesting, which version of cdda2wav you use, to which
major/minor-numbers /dev/cdrom points to and if you you use scsi, ide, or
whatever?

Why do you set -quiet so you don't see important informational messages?

Have you tried to rip without -e and -N, and play the resulting .wav-file?
It is possible that only the output to the soundcard isn't working..

You could also try to specify -D in the format "-D bus,id,lun" 
e.g. "-D 0,3,0" works for me.

HTH

Dschau.. Dominik

> -----Ursprüngliche Nachricht-----
> Von:	Tony Nugent [SMTP:Tony.Nugent@usq.edu.au]
> Gesendet am:	Dienstag, 29. Dezember 1998 08:04
> An:	Linux Applications Email List; Linux Sound Email List
> Betreff:	problems with cdda2wav and other audio CDROM ripping
> software
> 
> For the life of me I just can't get cdda2wav to work on my RH5.1/5.2
> box!
> 
> % cdda2wav -q -e -t2 -d0 -N -D /dev/cdrom
> 
> (and lots of variants) just produces ugly noise.  Same for cdparanoia
> - the wav files it creates sound like a ham radio between signals :)
> 
> And I can't get 8hz-mp3 to compile (there's a bunch of missing
> ieee*.h header files).  So "ripperX" is useless.
> 
> I'd really like to do some audio cdrom ripping (to do audio cdrom
> copies and to make some mp3 disks), but I'm at a loss to know what to
> use.
> 
> Can anyone point me in the direction of something (anything!!) that
> *works* ??
> 
> (rpm format would be ideal, but I'll use anything - just as long as it
> works :)
> 
> Many thanks.
> 
> Cheers
> Tony

                 reply	other threads:[~1998-12-29  9:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-sound-91493029131527@msgid-missing \
    --to=dominik.stadler@apertum.de \
    --cc=linux-sound@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