Re: ermm you guessed it! trouble with cdrecord/gcombust/gtoaster

2000-06-21 Thread C.Hays

ok, thanks!!

Actually, i went back and tried a command line nurn this morning MAKING SURE to
-swab..that didnt work either, prolly due to my doing something else wrong.. 

I think I have it figured out though, i went back and reinstalled the older
version of gtoaster (v.1 i believe) and am burning an audio cd as i write..i
think this is actually working, the burn times on the tracks seem relaistic
enough, ie, ..no 30 second tracks. The lesson Ive learned is not to fix it if
isnt broke :), in other words unless I'll die without the newer version,
sometimes it best for me to stick to what i know.

Thanks again for your help, i should run to the store for more 80 minutes cds,
unfortunately i wasted 10 or so in my aforementioned struggle :<

Regards, 

Cherie


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






Re: ermm you guessed it! trouble with cdrecord/gcombust/gtoaster

2000-06-21 Thread Jonas Munsin

Hello,

On Tue, Jun 20, 2000 at 06:02:35PM -0500, C.Hays wrote:
> undecipherable default settings.. Now im using gcombust, which seems MUCH nicer
> btw, and heres the scoop:

[...]

> No errors !!! Except the cd is ALL static. No music, no nada, sounds just like
> the TV at 430 am on a sunday :<
> 
> And do i ask, does anyone know what the earlier errors represent?? And lastly,
> whats causing the static and how do i get rid of it
> 

As someone said, the byte-order is wrong, toggle the swab option in gcombust.
gcombust has a detect-scsi button that is supposed to set the swab option right
(using cdrecord). I've only tested it with my drive, but it should work..



-- 
Jonas Munsin <[EMAIL PROTECTED]>   KeyID: 1024/98A0C47D
Key fingerprint 9F 69 9D 96 80 DD 8E D0  D8 A0 30 66 F9 55 63 B4
Debian GNU/Linux Developer comp.science student @ Åbo Akademi University


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






RE: ermm you guessed it! trouble with cdrecord/gcombust/gtoaster

2000-06-21 Thread Karl-Heinz Herrmann

Hi!

> No errors !!! Except the cd is ALL static. No music, no nada, sounds
> just like the TV at 430 am on a sunday :<
> 
> whats causing the static and how do i get rid of it

Wrong byte-order. Somehow the Frontend didn't use the right Byteorder
(Bigendian/Littelendian) for your drive. cdrecord would usually ask the
drive and when it know the inputfileformat will set it right.
But with raw data cdrecord doesn't know what byte order the input
has

Try to use the commandline (cdda2wav and cdrecord) and write the files
as wav files (they have a well defined byteorder).

Or have a look if gcombust has a byteswap option. That would probably
do as well. 

K.-H.



--
E-Mail: Karl-Heinz Herrmann <[EMAIL PROTECTED]>
Date: 21-Jun-00  Time: 11:59:55
--


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