Blog

Pod X3 Live Review, Two Years Later

Pod X3 Live Review, Two Years Later

6b8162e9-73be-48cb-8507-9f6e5a07fcb16 comments

When I first got back into guitar 7-8 years ago, a friend recommended I check out GuitarPort from Line 6.  Since then, I’ve run through quite a few different products from them.  After getting hooked on modeling with the GuitarPort, I got a used Vetta that I used for playing out live.  Even though they have not updated that in years, it is still a great modeling amp with an almost perfect feature set.  The down side was, well, it’s an amp and weighs a ton.  Somewhere during that early period I got a regular gig playing in the band at church and the thought of hauling the Vetta back and forth twice a week quickly wore on me.  So… I picked up the Pod XT Pro and stuck it in a portable rack case and used the same floor board that I used with the Vetta.  That wasn’t bad, but the tone options weren’t as good as with the Vetta.  Thus began a years long quest to find the Vetta options in an extremely portable package.

The Vetta and Pod XT Pro eventually went on eBay and I picked up a new Pod XT Live.  Finally — portability was at hand!  I also added a Variax 700 to my rig and with just two pieces of gear to haul, I could cover all the bases, from acoustic to Stratocaster and Les Paul sounds. That was my main rig until the Pod X3 came out a couple of years ago.  I sold the XT Live and switched to the X3 Live.  With dual tones, I finally had a lot of the options I missed from the Vetta without the back pains to go along with it.  What follows are my thoughts on two years of regular use of that combination.

 

First, here’s the things that I really like about it.  It’s extremely light.  The pedal is much more fluid than the XT’s pedal was.  It has built in S-PDIF out (that I use for recording) and stereo XLR outs.  It also has the ability to drive 1/4″ outs at the same time and have the volume knob control only the 1/4″ outs.  Why is that handy?  Because you can hook up your own monitor to hear yourself and control the volume from that independent of what you send to the board.  We play on a pretty crowded stage and with only 2 monitor channels and the inevitable “more me” from everybody, it got pretty loud.  Being able to drive a separate local floor wedge was a great solution.  At least for me it was :D   Another obvious plus is you can control the Variax with the patches, so switching from acoustic to electric is as easy as changing patches. Definitely a cool option.  Another plus (and a huge minus) is that the dual tones are completely separate.  If you have a guitar with a piezo output, you can route both cables to the X3 and get some of the same Variax style flexiblity — switching between acoustic and electric (and controlling which of the two 1/4″ inputs the tones use) — at the stomp of the foot.

So, what’s not to like?  Well, the X3 was anticipated as the “Vetta on the floor” solution.  Unfortunately, if you want to do more than run a single amp model and limited effect options, it’s not.  The Vetta still blows away the X3 in terms of routing flexibility.  The Vetta is more like a 2 amps at once feature rather than dual tone.  With the Vetta, you can stick an overdrive in front of the signal chain and when it’s on, it drives both amps.  You can do the same thing with the the X3, but you have to keep them in sync on both tones and to turn the stomp on or off, you have to hit a button to toggle the stomp, then hit a button to switch to the other tone, and hit the stomp button again.  Repeat the process to toggle the effect.  The other option is burn another patch — one with the stomp on and another with the stomp off.  So now 128 patch slots doesn’t look so good.  This same issue affects the mod and delay settings.  The only way to turn an effect on or off globally is to switch to the patch that has it set the way you want.  Now when you’re tweaking, even if you’re using GearBox, migrating amp effects or stomp effects between patches is a real nightmare. The other killer here is delay tails.  When you switch patches because you want to turn off delay on both tones, the delay tails stop.

I’ve also had a few hardware issues with mine.  The main knobs have a “wiggle” sensitivity problem. Vibration or who knows what makes the X3 think you’ve changed a knob and so all of a sudden drive will go to wherever the knob is set.  You can park the knobs at 0 or 10 to minimize the issue but still — it’s a pain.  The other problem was the super-cheap S-PDIF connector they used.  If you apply any pressure what-so-ever when hooking up, it will eventually break one of the solder legs that connects the jack to the circuit board.  A little solder fixes the problem, but again, not something you should have to do with normal use. And here’s the real problem — it’s plastic.  Plastic attracts dust like crazy. My XT never caught the amount of dust my X3 gets.  And as you can see from the picture, I’m not a fan of dusting.

Now there are solutions for all of this.  When the the X3 came out, there was no MIDI support.  With a software upgrade, they added full MIDI support so you could program a MIDI board to toggle the stomps with a single button press.  But then you’re back to carrying something extra around, which defeats the purpose.  You could at a Line 6 M13 and use the famed “four cable method” to get some of the Vetta flexibility, but again, it’s another box, to hook it up right you’d lose some of the Variax flexibility and you also lose the stereo separation because of M13 and FX loop limitations. And of course, I could dust more…

