Re: Possible way to get better bug reports/support requests for CDRecord

2002-10-28 Thread Lourens Veen
On Monday 28 Oct 2002 7:07 am, [EMAIL PROTECTED] wrote:
 Lourens Veen [EMAIL PROTECTED] writes:
 snip - have explanation of how to submit bug reports when an 
error occurs

 Well, this kind of crash handler is just a signal handler - some
 code which is executed when the operating system tells a process
 (a program being executed) that it has done something way wrong.
 It replaces the default behaviour of dumping the core. So the
 process has to do something what the operating system can
 recognize as being wrong.

I know, but that's not what I meant. CDRecord already has signal 
handlers, although not for SIGSEGV (IMHO it would be good defensive 
programming if it had one, if only to say CDRecord crashed, check 
your hardware because the software is perfect). Anyway, what I 
mean is that if something unexpected occurs, which may be a SIGSEGV 
(no I never had one with CDRecord either) or a SCSI error, or 
whatever else that's unexpected, the user should get some 
information on how to deal with it. Joe User isn't going to search 
the mail archives, and isn't going to give a decent bug report, 
unless there's a big fat do _this_ and exactly _this_ or we won't 
help you message to go with the error message. And if he doesn't 
search the mail archives or send a decent bug report, but instead 
send a mail that says it doesn't work then Jörg is going to give 
another rant about how he spends so much time developing CDRecord 
and that everybody is stupid, which we're trying to avoid, right?

 By now I never saw cdrecord crashing in this way. cdrecord
 certainly outputs SCSI error messages if something goes wrong,
 but these are errors detected by cdrecord itself. The operating
 system stays completely cool about them.

Again, it's not a technical point I'm trying to make, I'm looking at 
it from a user-interface point of view.

 So what's needed is some translation of plain SCSI error messages
 to instructions what could be done to fix it. However this is a
 feature already wished for a dozen times, which requires
 knowledge about:

I know, I took part in that discussion.

Lourens
-- 
GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Problems with BTC BCE1610IM burner under linux.

2002-10-28 Thread satan
I have problems with BTC BCE1610IM burner under linux. 

My software version is: Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 
1995-2001 J?rg Schillin on Linux 2.4.18. 

I have try with cdrecord 1.11 but I have a same result. 

cdrecord -scanbus prints: 

Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J?rg Schilling
Linux sg driver version: 3.1.22
Using libscg version 'schily-0.5'
scsibus0:
  0,0,0 0) 'COMPAQ  ' 'BD01874554  ' '3B05' Disk
  0,1,0 1) *
  0,2,0 2) 'SEAGATE ' 'ST336706LW  ' '0108' Disk
  0,3,0 3) *
  0,4,0 4) *
  0,5,0 5) *
  0,6,0 6) *
  0,7,0 7) *
scsibus1:
  1,0,0   100) *
  1,1,0   101) *
  1,2,0   102) *
  1,3,0   103) *
  1,4,0   104) *
  1,5,0   105) *
  1,6,0   106) 'COMPAQ  ' 'SDT-9000' '4.20' Removable Tape
  1,7,0   107) *
scsibus2:
  2,0,0   200) 'BTC ' 'BCE1610IM   ' '0.19' Removable CD-ROM
  2,1,0   201) *
  2,2,0   202) *
  2,3,0   203) *
  2,4,0   204) *
  2,5,0   205) *
  2,6,0   206) *
  2,7,0   207) * 

And kernel modules:
#lsmod
Module  Size  Used by
cdrom  28800   0  (unused)
ide-scsi7664   0
lp  6752   0  (unused)
parport_pc 12688   1
parport14816   1  [lp parport_pc] 


What can I do to put in action this burner ?
I hope I get reply on my message.
10x and sorry for my bad english.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cdrtools-1.11a39 ready

2002-10-28 Thread Andy Polyakov
 -   A new experimental feature

I was under impression that the project was in feature-freeze stage...
Well, whatever...

 of the -immed flag is  to
 tell  cdrecord  to try to wait short times wile writing
 to the media.
 
 As this is an experimental feature, I would like to get feedback.

