GSP-2101 FAQ: Tips/Tricks - Friday Tips

 
GSP-2101 FAQ: Table of Contents GSP-2101 FAQ: General FAQ (Architecture, Analog, Digital, interconnect, etc.) GSP-2101 FAQ: Hardware/Software Version Differences GSP-2101 FAQ: Footcontroller usage, especially programmability of footswitch functions in the 2101. GSP-2101 FAQ: Tips and Tricks from other users.
GSP-2101 FAQ: MIDI Data Transfer GSP-2101 FAQ: Preamp tubes facts and user experiences. GSP-2101 FAQ: Library of 2101 programs. GSP-2101 FAQ: Technical Issues related to the 2101. GSP-2101 FAQ: Info on joining/leaving the 2101 eMail group.
GSP-2101 FAQ 3.0, Section 3a: Friday Tips
 

Friday Tips Introduction:


Index of Friday Tips:


Acoustic Tip (Phase Inversion to reduce feedback):


Cabinet Tip 1:


Chorus Tip 1:


EQ Tip1:


C-1 Tip 1:


C-1 Tip 2:


C-1 Tip 3:


Flanger Tip:


Master Volume Tip:


Miscellaneous Tip:


Modulated Delay Architecture:


Phantom Power Tip (XLRs):


Programming Tip 1:


Steve Morse Tip:


Studio Tip 1:


Creating Patches:

"Here is a question for Randy:

How do you write your patches? This is a creative question--not a "how-do-I" question. Do you start with an idea and then start plugging stuff together? Do you write the patches with your guitar strapped on or do you program it all in and then grab the guitar? How do you have your programming area set up? "

First off, understand that I am a studio rat...through and through. So my patches are usually tweaked on the fly, beginning with a sound that already exists in the box (why? because I am very familiar with the existing Programs and know which one to use to start). I usually run my 2101 through the console and when I am finished with whatever I am recording, I may save the sound, but I don't care because I will end up tweaking a different sound later.

I *rarely* write user algorithms for the guitar. Everything I need is usually present and acounted for in an existing Algorithm. For something whacky, I might build an alg, or modify an existing one. I am a schooled studio engineer (whatever that means) and so I do all my algoithm building on a white board in my studio. I jot the modules down on the board with their routings...I can then *see* if it works...I don't have to hear it...I don't believe this to be normal per se, it is just how I do it...

Once I have the pieces in front of me (from an existing Alg or a new one), I start by stripping everything away. I think I lean this way because of my mixing experience. I want to tweak in each effect by itself, because I already know in my head what each peice of the sound should do to create the complete sound. With enough practice, you start using the proper amounts (usually alot less than you think) to get what your after without tons of tweaking.

One thing that I am able to do is hear a guitar sound on an album and pretty much know the effects I am hearing. Once again this is from my many years of mixing...but something that anyone who is serious about effects should practice.

>>What is the most effective physical set up for your design team?

We have a studio (OK its a room with tons of studio stuff in it!) has a nice console and monitors. We also have a couple of Marshal 4x12s, a couple small Boogie cabs, a couple large Rivera cabs, several sets of PA speakers, a Music Man combo and a Fender combo...etc...

We listen to stuff through all the rigs but usually pick one rig to help get some resemblance of consistancy. That rig usually includes the 4x12 cabs...

For Program composition, we usually come up with categories of sound that we want and how many will be included in that category. This is why we don't have extra Programs laying around...we have been doing this for so long that we do very little wheel spinning.

Does that answer the question? Or just add to the confusion? :-)


Ducker Tip:


Parametric EQ Tip:


Go to GSP-2101 FAQ Table of Contents  Go Back to CLPastor's Home Page

Written by Curtis LeMay Pastor,
CLPastor@aol.com or clpastor@ee.tamu.edu
Last revised as of Feb 3, 1997.