Creating an Audio CD with mp3cd
I guess the title tells you too much. The reality is that I was given some MP3 files and wanted to put them on a normal audio CD so the non-geeks here could listen to them. Thus, consider this a geek to non-geek conversion article.
First I looked at the obvious candidates in the Multimedia menu and found nothing useful. So, I decided to fire up Adept and see if it had any interesting sounding programs with mp3 in their name or description. The winner was mp3cd that was described as a program to burn audio CDs from MP3, Ogg, ... files. Perfect. I added the sucker and typed in its name.
It gave me a list of options. -n, simulate but don't write, sounded like a good first step. Well, in spite of the fact that it wasn't going to write anything, it complained it could not open the CD device /dev/cdrecorder. So, I fed it the right device with -d /dev/scd0 which brings the whole command line up to
mp3cd -d /dev/scd0 *mp3
It actually seemed to start working, cleaning up (its words) and creating WAV files. But, it then blew up with the folloing messages:
Checking WAV format for track 01 ...
sox did not report channel count:
sox: SoX v14.0.0
sox soxio: Failed reading `01.wav': unknown file type `auto'
Clearly, it was time to think about what that message might really mean. I decided it meant some sox library was missing. Firing up Adept again and looking for sox, I found a bunch of files whose names started libsox. One option was an "all" file. Sold. I clicked and when it was done, gave mp3cd another try.
It worked perfectly. It created a CD and sticking it in the CD player worked fine. And, for me, the good news is that I can do this again without ever having to use a GUI.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide