At the Sounding Edge: FreeWheeling
A few years ago, one of my students performed a rather unique original piece at a local coffee house. He used one guitar, one bass, his voice and a foot-controlled hardware device called a loop sampler. The sampler recorded brief segments played on the guitar or bass and then fed them back out as repeating audio loops. The sonic result was a texture of seven looping guitar parts and two looping bass parts. When the texture was built to his liking, he then added his vocal, singing a non-looped song over the looping sounds. At the climax of the song, he simply stopped the sampler on an appropriate beat, and the crowd went wild.
JP Mercury's FreeWheeling program is the software equivalent of that loop sampler. Of course, features have been added that are possible only in software, making FreeWheeling a powerful loop-based performance tool. In this month's column, I take a look at the latest version of FreeWheeling and consider its basic capabilities. FreeWheeling has features I haven't explored yet, but even its basic use shows off FreeWheeling's musicality.
An audio loop is a sound or part of a sound that is played repeatedly until stopped by an internal or external control. In musical terms, a loop is a kind of ostinato, a repeating figure that may function alone or in combination with other ostinati. Stravinsky's "Rite Of Spring" includes excellent examples of layered ostinati. Layering audio loops can enable quick construction of complex musical textures in the studio or in live performance.
The tape loop echo boxes of Ye Olde Days were the original audio looping devices, but the modern audio looper truly begins with the hardware samplers and drum machines of the 1980s. These machines offer looping capabilities that have been put to creative use by musicians in various genres, including hip-hop, rap and techno. As sampling shifted to software running on general-purpose computers, a genre of powerful music composition software evolved from the basic hardware implementations. Programs such as Fruity Loops and Sonic Foundry's Acid are excellent examples of audio loop sequencers, adding enhancements such as timed loops and high-quality time stretching and pitch shifting.
I'm often asked whether Linux audio software includes anything similar to Acid. I freely confess that Linux audio development has yet to come up with an Acid competitor, although Ardour might be warped into service. However, Linux-based musicians do have access to some impressive loop-based music software, and so we come at last to FreeWheeling.
I built and tested FreeWheeling 0.5pre4 on Red Hat 9 and Fedora Core 3 installed from the Planet CCRMA ISO CD images (see Resources). Compiling the program was a straightforward task, with only two special considerations. The excellent SDL (Simple DirectMedia Layer) libraries and headers are required for FreeWheeling's GUI, including the SDL_gfx and SDL_ttf components for graphics and TrueType font support. The second consideration was the option to provide internal support for the FluidSynth soundfont synthesizer, allowing direct play and record with FreeWheeling.
My Planet CCRMA installations already supplied the main SDL and FluidSynth systems. However, during the configuration process, I discovered that the Planet had not installed the SDL_gfx and SDL_ttf devel packages. After installing those packages, FreeWheeling compiled and installed without complaint.
To fully configure FreeWheeling to your personal tastes, you need to learn the details of its .fweelin.rc file. By default this file is installed in your home directory and in /usr/local/share/fweelin. The file in your home directory has preference, and it's there that you customize FreeWheeling. We look closer at .fweelin.rc later, but for now let's get started with the program set to its defaults.
FreeWheeling is a JACK-aware application, so you need to start the JACK audio server before opening FreeWheeling. After starting JACK, open an xterm, type fweelin at the prompt, and gaze in awe as your screen fills with messages as FreeWheeling starts up. Figure 1 shows part of that message stream, along with my JACK audio connections and the FreeWheeling default display. FreeWheeling does not autoconnect to any other JACK client, so you need to make your connections with jack_connect or a GUI such as Rui Capela's QJackCtl. Of course, thanks to JACK, you can route FreeWheeling's audio I/O to and from any other JACK client, for example, attaching the audio output from an external softsynth to FreeWheeling's audio inputs. FreeWheeling is also an ALSA sequencer client, which means it can send and receive MIDI messages to and from any other ALSA sequencer client, such as that external softsynth.
Press the / key to call up FreeWheeling's help screen that lists the current key bindings and control commands. FreeWheeling is essentially a keyboard-controlled audio loop sequencer, designed for maximum personalization through the .fweelin.rc file. Again, I must delay further explanation of that by-now mysterious document in order to proceed to the hands-on operation of the program.
Similis sum folio de quo ludunt venti.
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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