SEO

Anyody got a clue about cdparanoia? I'm running Debian and can play
CDs just fine. cdparanoia happily delivers all the track names,
creates the album directory, creates a track01.cdda.wav file at
44 bytes and stops. I've tried just about everything I can think
of -- hours and hours at this. Looked through all the answers I
could locate online and can't find a thing.

I've tried both the readonly and readwrite drives, /dev/cdrom and
/dev/cdrom1. They are, respectively, /dev/sg0 and /dev/sg1
respectively. I've tried various values of the -o parameter,

cdparanoia -d "/dev/cdrom" -g "/dev/sg0" -B -- "4-5"

I've tried the -T switch, the -n switch. It majestically and uselessly
creates the 44 byte .wav file. I despair.

On Sun, 26 Sep 2004 21:22:02 +0000, Kosmo Threadbane wrote:

> I've tried both the readonly and readwrite drives, /dev/cdrom and
> /dev/cdrom1. They are, respectively, /dev/sg0 and /dev/sg1
> respectively. I've tried various values of the -o parameter,

you're saying /dev/cdrom is a symbolic link to /dev/sg0 etc?

if so, i think that's probably your problem!

on my system (which does cd ripping ok), /dev/cdrom is a symlink to
/dev/scd0 - which i believe is the correct device for ripping audio from
a cd with. if you try using "/dev/scd0" instead of "/dev/cdrom" you might
get somewhere.

> cdparanoia -d "/dev/cdrom" -g "/dev/sg0" -B -- "4-5"

for a start, you don't need the "--" in this situation, it's only needed
when you're doing something like "-5" (i.e., rip to track 5) - so the "-5"
isn't interpreted as an option flag (which is would be otherwise, as
options begin with a "-"). secondly, you *definitely* don't need the
"-g /dev/sg0" option - unless you've got some weird, non-standard setup.

thirdly, have you tried using 'grip'? it's a gui front end to cdparanoia
and lame that can rip whatever tracks you select (by ticking the
individual tracks) and therefore save worrying about cdparanoia command
lines, and optionally encode them as mp3s. i'm quite at home with
command-line stuff, but i find grip a much handier tool than raw
cdparanoia.

will

Kosmo Threadbane wrote:

>
> Anyody got a clue about cdparanoia? I'm running Debian and can play
> CDs just fine. cdparanoia happily delivers all the track names,
> creates the album directory, creates a track01.cdda.wav file at
> 44 bytes and stops. I've tried just about everything I can think
> of -- hours and hours at this. Looked through all the answers I
> could locate online and can't find a thing.
>
> I've tried both the readonly and readwrite drives, /dev/cdrom and
> /dev/cdrom1. They are, respectively, /dev/sg0 and /dev/sg1
> respectively. I've tried various values of the -o parameter,
>
> cdparanoia -d "/dev/cdrom" -g "/dev/sg0" -B -- "4-5"
>
> I've tried the -T switch, the -n switch. It majestically and uselessly
> creates the 44 byte .wav file. I despair.

You know, you never bother to say what you want to do. This greatly limits
your options in complaining about it.

--
Paul Lutus
http://www.arachnoid.com

Kosmo Threadbane wrote:

> I've tried the -T switch, the -n switch. It majestically and uselessly
> creates the 44 byte .wav file. I despair.

Have you tried Grip? It's a great GUI wrapper around cdparanoia (and
oggenc and various other compression tools) which should eliminate the
one set of possible mistakes.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact
Now Playing ~ ./toad_the_wet_sprocket/ps/03_all_i_want_remix.ogg

Paul Lutus <nospam@nosite.zzz> wrote:
>
>Kosmo Threadbane wrote:
>
>>
>> Anyody got a clue about cdparanoia? I'm running Debian and can play
[...
>You know, you never bother to say what you want to do. This greatly limits
>your options in complaining about it.
>

I'm trying to copy an audio track from cd to a .wav file on disk --
well, actually I'd like to wind up with an mp3 or some other
compressed format, but a .wav file would be a nice intermediate
victory. 8^)

will kemp <will@xxxx.swaggie.net> wrote:
>
>On Sun, 26 Sep 2004 21:22:02 +0000, Kosmo Threadbane wrote:
>
>> I've tried both the readonly and readwrite drives, /dev/cdrom and
>> /dev/cdrom1. They are, respectively, /dev/sg0 and /dev/sg1
>> respectively. I've tried various values of the -o parameter,
>
>you're saying /dev/cdrom is a symbolic link to /dev/sg0 etc?

Yes.

>
>if so, i think that's probably your problem!
>
>on my system (which does cd ripping ok), /dev/cdrom is a symlink to
>/dev/scd0 - which i believe is the correct device for ripping audio from
>a cd with. if you try using "/dev/scd0" instead of "/dev/cdrom" you might
>get somewhere.
>

>> cdparanoia -d "/dev/cdrom" -g "/dev/sg0" -B -- "4-5"

