ive been using Burrrn for several weeks now, burning a cd every once in a while. recently i sat down and burned cd's non-stop and found that Burrrn suffers a "burn failure' about every 3rd or 4th disc and ruins the cd. i tried a couple different brands of cd's to no avail. the files that i get the failure with burn with no problem with Musicmatch. i have Burrrn installed on 2 different PC's and the problem exists on both. like the app, as it is a really fast burner, but rather expensive with all the failed burns. is there a fix for this or should i just give up with it??? thanks thanks!!

What kind of error do you get? I think this is rather connected to your hardware. Did you try a burning marathon like that with other software?

Two things to try, if you haven't already.

1. Give the drive a rest every disc or two, to let it cool down.

2. Restart Burrrn every disc or two, to clear out any bad juju.

-brendan

What about settings?..

What would you recommend - ASPI or SPTI and Raw-Driver or not?..

i also have problems with burrrn when setting it up for people who don't have a plextor but a noname burner.

sometimes it doesn't even start to burn and sometimes it failes or creates broken burns (one example: a friend of mine has a noname burner and burns cue+wav (eac ripped). when he puts the burrrn burned cd in his cd player it will always display 0:00 as timeposition and no seeking is possible but it plays fine. we checked it with several cd players. strange but true. no such problems with nero)

the error is something about "textfile" and it appears right after the app shows "text lead-in written". it keeps on running and does not eject the disc when finished. yes, i was burning one disc after another, about enough time to find another file before starting to burn again. i did not shut the app down and restart each time. i do the same thing with Musicmatch Jukebox v8.2 Plus for over 2 years now and never had a failed burn (Yet). i also notice that i have to "guesstimate" if all the audio files will fit on 1 cd, as i see the app already starts burning before it tells me some discs may not be able to overburn. i imagine thats correct operation for Burrrn. MMJB shows me % used on a cd and if its beyond the size of a single cd, it does not burn.
the burners i am using are 1-HP CD-RW/DVD Rom 1-HP CDRW/DVD+-RW (this is the machine i use most) i think these are made by Liteon. and my other PC is Dell CDRW/DVD+-RW.

this site was recommended to me by a mod at kerrazy torrents and so far some other people there have experienced the same problem.
i also see that Burrrn appears to be a memory hog, i usually do other things while burning, but when using Burrrn the PC is too slow to use for anything else and i thought that may cause the failures, so i stopped using the PC when burning, but i still get the failures. i'm thinking the high memory useage is because the app burns so damn fast, am i right??

the drive gets a short rest in between burns while i write tracklists, and move files, etc. i normally dont shut the app down, but i have gotten the failed burn on the first try after opening the app.

I have not had this experience setting up folks with no-name burners. On my box I have a Plextor and a Lite-On and Burrrn works fine for both. YMMV

here are some of the errors i get with a burn failure:
1. corrupt files (same file burned ok with another app)
2. buffer error
3. error-writing of cd text data failed
4. scsi error
5. error-writing failed
6. sense key ox3 medium error segment o
trashed 6 discs out of 20, each file that did not burn wrote fine with another app.

Does Burrrn use ASPI or SPTI? If ASPI, which ASPI driver do you use? If SPTI, do you have daemon tools, Alcohol 120%, or any other virtual optical drive software installed?

-brendan

it is SPTI, no Daemon Tools or Alcohol 120% installed, but i do have Nero 6, Ultra ISO and Power ISO.

You can also try to use magiciso to burn cd.
http://www.magiciso.com/