The Linux-Based Recording Studio
I grew up using keyboards. Cold-war grey TRS-80s, green-screened Apple IIs, IBM clones, 8088s, 286s, PC-DOS, then Windows (missing the command line) and finally UNIX command lines. Later, the recording bug bit me and took me away from the command line and into studios. I still was a PC guy, but there never was a reason to bring a computer into the studio. Affordable hard drives and memory were too small for audio, sound cards were junk and processors were too slow.
Then, Linux came along. Sure, I had to wait for hard drives to get bigger and chip speeds to increase, but even after that, proprietary software still was way out of reach. So I upgraded my studio, learning a lot about Linux along the way. Here, I share a bit of what I did in my studio and explain how you might start a Linux-based studio. General information about Linux audio and recording is vast, so I refer you to further resources where appropriate (see the on-line Resources section).
Like anything, what you need to buy for your studio and how you set it up is determined by a few key decisions, especially when it comes to studio hardware. The hardware is easy as 3.1415. Anything that runs Linux can run Linux audio applications, but bear the following in mind:
Audio uses 5MB per track minute at CD quality (44.1KHz, 16 bit), meaning a three-minute song recorded in stereo takes up 30MB on the hard drive. Multitracking uses more than two tracks. A typical project of 24 tracks that is three-minutes long would use 360MB, not including captured audio being used.
Slight upgrades to things like RAM size and CD-ROM speed are nice if you have older equipment. A CD writer is your friend, too, as you might have guessed.
Some bad video cards introduce noise into the sound card.
Drivers in Linux are sometimes hard to come by, so read and ask around before buying hardware, especially sound cards.
Acquiring software is almost as easy. Latency needs to be low, so the kernel needs a bit of a tweak in the form of a low-latency patch. The hard drive needs to be tuned correctly too. This subject is more than I can cover here, but check out the Resources on the Web for other readings. Also, keep a dual-boot system with Microsoft Windows for troubleshooting. You may need to test hardware on another operating system to narrow a problem to a Linux driver, or you may have tasks, such as upgrading firmware, that need to be done on a Windows box.
Now that we've got the box, it's time to decide what studio hardware we need. I like to think of the signal flow for a given project, and that tells me what I need. Figure 1 shows the basic concept of where a signal goes in a recording project. Also take a look at Figures 2 and 3; 2 is a wiring scheme for a simple studio and 3 shows my studio's scheme. I begin with the lynchpin, which actually is a couple of rungs down on the signal chain.
The key to digital recording is analog-to-digital and digital-to-analog converters (ADCs and DACs). In other words, you need to get sound in to and out of your computer. In both directions, you have some decisions to make.
ADC must be done in order to record. This happens in the sound card, in a digital mixer or in a standalone ADC.
Getting sound out (DAC) consists of two parts, listening (or monitoring—more on that below) and mixing. When mixing, you might never convert back to analog. You might mix digitally inside or outside the computer, saving a mix as a .wav file or transferring digitally to a digital recorder. The thing to understand here is that at some point before you can hear it, a DAC must happen. If you've done everything digitally, make a CD and play it in your car, that's where the DAC has happened.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
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