Tag Archives: RedWirez

GuitArchitecture, Sonic Visualization And A Pentatonic Approach For The Holidays

Posted on by
3

Happy Holidays!

.

I know I’ve been posting a lot of gear related items lately – and  based on the statistics for site visits – this seems to be what people are primarily interested in – so this has driven the posting content recently.

While I’m happy to blog about gear (not incidentally, my 8 string Bare Knuckle Cold Sweat pickup came in last night and I squealed like Bobby Hill); I don’t want to get too far away from playing.  With that in mind I’m putting a concentrated effort to get more lesson/performance posts up to rebalance the site a bit.

I’ll have a new  chord-scale lesson up next week but in the meantime wanted to explain my performance/pedagogical approach to navigating the fingerboard with a fleet fingered pentatonic lick (yes, it’s reposted – but just like Thanksgiving leftovers – aren’t they still good on day two?).

.

GuitArchitecture?  Sonic Visualization?

.

I wanted to take a moment and talk a little about GuitArchitecture, sonic visualization and re-examine a chestnut from the lesson page as a little – three for the price of one post.

In broad strokes, the GuitArchitecture concept is that the nature of the guitar’s fretboard and tuning lends itself to visualizing fingering patterns.

While patterns performed mindlessly can be a bad thing, they allow people to realize ideas more readily.

Through these patterns, musical structures can be realized and worked into larger sonic arrangements.  More importantly, patterns can be associated with sounds and visualizing how to realize a sound by seeing its shape on the fretboard makes performing it easier.  Hence the term Sonic Visualization.

In my forthcoming books – I have a lot of information on this topic as it applies to scales.  When approaching scales – I see them as a series of modular two-string patterns that connect the entire fingerboard.

.

The GuitArchitecture Approach

. 

Here’s an applied example of sonic visualization:

Let’s say I’m playing a solo over an E minor chord.  As mentioned in a previous post – when soloing over a minor chord you can substitute a minor chord a 5th away (in this case B minor).