If it's introduced so late and so experimental, then it probably should
be denoted with distinct command-line flag.

The code in question is engaged only if(verbose). Why? Shouldn't it be
engaged regardless verbosity?

Some commentary or longer variable names would help to audit the code.
After a short look I can't tell when exactly usleep is called... Is it
when drive buffer is reported full as one would normally expect?

A.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: cdrtools-1.11a39 ready

2002-10-28 Thread Joerg Schilling

From: Andy Polyakov [EMAIL PROTECTED]
 -   A new experimental feature

I was under impression that the project was in feature-freeze stage...

If you are able to add  50 lines at a single well known place and the code does
definitely not affect other features, what would you do?

Well, whatever...

 of the -immed flag is  to
 tell  cdrecord  to try to wait short times wile writing
 to the media.
 
 As this is an experimental feature, I would like to get feedback.

If it's introduced so late and so experimental, then it probably should
be denoted with distinct command-line flag.

The code in question is engaged only if(verbose). Why? Shouldn't it be
engaged regardless verbosity?

Some commentary or longer variable names would help to audit the code.
After a short look I can't tell when exactly usleep is called... Is it
when drive buffer is reported full as one would normally expect?

The code is audited ;-)

And please note that the -immed flag has been marked experimental too.


Jörg

 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED]   (uni)  If you don't have iso-8859-1
   [EMAIL PROTECTED]   (work) chars I am Jorg Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




MP3 packing format

2002-10-28 Thread Hanspeter Roth
Hello,

is there a standard pertaining the format how MP3 should be packed
onto a CD? Is it audio, data or does it have it's own packing
format?

-Hanspeter


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: MP3 packing format

2002-10-28 Thread Matthias . Riese
Hanspeter Roth [EMAIL PROTECTED] writes:

 Hello,
 
 is there a standard pertaining the format how MP3 should be packed
 onto a CD? Is it audio, data or does it have it's own packing
 format?

That depends on the type of player you want to be able to use your CD
with.

Standard CD player just accept audio CDs (CDDA format). So you have to
convert your MP3 to Wave files and then burn as an audio CD (with a
max of ~74 minutes play time).

MP3 CD player and computers can handle both audio CDs and data CDs
(ISO9660 format) and this is also the only way to burn MP3 as-is
giving you lots of hours of play time per CD.

Regards, Matthias


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: cdrtools-1.11a39 ready

2002-10-28 Thread Joerg Schilling

From: Andy Polyakov [EMAIL PROTECTED]

 The code is audited ;-)

Then why are you asking for feedback;-)

Because the code interacts with control in the drive
I had some control oscillations in the first version.

But seriously speaking I'd really like to figure out when exactly usleep
is called. I'd appreciate if you could answer this question in some way
[note that I don't demand an answer, but express an appreciation in case
you would find an opportunity to do so]. Commentary or longer variable
names is nothing but an alternative to explicitely answering the
question:-)

I usually use comments when the code is non-obvious.

Sorry, I am on the Linux WOrld expo in Frankfurt and like to read my mail
quickly


You didn't comment on/answer the 2nd question. I.e. is it intentional
that the code in question is engaged only if(verbose)? If it is, then my

This looks like a bug ;-)

Well, it is experimental and I would like to help people with rotten notebooks


Jörg

 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED]   (uni)  If you don't have iso-8859-1
   [EMAIL PROTECTED]   (work) chars I am Jorg Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: P Q in Raw Mode

2002-10-28 Thread Joerg Schilling
From: Lourens Veen [EMAIL PROTECTED]

 =09I have a large wav file that I want to break into several tracks
 without 2 secs of a silence between tracks ( i.e. continuous
 audio). I know how to do the job with goldenhawk. Can anyone
 point me to where this is documented in the cdrecord? It would
 require being able to define the write data and PQ independently.
 (This is done in the .inf in Goldenhawk) I have been unable to
 find it, but then again my wife claims I can't find anything.