So there you have it.  Two plus years later, I still use the X3.  Mostly because I haven’t found anything else in the price range that comes close to the options I want.  But that doesn’t stop me from wishing that the X4 will be the Vetta on the floor we were all hoping the X3 would be.

 

Move Vista’s Users folder to a Different Drive

16790fd9-cfee-4e70-830a-47f709d0f72a9 comments

OK, so I’ve finally gotten around to setting up a Vista machine as my main machine.  I opted to go with an SSD drive for the system drive and planned on putting all the user data on a different drive.  After doing a little research, the best solution to accomplish this with the least amount of hastle (or so I thought) would be to copy the content of Users to the new drive and set up a junction (symbolic link) to the new location.  Well, that was certainly easier said than done.  Everything I read suggested to do all the copying and sym-linking from the command prompt from the Vista setup disk because the Users directory is in use once Vista is running.  The problem with doing that turned out that the drive letter assigned to the new home for Users wasn’t the same during setup as when running Vista.  After multiple attempts to get the setup instance of Vista to use the same drive letters as the running instance, including re-installing Vista after failed attempts rendered the Users folder unusable, I decided there had to be a better way.

During my initial research, I found mention of people using MOUNTVOL instead of MKLINK.  The main difference is that MOUNTVOL makes the entire disk volume available at the mounted location rather than just a directory.  Depending on your application, that may be too restrictive.  But for my application, that was fine as that’s what I wanted to do anyway.  And the huge benefit of using MOUNTVOL is that the pointer is to a physical drive, not a logical drive letter.  After installing and booting to the setup CMD shell, renaming the Users directory to something else, I created an empty directory and mounted the drive on it.  I then used ROBOCOPY to copy the Users directory content back to Users, thus restoring and preserving the settings and security attributes.

So, here’s my recipe:

Install Vista (if you haven’t already)
Boot to the setup CD and once the installer is running press Shift+F10 to get to the shell

Then, on the boot drive:

ren Users Users_save
mountvol

(Note: no parameters on the mountvol command to get the volume label of the disk you want to use.  Then use the shell’s clipboard feature to copy the volume label to the clipboard.)

mountvol \Users <paste the volume label here>
robocopy \Users_save \Users /MIR /E /XJ

Reboot and enjoy.

 

All about Moonlighting

All about Moonlighting

375b08f1-1d7f-449d-b5a9-6dcf3cf6abcd, Photographic2 comments

Moonlighting (also called tree lighting) is a technique where the light is placed near the top of the tree and shines down.  It’s great for getting some soft general area illumination without the glaring effect of flood lighting.  It is best done in trees that are at least 20 to 30 feet tall and in trees that keep their leaves year round.  Here in Dallas, the best type of tree to do this in is the Live Oak but it can also be done in any large tree, including Red Oaks, Burr Oaks and Pecans and Elms.

The picture below is of a Burr Oak in a back yard.  It’s common in the Dallas area to do this type of lighting using a type of bulb called mercury vapor.  It creates a blueish green type of light that is soft and creates similar patterns on the ground.  However, the Energy Act of 2005 stopped the manufacture and import of mercury vapor ballasts (electronics required to ignite the mercury vapor bulbs) starting in January of 2008.  There are alternatives but they all use a fair amount of electricity (typical mercury vapor bulbs are 100 watts).

This tree was lit using a ceramic metal halide bulb (CMH) from Outdoor Lighting Perspectives (www.outdoorlights.com).  It’s only 39 watts and puts out more lumens than a 100 watt mercury vapor bulb.  It also produces a soft white color light so the landscape elements are illuminated in their more natural color, rather than the blue/green tint from mercury vapor.  All in all, a pretty cool effect!

New version and new theme

ecb807e3-8744-465a-8d03-1148a88a875a0 comments

I’ve been using the latest version of BlogEngine.Net and in the process of upgrading to Visual Studio 2008, I reorganized the solution for the whole site.  It’s now simpler to maintain and I’m now on a near-pristine copy of BlogEngine.Net which will make picking up future updates quite a bit easier.  As is usually the case with software, it’s much faster and simpler to implement something the second time around, especially when you don’t worry about maintaining any old data.  So, the old posts and comments are gone.

One interesting problem of note that I ran into while doing this was the blog main page would not load, complaining about not being able to find the Standard theme.  Everything worked fine on my development system but would not work when published out to GoDaddy.  Turns out that when it is running on IIS, the theme of the parent site (in this case,  www.keenesoftware.com) was defaulting onto the blog’s site (www.keenesoftware.com/blog).  The fix is to add a theme=”" attribute on the <pages> tag in the blog app’s web.config file.  Since BlogEngine.Net does it’s own theme handling, I would think this would be the default but it’s not. If you run into this issue while trying to add BlogEngine.Net to your own site as a virtual directory, this should fix it.

I’ll try to keep this blog a bit more persistent going forward so comment away.

  Newer posts →