Help burning CDs?
Help burning CDs?
I'm having an issue trying to burn a music CD for use in my (very old, I know I know) car. I'm running FedoraKDE (40) and Brasero, a Liteon brand external optical DVDRW drive, CD-R (TDK brand), and a Framework 16.
The issue I'm having seems to be that the blank disks(maybe?) aren't recognized automatically by Fedora, when I pop a full commercially released CD in it'll play/rip, but with a blank disk nothing happens, and I don't know where to "save" the "image" of this album I'm creating in Brasero to get it on the disk.
Someone on a random linux forum told some other guy to run cdrecord -checkdrive which says my drive is at /dev/sr0 with a blank disk, but that's as far as I've gotten. Do I choose sr0 as the place to save it? It says "something something overwrite" when I try which makes me wary, it seems it wants to overwrite "sr0" itself and either bork my drive or install, but maybe?
I'm positive it's just something simple I'm missing, any help would be greatly appreciated and I can answer questions and run commands if needed (but I don't actually have WIFI rn, so I'll have to have the package for said command already.)
Thanks in advance.
The way I do it is I rip the cd I have to FLAC or MP3, then I mix the songs I want and burn it to a “music CD”. You do not want to make a data cd as computers usually try to burn by default.
I can rip em no problem. I "ripped" this one and am totally "just making a backup." Where I got 14 audio files is of little consequence, I would like to put those audio files on a blank disk which I have purchased.
The problem is I do not know how to get the files from brasero to the disk. They're all in brasero, the only options I have are "name" (we'll call it Keasby Nights), and a dropdown menu with "image file" as the only option, and a button labeled "burn." So naturally, you click "burn" right? Ok, well now it pops up with a file picker on /home/. What now?
I did a bit of googling and it seems like "Brasero" had widespread popularity. I found this:https://documentation.suse.com/sles/12-SP5/html/SLES-all/cha-gnome-burn.html, but can't test it because I haven't had a disk drive in at least a decade. Since this is forum meant for noobs, please let me know if you need guidance on how to install Brasero and I would be happy to help. From there, it has a GUI and should be quite familiar to anyone who used Winamp, itunes, or windows media player back in the day.
Thank you for your assistance. The issue isn't "how to install brasero" however.
As per the documentation, it says
1. Select Project › New Project › New Audio Project. 2. Drag and drop the individual audio tracks to the project directory. The audio data must be in WAV or Ogg Vorbis format. Determine the sequence of the tracks by moving them up or down in the project directory. 3. Click Burn. A dialog opens. 4. Specify a drive to write to. 5. Click Properties to adjust burning speed and other preferences. When burning audio CDs, choose a lower burning speed to reduce the risk of burn errors. 6. Click Burn.My issue is during
4.The dialog pops up just as you'd expect. Where do I choose to save the file? It defaults to being open on /home/, however I think if I save it there, the files will not be on my disk, they'll be in my home dir. Where is the disk?Aha! I understand now. So, on Linux, everything is a file. Even Disk Drives, CDs, flash drives, etc. I think this may be the root of your confusion. Instead of new drive D:// popping up somewhat parallel to your C:// file system (as it would in Windows), it shows up inside your existing file system.
You were on the right path before. The cdrecord command you ran seems to have correctly told you the location of the CD in your file system (/dev/sr0) . I imagine this changes with distro and hardware, but I'm not sure because my CD burning days predate my Linux days. If you want to make sure that this is indeed the correct place to save the file, then run the command again with the CD removed. If it disappears, then you've got it.
The closest thing I've done is install raspberry OS to a flash drive, which often shows up as /dev/sd0, so it seems like you were very much on the right track. The /dev folder means "device", so most hardware peripherals will have some kind of presence here.
Maybe try k3b, a CD burning program by the KDE project instead. It always worked well for me.
yeah, burning and saving is probably not the same. /dev/sr0 is just a so called device node. it is a special file with two numbers that are an interface to control the drive. if this file gets borked (eg. replaced by a disk image) you can recreate it using the numbers with mknod, or likely udev or something will recreate it at boot when all the hardware is detected, which triggers events to create them.
i remember vaguely there used to be links to the proper device nodes being created, usually called /dev/cdrw or /dev/cdrom maybe check for those, preferably rw and maybe yours is dvdrw or so.
good luck
I do see what appears to be a /dev/cdrom, but if I click it, it says "a file named cdrom already exists. Do you want to replace it? The file already exists in dev. Replacing it will overwrite it's contents." Just like it says with /dev/sr0. That can't be right. It's trying to save the image of this audio cd as "cdrom" under /dev/. Am I supposed to do /dev/cdrom/keasbynights or something?
no. no. that's correct. Linux is warning you that you're about to burn to the disk which will overwrite any files that are there (rewritable CD Roms are a thing and Linux doesn't necessarily know what kind it is). It's just warning you that in either case, you're writing to the disk.
It's also no uncommon to have two locations. for example, on my Ubuntu install, I have several /dev/sdX (replace X with a sequential number). One for each physical disc. Those also show up in a folder called /mnt/media but I'm not 100% why. There's probably some subtle difference that exists for security reasons that's documented.... somewhere.
You really should try k3b. Brasero was always kind of a joke by comparison in my experience. For example, k3b easily let's you run diagnostics on your dependencies, so you can check that they are present and correct.