I have a theory that every competent electric guitarist will, at some point in their careers, inevitably enter into an affair with the Telecaster.
Leo Fender’s prototypes were constructed in 1949 and the instrument was originally dubbed “the Broadcaster”. The name was changed in 1952 for the mass-produced model, but this was accompanied only by minor refinements to the design. It’s almost as if the archetypal electric guitar emerged fully-formed from the forehead of Zeus.
Arguably the World’s first electric guitar design, the Fender Telecaster has a clean, practical look and an honest simplicity that remains unchanged today: A solid body, bolt-on neck, with two single-coil pickups.
With a reputation for both a melodious twang and a raucous screech, the Telecaster is an unforgiving instrument – if you flub a phrase or miss a note, you can be sure your audience will notice. Despite these limitations, or strengths, the instrument has found devoted players in almost every genre of popular music, including Country, Blues, Rock and Jazz.
It’s also eminently hack-able – the affordability of the instrument and ability to hide numerous mistakes beneath its plastic scratch plate make it open to experimentation: Changing components, wiring, and even additional pickups.
Over the years, successful official variations on the basic design have been attempted by Fender, many of them very successful product lines in their own right, used by many talented musicians, and still available today: the T hinline, the Deluxe, the 1972 Custom. But you will always be able to find the original Standard Telecaster hanging on the rack in any reputable guitar store. It’s a living fossil of the stringed instrument lineage: the “tuatara” of electric guitars*.
And so, if every competent electric guitarist will eventually enter into an affair with the Telecaster, then it is time I gave in to fate.
Here’s mine. Meet ‘Tara:
Beautiful, and eminently hack-able.
* OK, I know that strictly speaking, the term “living fossil” applies to species with no close living relative species. And clearly, I’ve just documented that the Telecaster is anything but that. Well, guess what: The tuatara isn’t strictly a living fossil either. So ‘Tara it is.
I’ve spent about the last year re-working a track called “Listen” that I really and truly thought was finished and done with. It all started when two independent things happened: Firstly, I decided to purchase XLN’s Addictive Drums software and improve the quality of my percussion tracks. This worked really well on my first experiment (a “new” track called … well that’s not important right now). As is the norm, before I finished the track to my satisfaction , I got heartily sick of hearing it. This happens on every musical project, I should plan for it. The only solution is to take a break; and work on something different for a while, and then come back to it, aurally refreshed.
I’d been getting a good bass tone on the new track, but I needed some practice, so I decided to give my fingers a workout and attempt to play along to the bass line of Listen. Now, the bass in Listen was originally recorded with a Chapman Stick, which requires quite different fingering, so this was not an insignificant challenge.
After about the second run-through, I was beginning to notice that it was sounding good. I mean, really good. It was kicking the track up a notch, to the point where I was considering that perhaps Listen actually should have the Bass on it instead of the Stick. Then I noticed some places where the drums were a little glitchy, could be tightened up a bit, given a more natural feel… and I could use XLN Addictive Drums on it, because after all, they sounded so much better than the sound module I used on Listen…
6 months later, with completely new drums, new bass (including a new bass melody in one section), some alternate synths, and some additional vocals, I was guiltily pleased with the results. And then…
This one time, I was in the car, and I put in one of my CD’s and I heard the original mix, the one with the Stick, and I realized that it had something that the new version I’d been working on just wasn’t delivering. The new version was great, don’t misunderstand me, it was improved dramatically in many ways, but in the process something had been lost. Something I had to get back. What to do? It was apparent that – although the new bass line was great, and had triggered many other improvements – it really needed to be played on the Chapman Stick. Back to where the riff began, as it were.
Time to go back to the Stick, and practice. A lot. I gained fluidity and clarity but the tone wasn’t there. The Stick is a different instrument than a conventional bass guitar, even though they dominate the same frequency range (at least the way I use the Stick), and feeding it through the same signal chain that I used for a great bass sound didn’t work. I have no idea what I used for the original Stick recording (yes, I keep notes, but they are not exhaustive), and this time I was getting nothing but rubbish sounds via external hardware amp simulators (my two stand-bys are the Line6 POD 2.0 and the Johnson J-Station), and getting really depressed about it, but in desperation I pulled out the Native Instruments Guitar Rig 3 LE plug-in that came bundled with SONAR 7.
It was the first time I used it. I’m not a fan of CPU-hungry virtual amp emulators and the associated latency. But in GR3le I started getting interesting results very quickly. Things were looking up. So much so, that I took advantage of a time-limited deal for SONAR users, and upgraded.
All of which is a preamble to what I actually wanted to talk about: Getting the bass tone for Listen using Native Instruments Guitar Rig 4.
Because GR4 is a resource-hungry beast,and the Listen project is already pushing the limits of my studio computer, I created a new project and loaded up three pre-rendered stereo tracks for the drums, synths, and guitars. Then a new track for the Stick recording:
Here’s the sound with just the drums accompanying – it’s basically just the natural sound of the Stick through the K&K pre-amp along with a little compression from the FX bin:
Guitar Rig is a lot of fun, because you can drag and drop icons around and construct a virtual equipment rack that represents how the audio signal will be processed. I created a rack with a tube compressor and phaser along with the typical bass amplifier and cabinet:
Pretty good… but it is missing some nice, clear, top-end frequencies. With Guitar Rig, you can set up a split to process the signal via two independent processing paths, so I set up a second “jazz amp” with all the bass and mids rolled off to add some shimmer in:
Cakewalk SONAR and similar DAW applications allow you to use third party “plugins” such as effect processors or “soft” synthesizers. These plugins – usually VST or DXi format – take the form of DLL files (on Windows anyway), installed somewhere on your local file system. I use several commercial plugins, but there are also many free, high-quality offerings from many different vendors both professional and amateur, available for download from the Internet. After a while, your hard drive can be littered with DLL files in various locations. In my case, many of these I have downloaded, installed, evaluated, and rejected, but left around in case I ever want to try them on something else.
So when it comes to backing up your system, it would be nice to know which plugins you are actually using! Unfortunately, in SONAR at least, there is no convenient way to list the plugins in use in a project. I asked this question on the SONAR forum, and received a couple of helpful replies, but I am happy to report that I have found another way:
Run Process Explorer. You will see a list of all the applications and processes currently running.
Locate and high-light SONARPDR.exe in the list. (That’s Sonar Producer. I do not know what name Sonar Studio would have.)
Press Ctrl-L to toggle the display of the lower pane, then Ctrl-D to display DLL files(instead of file handles).
Right-click on the column headings and choose Select Columns… and enable the [x] Path checkbox.
At this point you might see something like this:
This shows all the DLL files that SONAR has referenced as it loaded the project. I’ve clicked on the Path column to sort the list by file location, to make it easier to see the plugins differentiated from the other support files that SONAR uses. At that resolution it is difficult to read the text, so here is a portion of the image at normal size:
Here we can see that the project I have loaded is using TruePianos, Vintage Channel 64, pretty much all of the Sonitus FX suite, and Arturia’s awesome CS-80V. Oh, and a free audio “chopper” effect I downloaded from somewhere on the Internet called Gate3.
Once I’ve noted these down, I can switch to Sonar and load a different project, then switch back to Process Exporer and refresh the list with the F5 key. I will see a different set of DLL files.
Interesting point: It seems that when you close and open a new project, not all the plugin DLLs will necessarily be closed. For example, when I switched to a project that used XLN Addictive Drums but did not use Arturia’s CS-80V, the AddictiveDrums.dll showed up in the list, but the CS80VDx.dll stayed visible (the CS80V.dll, however, did not remain in the list.). So if you want to be completely sure to see only those plugins used in the project, close SONAR and repeat the steps above for the next project.
This virtual instrument really kicked my drum tracks up a notch. There are other products out there that are comparable, but this one hit a nice price point for me. Recommended.
My article on replacing the internal memory backup battery on the Korg
M1 synthesizer has been translated into Italian and reposted on an
excellent site called NonSoloSynth:
Cloud Chamber is the first completed track of a suite of instrumentals, a side-project which I have tentatively dubbed “Maxwell Tangent’s Divergent Thinking”. Musically it’s ambient, techno, loop-based instrumental music with plenty of guitars and processed natural sounds. But it’s early days, it could end up going in a different direction. I hope to have each track segue seamlessly into the next one in order to make one long piece of music. So far the tracks are being written in reverse order, because Cloud Chamber is the final movement.
I was working on this track on the later half of 2001, and therefore I’ve dedicated it to the victims of the World Trade Center attack in September 2001.
Melodic progressive rock songs and instrumental interludes, a touch of 70’s influence but a product of the dystopian Now.
“Very smooth, hi-tech sounding delivery…” – Chris Jemmett, alt.music.yes
“This guy is awesome.” – Dazed, on the Carvin Forum.
“..on a rare occasion you just have to conclude that the prog world should be feasting upon the birth of a new and promising act. That’s exactly the case with this [first] album.”
– Theo Verstrael, DPRP.net
“I find this new album attractive, [..] slightly less appealing than the 2014 debut. But as that is often the case with great artists, let it not distract you from trying this fine album. Especially those that are interested in bands that play varied, cleverly made, well played and sung [..], this might just be your cup of tea.”
– Theo Verstrael, DPRP.net
Recent Comments