So if I’m thinking of using E pentatonic minor over the chord (E, G, A, B, D) I can also use B pentatonic minor (B, D, E, F#, A).

If you look carefully – you’ll see the only difference between the two is the F# and the G.   Both notes sound good against E minor, so if we combine them we get a six- note scale (E, F#, G, A, B, D).  Here is a sample fingering of the combined scales in the 12th position.

.

If that scale were fingered as a 2-string scale instead of a six- string box pattern – the same fingering pattern can be moved in octaves – thus eliminating the need for multiple fingerings. (This is the same approach I’m using on 8 string guitar btw).

Here is an mp3 (note mp3s are a little glitchy in Safari – if it doesn’t play you may just have to reload the page) and notation/tab for the descending scale:

.

Sextuplet descending

.

.

* Fingering Note: I finger both patterns with the 1, 2 and 4 fret hand fingers on both string sets.

* Descending Picking Note: I play this with a modified sweep picking pattern

E string: up-down-up

B string: up-down-up

.

The picking pattern is the same for each string – but when I switch strings – it’s two up picks in a row.

Here it is  ascending:

Sextuplet Ascending

.

* Ascending Picking Note: I also play this with a modified sweep picking pattern

.

E string: down-up-down

A string: down-up-down

.

The picking pattern is the same for each string – but when I switch strings – its two down picks in a row.

If you’re used to alternate picking  – you can use that approach as well but I try to apply the same picking pattern to all three-note per string patterns.

.

Practicing the pattern

.

In addition to focusing on the timing of the notes – it’s very important to practice slowly and only increase speed when both the timing (are all the notes being played with rhythmic equivalence?), tone (i.e. can you hear all of the notes clearly?) and hand tension (is your hand should be as relaxed as possible?) are all working together.

I’ve written a whole series of posts on practicing  (Post 1, post 2, post 3, post 4, post 5, post 6 and post 7) that I’d recommend checking out if you haven’t already done so – but the simple principle here is to pay attention to what I call the 3 T’s in Performance: Timing, Tone Production and Tension.

This particular approach is challenging – particularly if you’re not used to the stretch.  Just remember to practice in small focused increments and try to increase steadily over time.

.

The Tones:

.

For those of you who are interested, tone on this recording was the same AU Lab/Apogee/FNH combination that I detailed here:

Here’s a screen shot of the Pod Farm setting (The tone can be downloaded from line 6 here):

.

That’s all for now

.

I hope this helps!  You’re free to download and distribute any of the lessons here but I maintain the copyright on the material.

I’m always looking for feedback on what people find useful and what they don’t so if you have any questions or comments, please feel free to e-mail me at guitar.blueprint@gmail.com

AU Lab/POD Farm 2.0/Live Laptop Rig Tutorial Part 2

Posted on by
Reply

In the previous post, an AU Lab session (or document) was established and an A/B POD Farm patch was created.  In this post, I’m going to start modifying the patch to make it more useable.

Building the rig:

Okay first I’m going to swap out the amp. I like the Double Verb instead.

You can drag and drop amps into the signal chain, but if I click on the down arrow to the right of the AMP field – I can just scroll down to the Double Verb amp.

Here are the settings I’m using.

If you look in the left hand corner underneath the input knob on POD Farm, you’ll notice the global gate is on.  I tend to use the global gate at a low setting.  This came from a ruined session where I switched to a distorted sound that DIDN’T have a gate on it and squealed between each phrase.  Now I keep the master gate on to not worry about that scenario.

Compression:

Louder isn’t always better.

Compression has it’s place – but I try to play dynamically, so the compression is the first thing to leave the POD farm signal chain.

If you click on the compressor in the signal chain and then ctrl-click on the compressor you’ll get the following options.

Just select Delete.  If you change your mind you can drag and drop another compressor from the menu into the signal chain.

Another point to bring up, is that when I use an amp and effects – I try to use the same signal chain for all of them.  (This comes from years of playing gigs and having a bunch of effects pedals going through the same amp and reverb).

Looking at this set up, the mic pre (currently between the amp and the reverb) would be something that I would want in the channel signal chain in AU LAB instead of POD Farm – so that it was the same mic pre for any amp I’m using.

The first step is to delete the mic-pre from the POD Farm signal chain (using the same method as the compressor above).

Next (in AU LAB) in the Audio 1 channel – click on the arrow in the next available Effects field below PODfarm .

If you scroll down to Line 6, you’ll see that in addition to PODFarm, that each individual component of a PODfarm rig has been broken down into components (aka POD Elements).  This is so you can use individual effects or amps as an AU plug in which much less of a CPU hit than loading in another instance of POD Farm.

In this case choose: POD Farm Element – Preamp.  I’ve chosen Vintage UK.

Reverb:

The reverb would also be something that I would want in the channel signal chain – so that it was the same reverb for any amp I’m using.  (The other advantage is that by placing the reverb outside of POD Farm, when I change amp settings the reverb doesn’t cut off with the amp change.)

Delete the Reverb from the signal chain in POD Farm (using the same method as the compressor and the mic-pre above).

Next, (in AU LAB) in the Audio 1 channel – click on the arrow in the next available Effects field below POD Farm Element – Preamp.

If you scroll down to Line 6, choose: POD Farm Elements – Reverbs.  I’ve chosen Standard Spring.  Here are the settings I’m using.

Impulse Responses:

I use impulse responses rather than the speaker sims in Pod farm.  So the next thing I’m going to do is get rid of the speaker cabinet/microphone on Podfarm.  If I click on the CAB button – I’ll get a list of speaker cabinets and microphones used.  If I scroll to the top of the list – I’ll get “No Cabinet” which deactivates both the cabinet and the microphone.

Next, (in AU LAB) in the Audio 1 channel – click on the arrow in the next available Effects field belowPOD Farm Element – Reverbs.

Scroll down to Lernvall Audio and select LA Convolver.

Now I’m going to select to impulse responses to act as a speaker simulator.  I’ve experimented with putting multiple instances of LAConvolver  on buses and running multiple cabs, but since I want to run SooperLooper in the bus (Where I can loop guitar and any other incoming audio source), I’m going to just stick with a stereo set.

Select a channel and hit “choose” under file. In this case I’m using the free RedWirez cabinet I got as part of their birthday giveaway.

I want to use a high sample rate to get better definition so I’ve chosen 88.2 K. (or 2 times 44.1k)

I’ve chosen an SM57 on the grill and a KM84 about 3 inches behind the back of the amp.  I tend to start with the Wet gain in the center position and adjust as necessary.

A brief note:

I’ve mentioned this in other posts, but since I want to use the same speaker cab for all the amplifiers, I’m going with a 4×12 for familiarity.  Normally,  I wouldn’t match a double verb up with a 4×12, but since I’m going to be running a Marshall on the other channel, I’m going to just have to adjust the clean amp signals accordingly.

Fixing the Sample Rate:

If you notice, the plug in sample rate and the Impulse response sample rates are different.  It will work like this – but I want to use the highest sample rate I can for the most clarity.  There is a delicate balancing act that comes between high sample rates, stability and useable latency, so everything here is a compromise.

I’ll fix this with Audio Midi Set up :

First: click on AU Lab and look under Preferences.

When the preferences window opens, click on the tab marked Devices.

If you click on the expert setting arrow you’ll see something like the following:

Another  brief note:

I’ve set the CPU to 100% to avoid glitches.  I’ve also set the latency really high to attempt to keep the system stable.  Depending on the system and interface that you’re using, you’ll probably have to lower the setting to the point that you get glitching (or max out the memory) and then bring it up a little bit from there.  With the headphone out of the Duet – even with these settings the latency is suprisingly tolerable.

If I click Edit Device – that opens up the Audio-Midi Setup application (or you could find it in the Application – –  > Utilities folder)

Note:  I’ve changed the output format to 88.2.

Going back to the Audio-midi sample rate window – it shows:

An Important note about sample rates:

I’ll mention this again – but if you’re going to be incorporating other audio into the session (including looping in SooperLooper) – you’re probably going to have to set the sample rate back to 44.1 (and set the Impulse responses back to 44.1).  If I’m not looping –  I try to set the rate as high as I can, but know that it’s going to have to get bounced down to 44.1 for recording, etc.

While I’m on the preferences Tab I might as well set up recording to the external drive.  Click on the tab marked “Recording”.

Now if I click on the “Rec” button at the bottom of OUTPUT 1 in AU LAB, it will record whatever I do to the Lacie as the default location, in a 24 Bit AIFF format.

With the changes in this part of the tutorial, the AU Lab Input looks like this with some sample input:

You’ll notice that the output is a little off balance.

If you pan it to the left you’ll balance the signal out a little more. Here’s the setting with all the global FX so far.

You may want to save the AU LAB session now, if you haven’t done so already.

In the next session, I’m going to complete the clean channel effects and automate some parameters with the Midi Learn function to be able to make changes to the sounds with the Line 6 Shortboard.

You can find all of the laptop guitar rig posts on the Blueprints tab on the top of the page.  Once on the blueprints page – just scroll down to the Laptop Guitar Rig section.

Thanks for reading!

AU Lab/POD Farm 2.0/Live Laptop Rig Tutorial part 1

Posted on by
Reply

I’ve received a couple of pm’s regarding AU lab and setting it up for live use (largely from this post).  With an upcoming film accompaniment and a need to re-tool the setup a little I thought I would build a rig from scratch and explain how I’m doing everything.

About this tutorial:

What I am doing here is documenting the specific process for building a working rig for myself.  If you don’t have this specific hardware/software set up, you could adapt the process to whatever you’re using.

AU LAB

First a bit about AU Lab.  If you have a Mac Laptop with an OSX operating system, you have access to one of the greatest FREE music applications imaginable.  AU Lab is a program that was designed for AU (Audio Unit – The Mac proprietary plug in standard – much in concept like a VST) developers to test plug ins – but since it can accept audio and midi, has buses and can record audio – this makes it a great tool.  The fact that it does it with a fraction of the CPU of something like Logic makes it essential.

AU Lab can be installed as part of the SDK package that is on your OSX install discs.  If for whatever reason you can’t find your discs – you can go to the Apple Developer site and sign up for a free account.  You can then download the SDK package.  Once it’s installed it should be in folder called “Developer” but if you just search for “AU Lab” on your computer it will come up.

3/10/11 NOTE:

The UA LAB Version used in all of these examples is AU LAB Version 2.1.  Version 2.2 has not been stable on my system with the Apogee Duet.  You can read about the current version here – but in the meantime – you may want to download X code 3.2.2 Developer’s Tools – which has version 2.1 of AU Lab, if it isn’t installed on your system already.

Before getting into the setup – here are the tools I’m using for this particular rig:

Hardware:

FNH custom guitar:  You can find a full review of this guitar here.

Macbook Pro- 2.4 Ghz Intel Core 2 Duo.  This is actually a 2008 version I got with a killer educational discount.  15” with firewire 400 and 800.  This Macbook has had 4 gigs of memory that I got from OWC (although the first slot can take 6 gigs so I’ll probably upgrade that before the end of the year) and a  Seagate 500 gig 7200 rpm drive.  I underestimated just how important the internal drive was to performance but it made a very big difference.

Lacie Rugged Drive – This is the 320 gig bus powered version.  Also 7200 rpm.  I run it on the firewire 800 port and use it to record to.  It’s a little overkill – but I can use it for larger sessions as well.

Apogee Duet – Firewire interface.  No other A/D converter near this quality in this price range –  No question about it.

Line 6 FBV shortboard Mark II – Line 6 got it 100% right with this product.  Smaller than the old shortboard, but can be USB powered.

Ilok key – This is required for the Ilok version of POD Farm.

Korg nanokey – The keyboard for this is a little toylike – but I’m not a keybaordist.  It is velocity sensitive and kits in a laptop bag – and I can use it to trigger patches, samples, etc.  I think all the Korg nano products are really cool.  Very useful item.

Apiotek USB 2.0 Quad – This is an express card adaptor that opens up 4 usb slots on the computer.  Since the Macbook only has 2 USB ports and I have at least 3 usb devices – this is REALLY helpful.

Software:

I’m not going to go into any real depth on the software – As I’ve already covered it in other posts.  (Look under LAPTOP GUITAR RIG)

AU Lab

POD Farm 2 Platinum (And POD Farm Elements)

La Convolver

RedWirez

SooperLooper

Absynth

Optional Software:

If using this hardware you will probably have to use one or all of these at some point.

Audio Midi Setup (Mac application – part of the OS install)

Apogee Maestro (Comes with the Duet)

Line 6 FBV Control (Free download from Line 6)

This will be a VERY indepth tutorial – but I want to make sure I cover everything I can.

AU LAB Set up

Go ahead and launch AU Lab

You’ll come to a screen that looks like this:

I want to run a stereo channel out so this is fine.

Click Next.

Notice that the default setting has no input – you can change this later – but it helps to set it up now.

Click Add Input.

Now you have an input source.

Click Next

In this case I’m using the Duet – so it came up as the default in the Audio Device field.  If you’re not seeing the audio device you want to use open Audio Midi Setup (in the Applications – –  > Utilities folder) and make sure you see it there.

You can check the input channels if you’d like:

This shows that the Left/Right 1/4” ins are both available.  I’ll only be using Instrument 1 for the guitar – but I could run another instrument if I wanted to.

Click Done:

Here’s the screen that you’ll get.  If you have your guitar plugged in and strum a chord – you should hear it.  But this is going to get a lot better.

POD Farm set up

The first step is to set up PodFarm:  Click on The Effects tab in Audio 1 and scroll down until you get to Podfarm 2.

Here is the default screen in Pod Farm:

What I’m going to do here is set up a clean and distorted channel that I can switch back and forth between and automate some of the parameters so I can change them with my shortboard.

The First thing to do is get the input sorted out – since I’ve selected a stereo input in AUlab – the default in Pod farm will be a stereo in.

I only need  the left channel in as I’m only using 1 guitar for right now.

If I click on the arrow to the right of input: Stereo and scroll down to left – I now have the Instrument 1 Input on the Duet (left) as the input for this channel.

Before setting everything up – I’ll take a second to get in tune:

If I click on the tuning fork to the right of the Line 6 logo – that opens the Tuner.

If I click on the tuning fork to the right of the Line 6 logo – that opens the Tuner.

The next step is to create a Dual Tone.   In this case I’ll just copy the current tone.

Click the dual button and select Copy Tone.

And you’ll get this:

Note that the input has stayed the same as well.  Now my single guitar input can be used on both channels.

In general, I haven’t had a lot of success with 2 channel sounds – particularly distortion – which tends to overload in unpredictable ways.  I’ve clicked on the A+B Switch to turn it off.

A brief note:

The first time I did this – the guitar tone was digitally distorting (unpleasantly) so I brought the output of PodFarm down and it was still an issue.  Once I opened Apogee Maestro – the utility that came with the Apogee Duet – I realized that the signal coming out of the Duet was too hot.

It’s important to realize that the more items you add, the more things you’ll have to check when it goes wrong.

You may want to save the AU LAB session and save the POD Farm patch as well.    AU Lab saves all the settings of all the effects in the session, but you need to save the patch in POD Farm to load it again.

In future sessions, I’m going to create an A/B rig with a dirty and clean guitar amps and use the midi learn functions to change effects with the Line 6 Shortboard.

You can find all of the laptop guitar rig posts on the Blueprints tab on the top of the page.  Once on the blueprints page – just scroll down to the Laptop Guitar Rig section. 

Thanks for reading!

Setting Up “Testing Environments” Or Multi Layered Tones In AU Lab

Posted on by
Reply

One site that I always forget to link to and need to do so now is the Guitar Amp Modeling Blog,  which is just a really tremendous resource.  It’s really inspiring to me to see so many people working on pushing more and more into alternate live and studio approaches to guitar.

A couple of days ago I went to the Speaker Cabinet Impulse section of the forum and found that RedWirez, a company that sells a high end collection of speaker impulses is giving away their impulses from a Marshall 1960A with Celestion G12M 25-watt Greenbacks to celebrate their birthday!  The folder is about 107 MB of impulses that go from 44.1 KhZ – 16 bit to 96 KhZ – 24 bit.

There are 17 different types of mikes used for each IR set AND there are ambient mics to capture the back of the cab at various distances, room and wall mics as well. You can go to the link for that here.

I still have the recabinet set – which at $15 for something like 2000 irs is an amazing bargain as well.

But one thing that comes up in something like this is how do you sort through all those speaker sounds?

My solution is to set up a bunch of instances of LA convolver on multiple busses in AU LAB.

In this way I can set up one bus at a time and mute the other channels to be able to a/b/c everything.

Additionally, you can set up more complex sounds by combining different IR’s.

For example here are the IR’s used in bus 1:

and bus1 is the tone.

Here are the IR’s used in bus 2:

and bus2 is the tone.

Here are the IR’s used in bus 3:

and bus3 is the tone.

And the final tone of all 3 together:

To my ears, this creates a more full bodied sound than any one channel.  Each plug in takes up more processing power – so it may be a balancing act based on resources – but since AU LAB uses so much less CPU than something like Logic, it’s easier to pull off here.

In case you’re interested – here’s the patch the sound is based on:

Thanks for dropping by!