On Thursday, 6 January 2000 at 20:05:21 -0800, Jordan K. Hubbard wrote:
Also, I can now add that cdda2wav does work (hurrah), but it does yelp
that it can't read the CD TOC.
Of course, the mystery is that tosha no longer works yet was not
changed, nor was the ripit script I call tosha from,
In message [EMAIL PROTECTED], Matthe
w Jacob writes:
Hmm! Better hold the 4.0 Code Freeze until this sorts out!
"No"
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before
Jordan K. Hubbard [EMAIL PROTECTED] wrote:
Any other SCSI CD owners here currently using tosha? I'd be
quite interested to know if this is drive-specific.
Works for me.
4.0-CURRENT from December 19,
Toshiba CD-ROM XM-3601TA 0175,
tosha-0.6.
--
Christian "naddy" Weisgerber
Around Yesterday, "Kenneth D. Merry" wrote :
Many of the opinions I've seen recently are that you jitter correction
isn't necessary for most newer CDROM drives. If you want jitter
correction, you can port cdd to CAM.
cdda2wav does jitter correction -
-P sectors --set-overlap
If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive
and try to read data off of it, I get the following behavior:
root@zippy- dd if=/dev/rcd0c bs=2k of=/dev/null
dd: /dev/rcd0c: Invalid argument
0+0 records in
0+0 records out
and on the console at the same time
(cd0:ahc0:0:4:0):
Hmm! Better hold the 4.0 Code Freeze until this sorts out!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
reading raw audio data off a cd with dd did never work for me...
anyway, it would be a good thing(TM) if there was a tool such as
cdparanoia under l*n*x that has all that fancy jitter and scratch
detection and removal (real goodd error correction) and this ones also
really fast (10x speed) when
I believe the cdrdao port had the abilities and some of the code from
paranoia in it.
On Fri, 7 Jan 2000, Karsten W. Rohrbach wrote:
reading raw audio data off a cd with dd did never work for me...
anyway, it would be a good thing(TM) if there was a tool such as
cdparanoia under l*n*x that has
On Fri, Jan 07, 2000 at 02:03:29AM +0100, Karsten W. Rohrbach wrote:
detection and removal (real goodd error correction) and this ones also
really fast (10x speed) when youre reading on a plextor drive (such as
my pxw4220t) or something else that has a native mode for extracting
audio.
One
In message [EMAIL PROTECTED] "Karsten W. Rohrbach" writes:
: i think, theres a port of tosha available, but the last time i tried
: this one it wouldnt work for me so i used the l*n*x box next to my
: workstation...
Last time I tried Tosha it worked w/o a hitch for me and my 1x cdrom
changer :-)
You mean an Adaptec controller, right?
Yes, I guess Adaptec did buy those guys.
Try tosha or cdda2wav and report back on whether or not it works. dd has
never been a supported way to read audio tracks, for the reasons outlined
above. It may be possible in some situations, but it was
On Thu, Jan 06, 2000 at 17:28:23 -0800, Jordan K. Hubbard wrote:
You mean an Adaptec controller, right?
Yes, I guess Adaptec did buy those guys.
Try tosha or cdda2wav and report back on whether or not it works. dd has
never been a supported way to read audio tracks, for the reasons
On Thu, Jan 06, 2000 at 20:05:21 -0800, Jordan K. Hubbard wrote:
Also, I can now add that cdda2wav does work (hurrah), but it does yelp
that it can't read the CD TOC.
Weird. What does cdda2wav identify the drive as? Can you send the output?
(verbose, if there's a verbose switch) That may
On Thu, Jan 06, 2000 at 20:02:34 -0800, Jordan K. Hubbard wrote:
In addition to trying cdda2wav, here's something else you can try in your
tosharc:
"SAF" "" "" 0x28 1 0x82 0 10 0
or:
"SAF" "" "" 0x28 0 0x00 0 10 0
Yep, tried both - no go.
I think what is actually going on is that it doesn't like the 0x82 density
code that most other drives use. So that's what the first error message
likely tells us. (the density is given in the mode select parameter list,
thus the invalid field)
The second error message likely means that
Also, I can now add that cdda2wav does work (hurrah), but it does yelp
that it can't read the CD TOC.
Of course, the mystery is that tosha no longer works yet was not
changed, nor was the ripit script I call tosha from, so something on
our side of the fence also moved with respect to this drive.
In addition to trying cdda2wav, here's something else you can try in your
tosharc:
"SAF" "" "" 0x28 1 0x82 0 10 0
or:
"SAF" "" "" 0x28 0 0x00 0 10 0
Yep, tried both - no go.
The first produces:
(pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0
Kenneth D. Merry [EMAIL PROTECTED] wrote in list.freebsd-current:
Also, you might want to try mailing Oliver Fromme
[EMAIL PROTECTED] (the author of tosha) and see if he
has any idea what it would take to get your drive to function.
I'm reading this thread, and no, I have no idea. :-)
To
On Fri, Jan 07, 2000 at 06:33:47 +0100, Oliver Fromme wrote:
Kenneth D. Merry [EMAIL PROTECTED] wrote in list.freebsd-current:
Also, you might want to try mailing Oliver Fromme
[EMAIL PROTECTED] (the author of tosha) and see if he
has any idea what it would take to get your drive to
I have TOSHIBA DVD-ROM SD-M1201 1R08 on Adaptec 2440U2W and tosha works fine
with it. I used to get the same error messages from tosha just a
couple weeks ago. cdd2wav worked OK. I upgraded to the latest firmware
on both the controller and the drive and error messages disappeared.
Kernel and
Any other SCSI CD owners here currently using tosha? I'd be
quite interested to know if this is drive-specific.
I've used tosha with a "TOSHIBA CD-ROM XM-6201TA 1037" SCSI drive to
read audio data for subsequent mp3 conversion with no problems.
louie
To Unsubscribe: send mail to
I'm reading this thread, and no, I have no idea. :-)
To be honest, I've never heard about an "SAF" drive.
It's a "Smart and Friendly CD-R8020", also sold as the "CD Rocket
Recorder" here in the U.S. It does 20X reads, 8X writes and 4X
re-writes. And no, I don't usually waste my CDR heads on
Kenneth D. Merry [EMAIL PROTECTED] wrote in list.freebsd-current:
[...]
PS: The email address that Ken mentioned isn't valid, please
use [EMAIL PROTECTED].
Then why are you still using it? This is from the headers on your message:
From: Oliver Fromme [EMAIL PROTECTED]
I
On 07-Jan-00 Amancio Hasty wrote:
I just thought that I would need to add an audio intergap between
tracks
but hey if cdrecord can do it great!
Well, if you are burning in Track-At-Once mode then there is a 2 second
gap between the tracks (and you can't do anything about it). To remove
or
24 matches
Mail list logo
