I’ve got a script on the list named simpleburner, that appears to work for command-line CD burning.
It does seem to make the task of working with cdrkit a little bit easier. It has flags for both ISOs and data CDs, although I don’t see an option for digital-audio-to-audio-CD.
Some issues though:
- The dates in the repo suggest it’s a few years beyond attention.
- The script comes as a pair, in perl and python versions. The python version wouldn’t work for me.
- The perl version seems to work, but also seems to ignore all the flags given to it … which, as you might imagine, makes things a little difficult.
- Technically it’s possible to hard-code the name of an ISO and other criteria into the script, but that seems to defeat the purpose.
Aside from that, it spun up my /dev/sr0 with no issue, wodim was happy to play along, and things seemed to be moving in the right direction. Even if it was trying to delete a mysterious ISO that didn’t exist, and so forth.
I only see simpleburner in AUR; I don’t think this ever passed muster for Debian.
I hold no ill will toward simpleburner; I suspect it’s just fallen out of step with its underlying software. If you need a command line CD burner, I think I would recommend any of a few others before this though. 😕
Back in September, when I was wading through the B section, I stepped across bashburn. Here’s its derivative, mybashburn.
To read the home page for mybashburn, it sounds very much like a viable offshoot of the original project, and I can see some similarities here and there.
As for which holds the higher ground, I don’t have an answer. I’m still sitting in that loop I mentioned earlier, where I only rarely need to burn a CD (and oddly, it’s usually to test something for this site 😕 ).
So if you prefer one or the other, that is your decision.
mybashburn is not in Debian (bashburn is, and both are in Arch/AUR), which surprises me in a way. I could swear this was one of the earliest console-only CD writers I ran across, years ago, when I was using Ubuntu.
This is another program where I feel obligated to mention that the last update was nearly six years ago. Ordinarily that’s not an issue, but for CD support software and access protocol, I have a fear that it might be.
Now go forth, and etch tiny lines in lacquer-coated circles of polycarbonate. 😉
I’m going to include mp3cd here today, even though I was a little less than successful with it.
You can look through those error messages, and see if you spot the issue. For my own part, I think this might be out of date with the perl substructure. But I am no perl wizard. Perhaps you are. 😉
I will mention that while there were spaces in the filenames for the music, I had a completely different set of errors. So I consider this an improvement, even though I don’t think this is what should have happened.
And what should have happened? If I understand the home page right, I think this should read an m3u file and send it straight to CD. Sort of a one-shot straight-to-disc tool.
But as you can see, it fell short. If you have any clues, let me know. I have a feeling this is probably workable, but might need some surgery first.
I always like finding a good, well designed console application.
Not out of any sense of spite, but because it reinforces something I decided a very long time ago: that in many cases, console or even CLI applications can do just as much, and just as well, as graphical counterparts.
cdw is like that. Here’s something that looks and behaves just as a graphical application might.
Configuration, CD composition, status and disc info … everything is right up front and easy to navigate.
Lots of colors too. I like colors.
I like this arrangement over something like bashburn too. I acknowledge that bashburn works (I just used it the other day, as a matter of fact), but the menu arrangement and configuration are sometimes obtuse for me.
No matter. cdw and bashburn are both choices, and that’s what this is all about: choice. 😉
It’s been a very long time since I used bashburn.
There are two reasons for that. First, because my initial work with bashburn was less than successful. That was about seven years ago though, so that criticism doesn’t really hold much water now.
The other reason is my slow and eventual drift away from CDs. That’s not a personal transformation, just a tendency to rely more and more on USB drives over optical media.
Where I used to burn CDs as backups, I now just use leftover hard drives and drive enclosures. And where I used to burn CDs to install distros, I now just inject ISOs onto flash drives with unetbootin.
Now, to add insult to injury, I don’t even have an optical drive on this machine. I could buy one I suppose, but I rarely use CDs any more.
And so we come full circle.
Regardless, bashburn is one of a handful of CD/DVD writing options at the console. For some reason, it seems the majority of burning tools come in graphical form.
Of course, as you probably know, 99 percent of those GUIs are just sending instructions to the command line. But we’ve probably talked about that before. …
If this works for you, leave a note. I’d be curious to get your impression of it.