All Activity

20 years later and still can't burn without complete wrestling match! I haven't burned a cd in a few years but, since the inception of CD burning, it has always been a wrestling match. I have a new burner LG BP50/NB40 and some new audio cds. I added my mp3s to the playlist and clicked burn only to find out that, CDBurnerXP thinks my disk is a blu-ray. It is not. When I click burn, it says, "the following disc is required BR-R". So, for the heck of it, I put in a blank BR-R and it still doesn't work. Why weren't all these bugs straightened out and standardized 20 years ago?

I have some home movies on VHS that I have recently copied to DVD with a VCR/DVD Recorder combo. I would like to make copies of these DVDs for other family members but the tapes are old and fragile so I don't want to keep using the VCR to make more DVDs. I was told that if I brought the DVD vob files into Adobe Premier Elements, the copied DVD would lose quality due to being compressed to MPEG2 twice. Which CDBurnerXP option would just copy the data from the DVD either to the hard drive or directly to a new burned DVD without encoding/decoding or otherwise messing with the quality? I was not sure whether to use the Data disc, Video DVD or Copy or grab disc option. My PC has 2 optical drives so a direct copy would be easiest. Windows 10 20H2

Puedes probar a cortar 80 minutos con un progama de edición como https://www.audacityteam.org/audacity Saludos MrCos

Hi, Got a sudden and very frustrating problem. After burning 'Audio Discs' with CDBurnerXP for many years (from MP3s) without any problems - always using using Verbatim CD-Rs - I'm now getting the follow error message every time: "CStarBurn_SCSITransportSPTI: ExecuteCDBO: Command failed - Internal SDK Error", also complaining about "low-quality media", etc. What happened is this. I got myself a brand new high-end(ish) PC with the specs listed below, so plugged-in my trusty external DVD burner Asus Slim SDRW-080 D2S-U Lite - only to get the above message (yes, using Verbatim CD-Rs). Strangely, also got the same message when trying to use my External Asus Slim Blu-Ray Writer. Even odder, I bought a new Asus Slim SDRW burner thinking that mu old one might be faulty in some way, only to be confronted by the same message. I also get the same sort of error message when trying to burn the CDs using Nero Burning ROM/Express. Now going completely bizarre, I am now getting the same error message on my old PC - after never having any problems. If I use different media (ie, Intenso 'high quality'), I do not get the above error message and it seems to burn the CD successfully. However, you always get digital glitching on the last few tracks. Infuriating and weird! Yes, I am suing the very latest version of Windows 10 64-bit on both PCs. Any ideas what the problem might be? DANNY New PC: Windows 10 Home (64-bit), Intel i5-9400F 6 Core ("Coffee Lake"), Asus Prime H310-Plus R2.0 (Intel LGA 1151 ATX motherboard) (Intel H310 chipset), Palit Nvidia GeForce RTX 3060 Ampere StormX OC 12GB, 16GB Corsair Vengeance LPX (RGB PRO DDR4 3200mhz), Asus STRIX SOAR PCIe 7.1 Surround (with DAC), Adata SX8200 Pro M.2 SSD 512GB (PCI-E NVMe), Seagate Barrucada SATA III 2TB, Asus PCE-AX3000 Wi-Fi + Bluetooth 5.0, Corsair CV650 80+ Bromze 650w PSU, GameMax White Diamond case, LG UltraGear 27GL850 GameMax Iceberg RGB Watercooler Old PC: Windows 10 Pro (64-bit), Intel Core2 Duo E8600 (3.4ghz), Abit IP-35 Pro (Rev. 2.00/BIOS v1.8 Beta) (Socket 775), PNY GTX 9700 XLR8 OC 4GB, 8GB Corsair PC2-6400 800mhz XMS (4 X 2), Samsung Evo 850 500GB SSD, Hitachi CCTV DVR 7200rpm 64MB 2TB, Corsair HX 620w PSU, Sharkoon T9 Value case, TP-Link Archer VR2008, LG UltraGear 27GL850

A decision about the future of this software has been made. stay tuned for news.

bump...let's update this great program!

it has been deleted now. your post will keep showing as guest. thanks.

Hello, I would like to request deletion of my forum account. The account is very old and I no longer use it. Thank you in advance, it is greatly appreciated.

Just acquired CDBurnerXP and the documentation shows a burning menu that includes Verify after burning but the app itself has no such feature. What happened? This is very important to me. Thanks, Jay

... and after 6 months...! Not one answer. Tragic.

Good info

When I try to burn a selection of tracks I get a message saying, None of the tracks could be added to the audio image. The disc cannot be burned.

Also wondering if it's possible to make windows "think" one of my USB drive's is a CD or DVD drive and then it would allow me to write to it (disc spanning) like that?

Hi. Wondering if anyone knows of a way I can do the following? I want to span a backup job onto several USB drives... (I have several 120GB USB hard drives). Is there a way to span a folder full of sub folders and files backup onto my spare hard drives? For example I have six or seven 120GB drives, but have a 2TB drive with one folder (with several sub folders on it) full of data I want to back up onto them. Is this possible? (Also I would like to be able to access the files on the smaller drives, so do not want them encrypting or zipping up or converting to any other backup format). * Operating System: Currently on Win7 or Win10). Software I'm currently using: www.AllwaySync.com I used to be able to do the above onto floppy discs using WinRar (But that would not enable me to read the backed up files on the new destination discs until they were all unpacked again). The closest I've gotten is CD burner XP that does exactly what I'm looking for, but only writes the data to CD's or DVDs. Thanks Gareth

Bucc69 has a promising work around. I don't understand why it works, but it does. The problem I experienced is when I drag and drop the tracks show in the order I have them in on my computer, but when the disk burns, the tracks are reordered. Bucc69 suggested taking one or more tracks out of order and then putting them back before hitting the burn button. It works!

Hello I am able to burn music tracks to a CD using CDBurnerXP. The CD plays using Windows Media Player. So far, so good, but when the last track has played, the sequence begins again from the first track, as if it's stuck in a kind of loop. Is that normal? I would prefer it so that when the last track has played, that's it. Is that possible, please? Thank you.

@skayflaya. +1 THIS WORKED.....I brought it down from x24 write speed to the lowest x10 and it didn't give me the error and stop half way. Only took me half my CD stack!

Bei mir liegt es an der Hardware. Mein LG BH10LS38 BR-Brenner, der an der SATA-Schnittstelle meines Windows 10-Rechners hängt, zeigt den Text ums Verrecken nicht an (egal mit welchem Programm (EAC, Feurio, WinAmp, etc)), obwohl er laut Hersteller und AIDA64-Auslese dazu in der Lage sein sollte. Das hat er auch schon so gemacht, als er noch an meinem alten Motherboard mit Windows 7 -> Windows 10 hing. Allerdings konnte ich auf dem alten Board noch meine alten LG DVD-Brenner per IDE anschließen, die den CD-Text ohne Murren ausgelesen haben. Das geht jetzt leider mit dem neuen Board (Asus Prime X470-Pro) nicht mehr, da auf diesem Board keine IDE-Schnittstellen mehr vorhanden sind. Also entweder lügt der Hersteller und AIDA64, oder es hat mit der SATA-Schnittstelle zu tun. Habe mir schon 'nen Wolf "gegoogelt" um da ein Workaround zu finden. Bisher allerdings ohne Erfolg. Es sieht beinahe danach aus, als wäre ich der Einzigste im WWW, der dieses Problem hat.

Have you stopped by making your program? :( You dropped a new version by 2019 .. Mvh: James Törnquist

When you're in the "Burn Disc" menu, to launch the burning of a media, and you scroll down the "Burn Speed" options and you choose "<Other speed...>" to choose "1x(4.500 KB/s)", the actual "burn speed" during the "burning process" is always something different, something random, and something much faster of course (like 6x, for instance).

The "Verification Process" after the burning should at least run UNTIL ALL FILES ARE ANALIZED, and there should be a report of the files which have not been burned correctly. I had to use an external program to find out which file had not been burned correctly, and that the issue wasn't CDBurnerXP nor the media, nor the burner, but the original file on the hard disk drive itself. A complete report of the verification process is a necessary tool, specially when you burn very large amounts of data (50Gb of data, for instance), you don't need the details but you need to know at least which files had discrepancies.

Oh, I see. Thanks for explaining. I will cut down on the number of tracks. Appreciate your reply.

I located sound tracks in my PC and changed the default column "Modified at" to "Created add". I wanted to sort the soundtracks accordingly, but The loaded sound tracks had incorrect time signature (exactly +2 hours off, maybe time zone or something ?) When I clicked the column to sort the sound tracks (ascending, so earlier created songs should be on top), they were sorted incorrectly, like this ... and so on. I would show a screenshot, but this site doesn't provide an option to upload images and the link to my image posted online doesn't work for some reason.

I've had the same problem. I did, however, already have the "Enable CD-Text" option selected, and some of the track information—including information as described in the original post here—is still missing. Track names, missing. Album art, also missing. Is there some other setting I've been missing somewhere?

I have burned a CD with only one song on it (it's for a demo). The original file is a .wav file. After using CDBurnerXP to burn to the CD, it is rendered as a .cda file. It appears to burn without error. However, when I attempt to play the CD on my computer's media player (foobar2000), I get this error message: Unable to open item for playback (Disc not available): "cdda://00023047,01" When examined in Windows File Explorer, the CD/DVD drive does recognize the file on the disk, apparently with the correct filename (Track01.cda). I have successfully burned many other CDs, and no other CD has failed to play back (yes, .cda files all). Windows 10. I thought at first that it must be a bad disc, but several more attempts all yielded the same results. Then I thought maybe it was because I was attempting to burn only one short file, so I added other copies of the file to the burn list. It made no difference, except to give me additional error messages, one for each file. Obviously, there must be something wrong with the file I am attempting to burn, but I'll be darned if I can figure out what it might be. Anybody out there have any ideas?