Setting up a Multitrack Audio Recording Studio
Ever since Elvis plopped down his nickel and crooned a song captured in glistening black vinyl, children everywhere have dreamed of making the next hit single. Unfortunately, doing so usually costs more than the paltry sum The King laid out for his tracks. Today, anyone with a PC can be the next George Martin or Trent Reznor, making the next big hit to be traded illegally, right in their own bedroom! Linux's capabilities make it perfect for multimedia production, and as distributions become easier to install and set up, more ordinary users will want to do more multimedia projects.
To begin, start with your favorite Linux distribution, it doesn't matter which one. I choose Slackware. For this article I will assume you have the sound working and X running on x86 architecture. I'll also assume you know how to navigate Linux and install programs, although you don't have to be a guru. Because this article is targeted toward users who want to make good recordings, there will be less emphasis on the technical aspects of using Linux and more on recording theory and practices, including program-specific HOWTOs.
The two programs I discuss are Gmurf and Broadcast 2000, the latter of which had a nice introductory article in the January 2001 issue of Linux Journal. Neither program requires root privileges to install or run, and both are easy to install and run (just follow the documentation), so I won't cover that here.
The only other things you'll need aren't computer-related at all and consist of noise-making items (such as your voice or a pan and spoon), studio gear (such as a 48-channel powered mixing board with DSP or a Wah-Wah pedal) and a mic or three.
Once you have everything you think you need (trust me, you'll want more stuff once you get going), the next step is to record. Multitrack recording is essential for getting the best possible sound out of more than one instrument, and it is necessary if you are the only one playing the instruments.
Multitrack recording, in its simplest form, is simply multiple single tracks recorded and played in synch, so that the resulting music sounds like one composition. An audio CD is a multitrack recording consisting of two tracks that are played through a machine that sends one track to the left speaker and one to the right.
Music studios traditionally have tape machines that can record up to 64 tracks, and multiple machines can be synched to make an unlimited amount of tracks available. Then each track can have effects added to it and be mixed down to a regular stereo recording for placement on a CD, cassette or web site. With Linux, you can have an all-digital studio, with the number of tracks limited only by the space on your hard drive.
The two basic formats that we'll be working with are .wav and Broadcast's hypertext audio language (HTAL). Gmurf and Broadcast 2000 both work with .wav files; while Gmurf will actually let you edit and manipulate the bits of data that make up a sound file, Broadcast 2000 works only with pointers to various parts of sound files. The result is a small project file, one that leaves no fear of accidentally chopping the middle out of that killer take, and one that makes it incredibly easy to add "just one more" track.
The two quickest and cleanest ways of getting audio onto your computer are to rip from a pre-existing CD or download samples from the Web. The first method has the advantage of offering an enormous selection of samples to choose from, acquired simply and easily with countless CD-ripping utilities for Linux. However, current law limits the duration of samples you are legally allowed to use, and you'll need to be creative in finding even small samples that would be appropriate to use in an original composition. The second method has the advantage of being an easy way to get usable instrument sounds presampled. This is a great thing if you are looking for a unique instrument or any instrument to which you do not have access. I use downloaded samples to create drum tracks for lack of a real drum machine or drum kit.
The major disadvantage to using prerecorded sounds is that you will need some kind of sequencer to get maximum benefit and flexibility from the samples. For example, it is easy to arrange drum samples in Broadcast 2000 to create a great-sounding beat, but there is no easy way to add swing to the track to make a really funky groove, aside from tweaking it by trial and error.
Making a live recording using a microphone through your sound card will give your opus the "you are there" energy that can make a good tune rock. Synthesized noises are okay for backgrounds, but if you want your creation to turn out sounding more like a person played it and less like a midi-enabled web site, you'll have to break out some real recording tools.
Some programs will allow you to make a stereo recording on your hard drive, using the input jacks on your sound card. Broadcast 2000 is no exception, and shortly I'll discuss exactly how to record that screaming guitar solo quicker than you can say "real recording studio".
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