Why don't you just split up the WAV file with sox or something and=20
then burn the tracks in dao (sao) mode? That would seem to be the=20
easiest way to me. Alternatively, have you looked at cdrdao? That=20
seems to be more geared towards this type of task than cdrecord.

cdrdao makes it more complicated without improvement.

Cdrecord does not introduce 2 seconds between two tracks, just read the
man page and follow the instructions.

Jörg

 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
   [EMAIL PROTECTED]   (uni)  If you don't have iso-8859-1
   [EMAIL PROTECTED]   (work) chars I am Jorg Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




RE: P Q in Raw Mode

2002-10-28 Thread Basile, Greg
Hello again,

Let me be more specific. I assume the command I want is ( from the
man page):

 cdrecord -v dev=2,0 -dao -useinfo  20minuteaudiofile.wav

I assume I can create a 20minuteaudiofile.inf that will give me a
track change every 2 minutes. 

If the above is correct, my specific question is:

  Where is the format of the *.inf file documented? I was unable to find
this in the man pages.


Thanks,
Greg

-Original Message-
From: Joerg Schilling [mailto:schilling;fokus.gmd.de]
Sent: Monday, October 28, 2002 10:42 AM
To: [EMAIL PROTECTED]; Basile, Greg; [EMAIL PROTECTED]
Subject: Re: P  Q in Raw Mode


From: Lourens Veen [EMAIL PROTECTED]

 =09I have a large wav file that I want to break into several tracks
 without 2 secs of a silence between tracks ( i.e. continuous
 audio). I know how to do the job with goldenhawk. Can anyone
 point me to where this is documented in the cdrecord? It would
 require being able to define the write data and PQ independently.
 (This is done in the .inf in Goldenhawk) I have been unable to
 find it, but then again my wife claims I can't find anything.

Why don't you just split up the WAV file with sox or something and=20
then burn the tracks in dao (sao) mode? That would seem to be the=20
easiest way to me. Alternatively, have you looked at cdrdao? That=20
seems to be more geared towards this type of task than cdrecord.

cdrdao makes it more complicated without improvement.

Cdrecord does not introduce 2 seconds between two tracks, just read the
man page and follow the instructions.

Jörg

 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353
Berlin
   [EMAIL PROTECTED]   (uni)  If you don't have iso-8859-1
   [EMAIL PROTECTED]   (work) chars I am Jorg Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling
ftp://ftp.fokus.gmd.de/pub/unix


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: MP3 packing format

2002-10-28 Thread Carsten Neumann
On Mon, 28 Oct 2002, Hanspeter Roth wrote:
 Hello,
 
 is there a standard pertaining the format how MP3 should be packed
 onto a CD? Is it audio, data or does it have it's own packing
 format?
 
 -Hanspeter

Hi Hanspeter,

I've tried this some months ago.

A short info is at:
http://www.cdrfaq.org/faq03.html#S3-27

You should use 128kbps, plain stereo - whatever this means. ;-)
I used `-m s' for lame.

You have to create an ISO9660 file system, 8.3 filenames are a good choice,
nested directories should be no problem on (some) MP3-CD players.

You have to play around with your MP3 encoder's and mkisofs' options
to find out what your MP3-CD player suppports.

HTH, kind regards,

Carsten


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: MP3 packing format

2002-10-28 Thread Frank Hage
On 2002.10.28, Hanspeter Roth wrote:
: 
: Hello,
: 
: is there a standard pertaining the format how MP3 should be packed
: onto a CD? Is it audio, data or does it have it's own packing
: format?
: 
: -Hanspeter
: 

I don't think there's a standard. I think it depends on the player.

I recently purchased a cheap CD/MP3 player. It was somewhat picky about
how the disk and files were written before it had all its functionality. I
get good results writing 128Kbps mp3's on plain IS09960 (with 32 character
filenames enabled).  ID3 tags in the MP3 files are used to provide song
title and artist info as the music plays. My player has no problems
traversing directories. Names do not have to be 8.3  I organised my
files by artist/album/*.mp3 etc.

-Cheers,

-- 
Frank Hage  [EMAIL PROTECTED]
National Center for Atmospheric Research


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]