cdparanoia -d "/dev/scd0" -B -- 4-5

(== PROGRESS == [ | ...... 00 ] == :^D . ==)

And there it sits. 8^)

I think I started with scd0 to begin with, then tried sg0 because I found
it in the /proc/scsi world and decided to go with that for a while.

>
>for a start, you don't need the "--" in this situation, it's only needed
>when you're doing something like "-5" (i.e., rip to track 5) - so the "-5"
>isn't interpreted as an option flag (which is would be otherwise, as

Well, yes...

>options begin with a "-"). secondly, you *definitely* don't need the
>"-g /dev/sg0" option - unless you've got some weird, non-standard setup.
>
>thirdly, have you tried using 'grip'? it's a gui front end to cdparanoia
>and lame that can rip whatever tracks you select (by ticking the
>individual tracks) and therefore save worrying about cdparanoia command
>lines, and optionally encode them as mp3s. i'm quite at home with
>command-line stuff, but i find grip a much handier tool than raw
>cdparanoia.
>

Actually, I started with rip. It just disappeared waiting for cdparanoia
to tell it something interesting, which it never does. No errors, no .wav.
A friend at work suggested that the CD is copy protected, which it is,
but that's just a header setting. I don't see why it wouldn't at least
finish producing a bogus .wav file, unless there's something in the
first few sectors of each track that makes it compute weird, but I've
tried the -t switch and it doesn't help.

Like I said, it shows all the tracks and their correct titles, the
artist, etc., so it CAN read the cd a little, apparently.

Toby Inkster <usenet200409@tobyinkster.co.uk> wrote:
>
>Kosmo Threadbane wrote:
>
>> I've tried the -T switch, the -n switch. It majestically and uselessly
>> creates the 44 byte .wav file. I despair.
>
>Have you tried Grip? It's a great GUI wrapper around cdparanoia (and
>oggenc and various other compression tools) which should eliminate the
>one set of possible mistakes.
>

I did start with rip, but it never gave me any error because it
hangs on the cdparanoia call, which doesn't have produce errors -- it
just doesn't do anything. Actually, it says it's DONE with track04,
I think!

(== PROGRESS == [> | ...... 00 ] == :^D ==)

Like I said in the previous post, I see the header info just fine, but
doesn't read the audio sectors.



>--
>Toby A Inkster BSc (Hons) ARCS
>Contact Me ~ http://tobyinkster.co.uk/contact
>Now Playing ~ ./toad_the_wet_sprocket/ps/03_all_i_want_remix.ogg
>

will kemp <will@xxxx.swaggie.net> wrote:
>
>On Sun, 26 Sep 2004 21:22:02 +0000, Kosmo Threadbane wrote:
>
>> I've tried both the readonly and readwrite drives, /dev/cdrom and
>> /dev/cdrom1. They are, respectively, /dev/sg0 and /dev/sg1
>> respectively. I've tried various values of the -o parameter,
>
>you're saying /dev/cdrom is a symbolic link to /dev/sg0 etc?
>
>if so, i think that's probably your problem!

No. /dev/cdrom is a link to /dev/scd0. I STARTED with that, then
after reading some stuff where other people had similar problems, I
gave the sg0 a go because I found it in /proc/scsi. Actually,
they both almost do the same thing. When I try
>
>> cdparanoia -d "/dev/cdrom" -g "/dev/scd0" -B -- 4-5
>

It just says that /dev/scd0 is a readonly file system and dies
immediately. (Why it would care, I have no idea, since all it
should be doing is reading anyhow -- unless it's the device control
itself.)

The other thing that bugs me is that it sees the cdrom as uncooked.
Apparently cdparanoia only works with cooked devices.

BTW, one drive is a SONY and the other is a NEC, the former a readonly
and the latter readwrite. Hard to believe that both would give
identical results.

Kosmo Threadbane <zeteticCXL@hq.eac> writes:

> Actually, I started with rip. It just disappeared waiting for cdparanoia
> to tell it something interesting, which it never does. No errors, no .wav.
> A friend at work suggested that the CD is copy protected, which it is,
> but that's just a header setting. I don't see why it wouldn't at least
> finish producing a bogus .wav file, unless there's something in the
> first few sectors of each track that makes it compute weird, but I've
> tried the -t switch and it doesn't help.
>
> Like I said, it shows all the tracks and their correct titles, the
> artist, etc., so it CAN read the cd a little, apparently.

Have you tried with different readers? A friend of mine failed to rip
a copy protected CD, whereas it could be read without problems with my
machine. FWIW, I used a Samsung CD-RW/DVD drive. I can't remember
what the other one was, but it was a read-only unit.

--
Måns Rullgård
mru@mru.ath.cx

Phil Deane wrote:

> I presume you have tried more than one cd?

Kosmo, pay attention to this one!

Could be a corrupt CD -- there are a lot of them about these days. Try a
CD about 3 years old.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact