floele

In this case you probably have no burning device available at all. Depending where you are in the application, you would usually have a combo box with all devices available for selection.

The burning library changed quite a few years ago (don't remember when exactly) so if you had the issue before the change, then it is most likely fixed.

Actually, I have: https://github.com/canneverbe/Ketarin

Not sure how old you need. You can check this link for very old ones https://cdburnerxp.se/downloads/releases/4.5/ Or this one: https://download.cdburnerxp.se/

At this point there is not much I can add to the software because nowadays even the underlying burning libraries are nonger under development, so it's hard to make any progress in this regard. I will make bug fixes whenever possible, but I'm not aware of any reproducible isses right now.

What you are seeing is completely normal. In VLC, did you try Media --> Open Media from the menu?

CDA is what you should expect when burning audio discs, this is completely normal. These discs should play fine in actual audio CD players. You should also be able to play them on your computer. If it doesn't work, maybe your file association with CDA is wrong, you should try to open the audio disc from within the media player application to play the disc.

It should not take this long indeed. Hard to tell why it's happening for you though.

CDBurnerXP does not provide "ripping" functionality (there are better tools for this purpose) but you can drag and drop CDA files to new audio compilations to compile a new audio disc from multiple existing audio discs.

This might happen if file names get too long, UDF would be a better choice for this case. It's not the default setting though since there have been compatibility issues with UDF.

Maybe you are using a different file system than before (check Disc --> File system). CDBurnerXP hasn't changed how sizes are calculated for a very long time now.

In case of data discs (includes MP3 discs), you cannot change the order of tracks.

Will add these options to the menu in the next version!

Since MP3 discs are data discs and don't really have an order in the file system, it's hard to randomize them. You could prefix the file names with a random piece of text. A randomization option is only available for audio discs.

Sorry that it took way longer than intended, but at least it works. Thanks for the feedback

There is no Blu-Ray video disc support in CDBurnerXP.

You could open the audio compilation file (.axp, it's just an XML file) using an editor of your choice and search and replace the drive letter or file path in there.

You can still choose to burn a disc without pauses between tracks (there are more options for this now), which will internally use disc at once.

"Temporary Burn Folder" is a MS Windows thing. CDBurnerXP does not use this kind of directory name.

What kind of file? If it's audio data you can just add it to the audio compilation. If it's 90MB of compressed audio though (MP3) you will most likely have to split the track before because it's length is too high.

Just released a few days ago. Don't except any major changes though at the moment.

It should give you this message if a single file alone is larger than the disc capacity, since CDBXP won't split individual files.

A CDBurnerXP project file does not include any file sizes. You can use the command line to create a dir listing (https://www.howtogeek.com/98064/how-to-print-or-save-a-directory-listing-to-a-file/) or any other fancy tool if you have one.

Looks like an oversight in error handling on my side. In order to select the data for ISO image creation, you need to add them to the "disc" layout at the bottom (as you would do when burning a data disc).

CDBurnerXP does not split files, it only spreads them across discs (which has the advantage that you don't need any tools to put your data back together). This may lead to a large amount of unused space if you have very large files. If you send me a full list of files (just individual sizes) I can check if the algorithm does something unnecessarily stupid and can be optimised, but you will never get a perfect use of space.