* Plextor Plexwriter Another Question
@ Martin G. McCormick
` Willem van der Walt<vdwaltw@health.gov.za>
0 siblings, 1 reply; 5+ messages in thread
From: Martin G. McCormick @ UTC (permalink / raw)
To: blinux-list
I am also working on installing a Plextor CD writer on my
Debian Linux system. The biggest problem I have run up against
is a little discontinuity in documentation. I built a kernel
an answered yes to SCSI emulation as well as yes to SCSI CDROM
support and the kernel build went properly as far as I can tell.
I haven't yet actually put the Plextor in to the system
because I know for sure it won't work until I get all the SCSI
issues solved.
The documentation for cdda2wav which extracts .wav files
from CD's says I should use cdrecord -scanbus to find out about
my SCSI devices. When I do that, I get an admonition to use
cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
getting a recording that says to call 911 for help.
There is also a mention in the cdda2wav documentation of
a script called scan_scsi.linux which is supposed to tell all
about what devices one can use. I can't seem to find that
anywhere except for that mention.
This all leads to one final problem which is due, I hope,
to my not knowing the proper SCSI device to use for the IDE CDROM
drive.
If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
This option for cdda2wav is supposed to pipe the digital data
from the CD track right to the sound card.
What happens is that cdda2wav generates a complaint that
this is not the native SCSI channel so cooked mode is to be used.
What I get are brief segments of audio with a scratchy
buzz that I think is related to the raw CD data. It could be
about 75 pops per second. You don't really hear it as a buzz so
much as an interruption in the audio. It's definitely not proper
CD decoding.
My sound card plays other known good wav files properly
so it is the ripping process that is broken at this time.
Also, while all this is going on, the mmotor on the CDROM
drive races and slurps up a buffer full of data which get played
with the static. Then everything falls silent and another shot
of data is loaded and briefly played.
This all makes me feel kind of stupid except that I am
hoping I am just using the wrong representation of the SCSI
emulation.
These various drivers are optimized to do specific things
and I think I am using a SCSI driver that is meant for data
rather than the specific application of audio.
The directory and table of contents information on the
disk come through with no trouble. I haven't read a CD with any
text on it, but normal music CD's have a calendar display of
playing times, etc, and there is no evidence that anything is
wrong with that part of the process.
So my last questions follow: How do I find out the name
of the correct SCSI channel to use? Where do I get this
scan_SCSI.linux script or anything that will point me to the name
of the right device.
Martin McCormick
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Plextor Plexwriter Another Question
Plextor Plexwriter Another Question Martin G. McCormick
@ ` Willem van der Walt<vdwaltw@health.gov.za>
` Brent Harding
0 siblings, 1 reply; 5+ messages in thread
From: Willem van der Walt<vdwaltw@health.gov.za> @ UTC (permalink / raw)
To: blinux-list
On Fri, 4 Jan 2002, Martin G. McCormick wrote:
> I am also working on installing a Plextor CD writer on my
> Debian Linux system. The biggest problem I have run up against
> is a little discontinuity in documentation. I built a kernel
> an answered yes to SCSI emulation as well as yes to SCSI CDROM
> support and the kernel build went properly as far as I can tell.
>
> I haven't yet actually put the Plextor in to the system
> because I know for sure it won't work until I get all the SCSI
> issues solved.
>
If you do not have true scsi chances are good that this command will work:
modprobe ide-scsi
cdrecord dev=0,0,0 --data file.iso
I found cdparanoia to be much better than cdda2wav.
It is a while since i tried cdda2wav it might be better now, but when
i tried it, it did not work well.
One other thing, you need to make sure that your
ide cdrom driver does not grab the cdwriter as if it is a cdrom.
This happens by default if the append hdb2=ide-scsi or simmelar
statement is not in lilo.conf.
There is a good cdwriting-howto that explains these things.
It is werth reading.
regards, Willem
> The documentation for cdda2wav which extracts .wav files
> from CD's says I should use cdrecord -scanbus to find out about
> my SCSI devices. When I do that, I get an admonition to use
> cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
> getting a recording that says to call 911 for help.
>
> There is also a mention in the cdda2wav documentation of
> a script called scan_scsi.linux which is supposed to tell all
> about what devices one can use. I can't seem to find that
> anywhere except for that mention.
>
> This all leads to one final problem which is due, I hope,
> to my not knowing the proper SCSI device to use for the IDE CDROM
> drive.
>
> If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
> This option for cdda2wav is supposed to pipe the digital data
> from the CD track right to the sound card.
>
> What happens is that cdda2wav generates a complaint that
> this is not the native SCSI channel so cooked mode is to be used.
>
> What I get are brief segments of audio with a scratchy
> buzz that I think is related to the raw CD data. It could be
> about 75 pops per second. You don't really hear it as a buzz so
> much as an interruption in the audio. It's definitely not proper
> CD decoding.
>
> My sound card plays other known good wav files properly
> so it is the ripping process that is broken at this time.
>
> Also, while all this is going on, the mmotor on the CDROM
> drive races and slurps up a buffer full of data which get played
> with the static. Then everything falls silent and another shot
> of data is loaded and briefly played.
>
> This all makes me feel kind of stupid except that I am
> hoping I am just using the wrong representation of the SCSI
> emulation.
>
> These various drivers are optimized to do specific things
> and I think I am using a SCSI driver that is meant for data
> rather than the specific application of audio.
>
> The directory and table of contents information on the
> disk come through with no trouble. I haven't read a CD with any
> text on it, but normal music CD's have a calendar display of
> playing times, etc, and there is no evidence that anything is
> wrong with that part of the process.
>
> So my last questions follow: How do I find out the name
> of the correct SCSI channel to use? Where do I get this
> scan_SCSI.linux script or anything that will point me to the name
> of the right device.
>
> Martin McCormick
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Plextor Plexwriter Another Question
` Willem van der Walt<vdwaltw@health.gov.za>
@ ` Brent Harding
` Willem van der Walt<vdwaltw@health.gov.za>
0 siblings, 1 reply; 5+ messages in thread
From: Brent Harding @ UTC (permalink / raw)
To: blinux-list
Any good audio cd burning howto for disk at once mode? I know the .wav's
have to be combined, sound forge will do that in windows, paste mix one in
to another in to another about two seconds from the end of each song, but
track marking will be tough to burn this to CD.
At 09:45 AM 1/7/02 +0500, you wrote:
>On Fri, 4 Jan 2002, Martin G. McCormick wrote:
>
>> I am also working on installing a Plextor CD writer on my
>> Debian Linux system. The biggest problem I have run up against
>> is a little discontinuity in documentation. I built a kernel
>> an answered yes to SCSI emulation as well as yes to SCSI CDROM
>> support and the kernel build went properly as far as I can tell.
>>
>> I haven't yet actually put the Plextor in to the system
>> because I know for sure it won't work until I get all the SCSI
>> issues solved.
>>
>If you do not have true scsi chances are good that this command will work:
>modprobe ide-scsi
>cdrecord dev=0,0,0 --data file.iso
>
>I found cdparanoia to be much better than cdda2wav.
>It is a while since i tried cdda2wav it might be better now, but when
>i tried it, it did not work well.
>One other thing, you need to make sure that your
>ide cdrom driver does not grab the cdwriter as if it is a cdrom.
>This happens by default if the append hdb2=ide-scsi or simmelar
>statement is not in lilo.conf.
>There is a good cdwriting-howto that explains these things.
>It is werth reading.
>regards, Willem
>
>> The documentation for cdda2wav which extracts .wav files
>> from CD's says I should use cdrecord -scanbus to find out about
>> my SCSI devices. When I do that, I get an admonition to use
>> cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
>> getting a recording that says to call 911 for help.
>>
>> There is also a mention in the cdda2wav documentation of
>> a script called scan_scsi.linux which is supposed to tell all
>> about what devices one can use. I can't seem to find that
>> anywhere except for that mention.
>>
>> This all leads to one final problem which is due, I hope,
>> to my not knowing the proper SCSI device to use for the IDE CDROM
>> drive.
>>
>> If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
>> This option for cdda2wav is supposed to pipe the digital data
>> from the CD track right to the sound card.
>>
>> What happens is that cdda2wav generates a complaint that
>> this is not the native SCSI channel so cooked mode is to be used.
>>
>> What I get are brief segments of audio with a scratchy
>> buzz that I think is related to the raw CD data. It could be
>> about 75 pops per second. You don't really hear it as a buzz so
>> much as an interruption in the audio. It's definitely not proper
>> CD decoding.
>>
>> My sound card plays other known good wav files properly
>> so it is the ripping process that is broken at this time.
>>
>> Also, while all this is going on, the mmotor on the CDROM
>> drive races and slurps up a buffer full of data which get played
>> with the static. Then everything falls silent and another shot
>> of data is loaded and briefly played.
>>
>> This all makes me feel kind of stupid except that I am
>> hoping I am just using the wrong representation of the SCSI
>> emulation.
>>
>> These various drivers are optimized to do specific things
>> and I think I am using a SCSI driver that is meant for data
>> rather than the specific application of audio.
>>
>> The directory and table of contents information on the
>> disk come through with no trouble. I haven't read a CD with any
>> text on it, but normal music CD's have a calendar display of
>> playing times, etc, and there is no evidence that anything is
>> wrong with that part of the process.
>>
>> So my last questions follow: How do I find out the name
>> of the correct SCSI channel to use? Where do I get this
>> scan_SCSI.linux script or anything that will point me to the name
>> of the right device.
>>
>> Martin McCormick
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Plextor Plexwriter Another Question
` Brent Harding
@ ` Willem van der Walt<vdwaltw@health.gov.za>
0 siblings, 0 replies; 5+ messages in thread
From: Willem van der Walt<vdwaltw@health.gov.za> @ UTC (permalink / raw)
To: Brent Harding; +Cc: blinux-list
Hi,
cdrdao is for writing in disk at once mode.
I am using it to write my audio cd disks.
I am not sure if i understand what you want to do, but
you among other things, can do the following with cdrdao.
read an audio cd to create a toc file, a table of contents file that is
used for writing a cd. it then creates a file data.bin containing the
music.
The toc file describes where in data.bin, the various tracks start, what
the pregap is etc.
When i make a cd from my own wav files, i use it slightly differently.
Each song is in its own wav file.
If one gives a length of zero for the file, cdrdao assumes you want to
use the full file as one track. You can specify the length of the pregap
(silence between songs), for each track. The pregaps can differ in length
or be ommitted.
Note the wav files must be recorded at cd quality.
ie. they must have a sample rate of 44100, be in sterio and be at 16 bit
per
sample.
If the files are not in that format, one can use sox to convert them
before you write.
hth, Willem
On Mon, 7 Jan 2002, Brent Harding wrote:
> Any good audio cd burning howto for disk at once mode? I know the .wav's
> have to be combined, sound forge will do that in windows, paste mix one in
> to another in to another about two seconds from the end of each song, but
> track marking will be tough to burn this to CD.
> At 09:45 AM 1/7/02 +0500, you wrote:
> >On Fri, 4 Jan 2002, Martin G. McCormick wrote:
> >
> >> I am also working on installing a Plextor CD writer on my
> >> Debian Linux system. The biggest problem I have run up against
> >> is a little discontinuity in documentation. I built a kernel
> >> an answered yes to SCSI emulation as well as yes to SCSI CDROM
> >> support and the kernel build went properly as far as I can tell.
> >>
> >> I haven't yet actually put the Plextor in to the system
> >> because I know for sure it won't work until I get all the SCSI
> >> issues solved.
> >>
> >If you do not have true scsi chances are good that this command will work:
> >modprobe ide-scsi
> >cdrecord dev=0,0,0 --data file.iso
> >
> >I found cdparanoia to be much better than cdda2wav.
> >It is a while since i tried cdda2wav it might be better now, but when
> >i tried it, it did not work well.
> >One other thing, you need to make sure that your
> >ide cdrom driver does not grab the cdwriter as if it is a cdrom.
> >This happens by default if the append hdb2=ide-scsi or simmelar
> >statement is not in lilo.conf.
> >There is a good cdwriting-howto that explains these things.
> >It is werth reading.
> >regards, Willem
> >
> >> The documentation for cdda2wav which extracts .wav files
> >> from CD's says I should use cdrecord -scanbus to find out about
> >> my SCSI devices. When I do that, I get an admonition to use
> >> cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
> >> getting a recording that says to call 911 for help.
> >>
> >> There is also a mention in the cdda2wav documentation of
> >> a script called scan_scsi.linux which is supposed to tell all
> >> about what devices one can use. I can't seem to find that
> >> anywhere except for that mention.
> >>
> >> This all leads to one final problem which is due, I hope,
> >> to my not knowing the proper SCSI device to use for the IDE CDROM
> >> drive.
> >>
> >> If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
> >> This option for cdda2wav is supposed to pipe the digital data
> >> from the CD track right to the sound card.
> >>
> >> What happens is that cdda2wav generates a complaint that
> >> this is not the native SCSI channel so cooked mode is to be used.
> >>
> >> What I get are brief segments of audio with a scratchy
> >> buzz that I think is related to the raw CD data. It could be
> >> about 75 pops per second. You don't really hear it as a buzz so
> >> much as an interruption in the audio. It's definitely not proper
> >> CD decoding.
> >>
> >> My sound card plays other known good wav files properly
> >> so it is the ripping process that is broken at this time.
> >>
> >> Also, while all this is going on, the mmotor on the CDROM
> >> drive races and slurps up a buffer full of data which get played
> >> with the static. Then everything falls silent and another shot
> >> of data is loaded and briefly played.
> >>
> >> This all makes me feel kind of stupid except that I am
> >> hoping I am just using the wrong representation of the SCSI
> >> emulation.
> >>
> >> These various drivers are optimized to do specific things
> >> and I think I am using a SCSI driver that is meant for data
> >> rather than the specific application of audio.
> >>
> >> The directory and table of contents information on the
> >> disk come through with no trouble. I haven't read a CD with any
> >> text on it, but normal music CD's have a calendar display of
> >> playing times, etc, and there is no evidence that anything is
> >> wrong with that part of the process.
> >>
> >> So my last questions follow: How do I find out the name
> >> of the correct SCSI channel to use? Where do I get this
> >> scan_SCSI.linux script or anything that will point me to the name
> >> of the right device.
> >>
> >> Martin McCormick
> >>
> >>
> >>
> >> _______________________________________________
> >> Blinux-list mailing list
> >> Blinux-list@redhat.com
> >> https://listman.redhat.com/mailman/listinfo/blinux-list
> >>
> >
> >
> >
> >_______________________________________________
> >Blinux-list mailing list
> >Blinux-list@redhat.com
> >https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Plextor Plexwriter Another Question
@ Martin G. McCormick
0 siblings, 0 replies; 5+ messages in thread
From: Martin G. McCormick @ UTC (permalink / raw)
To: blinux-list
Thank you. I have also found that I don't have /dev/sgx
devices installed and that is most likely the biggest problem.
I will have to give cdparanoia a try but first I must get
a valid SCSI device since cdrecord and cdda2wav as well as
cdparanoia all want to see a SCSI adapter.
It's all so close and still just out of reach.
I suspect that when it is working, I will be able to rip
tracks from audio disks that will then play correctly as there
appears to be nothing at all wrong with the existing CDROM drive
that is in the system. When it is reading data CDROM's, it hums
right along and does what it should.
Martin
"Willem van der Walt<vdwaltw@health.gov.za>" writes:
>If you do not have true scsi chances are good that this command will work:
>modprobe ide-scsi
>cdrecord dev=0,0,0 --data file.iso
>
>I found cdparanoia to be much better than cdda2wav.
>It is a while since i tried cdda2wav it might be better now, but when
>i tried it, it did not work well.
>One other thing, you need to make sure that your
>ide cdrom driver does not grab the cdwriter as if it is a cdrom.
>This happens by default if the append hdb2=ide-scsi or simmelar
>statement is not in lilo.conf.
>There is a good cdwriting-howto that explains these things.
>It is werth reading.
>regards, Willem
>
>> The documentation for cdda2wav which extracts .wav files
>> from CD's says I should use cdrecord -scanbus to find out about
>> my SCSI devices. When I do that, I get an admonition to use
>> cdrecord -scanbus from cdrecord;-- sort of like calling 911 and
>> getting a recording that says to call 911 for help.
>>
>> There is also a mention in the cdda2wav documentation of
>> a script called scan_scsi.linux which is supposed to tell all
>> about what devices one can use. I can't seem to find that
>> anywhere except for that mention.
>>
>> This all leads to one final problem which is due, I hope,
>> to my not knowing the proper SCSI device to use for the IDE CDROM
>> drive.
>>
>> If I use cdda2wav -e -D/dev/cdrom, it all tries to work.
>> This option for cdda2wav is supposed to pipe the digital data
>> from the CD track right to the sound card.
>>
>> What happens is that cdda2wav generates a complaint that
>> this is not the native SCSI channel so cooked mode is to be used.
>>
>> What I get are brief segments of audio with a scratchy
>> buzz that I think is related to the raw CD data. It could be
>> about 75 pops per second. You don't really hear it as a buzz so
>> much as an interruption in the audio. It's definitely not proper
>> CD decoding.
>>
>> My sound card plays other known good wav files properly
>> so it is the ripping process that is broken at this time.
>>
>> Also, while all this is going on, the mmotor on the CDROM
>> drive races and slurps up a buffer full of data which get played
>> with the static. Then everything falls silent and another shot
>> of data is loaded and briefly played.
>>
>> This all makes me feel kind of stupid except that I am
>> hoping I am just using the wrong representation of the SCSI
>> emulation.
>>
>> These various drivers are optimized to do specific things
>> and I think I am using a SCSI driver that is meant for data
>> rather than the specific application of audio.
>>
>> The directory and table of contents information on the
>> disk come through with no trouble. I haven't read a CD with any
>> text on it, but normal music CD's have a calendar display of
>> playing times, etc, and there is no evidence that anything is
>> wrong with that part of the process.
>>
>> So my last questions follow: How do I find out the name
>> of the correct SCSI channel to use? Where do I get this
>> scan_SCSI.linux script or anything that will point me to the name
>> of the right device.
>>
>> Martin McCormick
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Plextor Plexwriter Another Question Martin G. McCormick
` Willem van der Walt<vdwaltw@health.gov.za>
` Brent Harding
` Willem van der Walt<vdwaltw@health.gov.za>
Martin G. McCormick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).