Skip navigation
4690 Views 85 Replies Latest reply: Mar 6, 2013 3:24 PM by snhirsch RSS
perapera Just Startin' 40 posts since
Jun 19, 2010
Currently Being Moderated

Jan 9, 2013 9:54 AM

What every POD HD 500 owner *REALLY* needs to know!

Hi guys, sorry, no kidding here:

I really think these are important things not stated (or in some cases not clearly stated) in the manual, that you need to know to start seriously programming your POD HD

 

I ran some serious tests on my Pod HD 500 and here is what I found out,

I'll try to be as synthetic (but complete and clear) as possible, but this is going to be a long reading so sit down and take your time or just go surfing somewhere else

 

§ § §

 

1) the "famous" [input-1: guitar / input-2: variax] setting gives you different levels of signal depending on the position of the first *mono* effect block you use (amplifiers included), in particular you LOSE 6dB in the "pre" path in comparison to the path A/B or post path

(note that this is not the same as saying that you gain 6dB with input-2 to "same", read on).

 

[ if you don't know what I'm talking about just go and read this thread: What every HD500 owner needs to know!

http://line6.com/support/thread/74045?start=0&tstart=0

then come back here to hear a different opinion on the matter]

 

first of all, try it out:

- connect a guitar to the guitar input and the Left output to a full-range linear amp (or use your headphones)

- recall a "new tone" default blank patch

- set input-1 to Guitar and input-2 to Variax

- set mixer channel A fader to unity (0.0dB) and pan to center

- set mixer channel B fader to mute

- setup a noise gate* with the threshold set to 0% in "pre" position

(with this setting this IS a unity gain mono fx block)

- play thru it

- now if you bypass it, you'll hear that it  looses 6dB of level when it's active (I initially thought this was noise gate's fault, but it's NOT)

- now re-activate the noise gate and move it in A or "post" path

- now if you try to bypass it you'll hear that it does NOT loose any dB

- try moving the block back and forth ** between pre and A or post paths and you'll hear more level in path A or post than in pre

 

[please note that this was edited some minutes after posting for small but significant typo's]

 

this was already found out at least by hurghanico here: http://line6.com/support/message/403287#403287

but it's so important that needs a dedicated and more detailed thread.

 

[* you can repeat the experiment with other mono effects instead of a noise gate but keep in mind that, if you want to clearly hear a level difference, you need a mono unity gain (www.music-dictionary.org/unity_gain) effect, for example:

- a tube comp with thresh 100% & level 2% settings will work just  as the noise gate above

- an fx loop block with a mono cable connected between send and return will work just the same (but also read point 2 below)

- do it with an amp with medium-low gain and, moving it between pre and A or post paths, you'll hear a significant difference in gain/ovedrive/distortion here, not only level difference

** Notice that I found an intermittent bug here that could change the result of the test: see point 3) below]

 

OK now that you heard it, let's see it in detail;

 

these are the REAL schemes of the pod and fx blocks routing, yes it's done by hand and I love it ;-)

 

http://dl.dropbox.com/u/8875989/Pod_HD_forums/pod_routing_%26_fx_blocks_graphs.png

 

As you can see the pre path is a "dual-path"

while A, B and post are all stereo paths;

at the splitting point, where the path A and B are born,

the signal coming from input-1 is splittted to the Left and Right channels of the path A

and the signal coming from input-2 is splittted to the Left and Right channels of the path B;

 

furthermore all fx blocks have TWO inputs and two outputs and the mono blocks do attenuate by 6dB and sum their inputs, then process the result and then split their mono output to both outputs of the block;

 

for those who don't know, notice that:

- summing two identical signals or doubling a signal, gives you the same signal with 6dB more

- "splitting" means duplicating one mono signal to two "routes", practically doubling it;

 

[and two side-notes:

- the "stereo dry & mono wet" effects are for example the pitch effects and the "dry" type delays, I'm not considering this type of effects in this post, but they work as expected from the scheme you see above;

- the mixer control named as "pan" is actually a "balance" control because if you move it to one side (e.g.: left) it acts on the stereo or dual mono signal by doing NOTHING on that side (left) and ATTENUATING the opposite side (right)]

 

So, if you only activate input-1, in the pre path, the first mono effect is attenuating the input 1 and 2 and summing them, but, since input-2 is actually silence, you loose 6dB;

in A and post paths the effects are receiving a doubled signal on L/R so for mono blocks attenuating and summing gives them the right mono signal level to process

 

so using "same" or "guitar" for input-2 does not mean to gain anything, but having a constant doubled signal wich is compensated by a 6dB attenuation in each mono summing it encounters in his flow

 

please note that I am NOT saying that using only input-1 is wrong, you just need to know that this can give you different gain results depending on the position of the first mono effect

 

with only input-1 active and the same parameters values, this:

http://dl.dropbox.com/u/8875989/Pod_HD_forums/rout-1.png

 

is giving you more distortion than that:

http://dl.dropbox.com/u/8875989/Pod_HD_forums/rout-2.png

 

and this is something that can not be ignored

...don't know how to be more clear than that

 

 

§ § §

 

 

2) the fx loop block is LOOSING 5dB on the send with the switch in the "stomp" position.

 

What I wrote untill here were just implications of how the routing of a complex multifx (like the pod hd is) can work; but now we go to something couter-intuitive and *guiltily* not stated anywhere in the manuals.

 

if you connect anything gain related (compression, distortion, preamps, envelope followers) into the fx loop you're getting the *wrong* result

 

this includes the very popular four-cable-method (http://line6.com/support/docs/DOC-2504)

 

Now I'm going to explain this and give a SOLUTION to the problem, let's see the details:

 

I have to say thanks to this post from anglepod (to whom I rashly replied that he was wrong and I'm gonna ask him his forgiveness for that): http://line6.com/support/message/393494#393494

 

and that I totally agree with the original post by jimsreynolds in this thread:

http://line6.com/support/message/397759#397759

but here I'm giving a different and easier solution I think

 

Anyway, what I measured is that, with the stomp/line switch on "stomp" and input pad on "normal", the guitar signal is attenuated by 5dB (approximated with no decimals) along his route from the input, thru no fx and then to the send jack, and is quite-compensated by gaining back 4dB at the return;

 

[this additional 1 dB difference (again approximated with no decimals) from -5 to +4 is even more inexplicable and could be only on my POD HD 500 unit, so you'll need to test your own]

 

furthermore, switching the stomp/line switch to "line" is (correctly) giving 12dB to the send AND compensating by attenuating the return by the same amount, but is "suffering" from the same -5/+4 attenuation/compensation, so you get +7dB at the send (+12 -5) and -8dB at the return (-12 +4) as a result;

 

I guess the reason for this attenuation/compensation is to put the unity gain at approximately half-way between a stomp and a line reference level, but this choice is wrong (or at least badly implemented and guiltily not documented):

 

common sense: when I connect my guitar directly to any guitar input (stomp-box or preamp) I have a "stomp" signal level, so:

- the stomp position of the switch should definitely be at unity (=same level as the guitar itself)

- consequently the "line" position should be +12dB on the send and -12dB on the return

- then we should (like anglepod noted) have the ability to give or take dB's on the send as well as on the return via some software trims

 

the SOLUTION to the problem is:

- set the fx loop switch to line

- set the send to -7 dB and the return to +8dB (could be e.g. -6 / +6 on different machines)

 

now you have a unity send and a unity return AND you can boost or attenuate both if you need it!

 

[

EDIT:

there are other solutions to this problem

see my post on the 9th of january

]

 

Then combining my 1) and 2) points:

if you connect a cable to just one of the fx return jacks (this works also with the Right return, not only the L/mono) the fx loop block acts exacltly like a mono fx block (see diagram above), so it attenuates and sums its inputs and then sends the result to the send jack (to both pins of the TRS jack to be precise), and then splits the return to both outputs of the block

this means that if you are using the [input-1: guitar / input-2: variax] setting and you put an fx loop in default mode into the "pre" path with for example your amp's preamp into it, you are loosing 11 (or 12) dB of gain!!

 

 

§ § §

 

 

3) I'm not spending time on this point because I've still to test it more but I'm pretty shure I found an intermittent bug on the action of moving an effect on the signal chain that complicates the investigation on all the things you read above (but doesn't deny them)

 

if you try to replicate the steps at the beginning of my point 1) above, if the bug presents itself (and it's not always), when you move an effect from the "pre" path  to path A it works correctly giving you 6dB more, but when you move it back to "pre" it doesn't go back to minus 6dB; if you save the patch and then move to another patch and come back using the pod pedalboard and *not* with the edit software, you can start over untill you move the effect again forth and back

 

Of course I'll submit this as a support ticket as soon as possible

 

 

4) OK, after all this reading, I'm asking something more to you;

please, since it took me days of work ("fortunately" I was ill at home in these holidays) to test, re-test and write all of this in english (which is not my mother language), you owe me this:

- re-read it (I'm not kidding)

- ask me any question you have (but don't expect me to be ill at home to much :-) )

- do all or some of the same kind of tests and then confirm, correct or deny my results

 

OR just shut-up, please ;-)

 

I hope to have been helpful to you... all that work was helpful for me!

 

thanks for reading and a happy new year!

 

bye

Lore

  • snhirsch Just Startin' 67 posts since
    Oct 17, 2012

    Very nice work.  If you are correct in your analysis, this is the type of detail that really should be present in the advanced users guide.  Two minor points: 

     

    1. No problem with hand-drawn figures, but it's difficult  to read the legends even after working on the png with a graphics program. 

     

    2. Do you possibly have the "mono fx block" and "stereo fx block" legends switched?  Looks to me like that's the case, but perhaps I'm misunderstanding something.

  • CairnsFella Just Startin' 205 posts since
    Sep 16, 2012
    Currently Being Moderated
    Jan 2, 2013 10:56 PM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    Thanks for this info and hard work. I am alread a 're-convert' to the guitar/same input approach, but I look forward to getting home and running through your examples nonetheless.

     

    Thanks again (and I can read your writing ... but then my writing is worse

  • dbagchee Just Startin' 235 posts since
    Apr 12, 2007
    Currently Being Moderated
    Jan 2, 2013 11:24 PM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    This is great information. Thanks for taking the time to pick this apart. I just recently tried switching to variax on the 2nd input based on the other thread and definitely noticed a significant difference in the gain response from amps I had been using. I just assumed that this was how they were supposed to sound but now I will have to go back and look at my FX chains and I bet I'll see that I was getting the 6db drop (I almost always have the noise gate first, always on and in the "pre" path). I think this point you made is really important for people to note:

    please note that I am NOT saying that using only input-1 is wrong, you just need to know that this can give you different gain results depending on the position of the first mono effect

    This is just more information we need when we design our patches. I really hope Line 6 is paying attention to these discussions. Like others have said, the pedal should have "smart" defaults that setup the signal path correctly for the most common usage (80/20 rule). If I'm just using a mono chain I shouldn't have to be getting into all these deep parameters or understand the effects of improper gain staging.

  • jimsreynolds Power User 2,227 posts since
    Jun 27, 43450

    Still chewing through all of this but wanted to make one point regarding the FX Block.

     

    Yes, you can turn the Loop Level switch to 'line' (with corrections to the send and return levels) as a way of boosting the FX send output.  The problem here is that you also raise the noise floor.  I tried this approach early on when I was trying to get my 4CM in order and the level of hiss that it introduced was significant.   The hiss level is not affected by the send/return levels on the loop and is constant.  This is why I rejected the approach ... which I agree, in principle should have been a great solution.

     

    Another forum member, Gortur gave it a try on the thread here and found the same result -->http://line6.com/support/message/340532#340532

      • jimsreynolds Power User 2,227 posts since
        Jun 27, 43450

        Hi

         

        Again, still chewing through your findings (you have been a busy boy) but the fact remains that specifically with 4CM, you get a lot more hiss with the loop set to line.

         

        The signal comes out of the Pod FX loop direct into the amp's guitar input.  The amp guitar input is designed for a signal around -10dBV.  The line output from the pod is at around +4dBu ... about four times the voltage.   For whatever reason, the ambient hiss level stays high and constant regardless of where you set the FX Loop Send Level.

         

        You might replicate something similar by simply taking the Pod FX Send out to an amplifier and cranking up the amp level/gain to hear the net impact.  It ain't pretty and you cannot correct for it downstream in the hookup.

         

        I did not go into deep investigations but I remember that, when I set a patch cable linking FX Send and Return and monitored hiss at the 1/4" output, the level of hiss was not increased when I switched from Stomp to Line.  I guess then that the FX Return compensates for whatever boost or cut there is in the FX Send.  However,  in the 4CM scenario the result seems to be Hiss.  Obviously this is much more audible with the amp in a high gain configuration. 

  • hurghanico Just Startin' 399 posts since
    Jan 28, 2007

    Good job parapera


    finally it was time for someone to open his eyes and trying to really understand how things are ..
    in several past threads I tried too to explain how routings of the signal really work in relation to the input settings and the position of the blocks ..


    now it's your turn ..


    keep it up, and good luck


    Hurghanico

  • phil_m Expert Line 6 User 4,243 posts since
    Jan 25, 2007

    This makes sense to me, and I appreciate all the work you put into it. I also like your wiring diagrams! The only thing that gives me slight pause is that the idea that the input signal is attenuated before being input into a mono effect actually contradicts what's actually in the Advanced Guide. On 6.2 it says this:

    Note that when utilizing both Inputs 1 & 2 (or when using “SAME” for either of these Input options) the two Input signals are combined to allow them to be fed into any Amp or mono FX Model within the Pre position, which can result in a hot signal level. Reduce your instruments’ volume as needed to avoid overloading your Pre-positioned Models.

    In this and in other places, the Advanced Guide seems to say that using only one input is the way to preserve a true mono input signal. So either you're right and the Advanced Guide is wrong, or there's some other sort of signal processing going on.

      • Akeron Just Startin' 224 posts since
        Jul 23, 2011

        Two years of arguing, pages and pages of obscure technical explanations and the solution is... use the default settings?

          • Akeron Just Startin' 224 posts since
            Jul 23, 2011

            perapera wrote:

             

            but ...beyond jokes:

             

            I wasn't joking The fact that periodically somebody gives a different interpretation on the same subject is crazy! I guess that was the Mayans best kept secret. Thank you anyway, what you've said made sense in a way, dear homonymous We will never ever know who is really right though...

             

             

            PS: Oh no, I prefer the "wrong" settings,. What I'm going to do now...

    • TexLefty65 Just Startin' 12 posts since
      Feb 17, 2012
      Currently Being Moderated
      Jan 3, 2013 9:02 AM (in response to phil_m)
      Re: What every POD HD 500 owner *REALLY* needs to know!

      phil_m wrote:

       

      This makes sense to me, and I appreciate all the work you put into it. I also like your wiring diagrams! The only thing that gives me slight pause is that the idea that the input signal is attenuated before being input into a mono effect actually contradicts what's actually in the Advanced Guide. On 6.2 it says this:

      Note that when utilizing both Inputs 1 & 2 (or when using “SAME” for either of these Input options) the two Input signals are combined to allow them to be fed into any Amp or mono FX Model within the Pre position, which can result in a hot signal level. Reduce your instruments’ volume as needed to avoid overloading your Pre-positioned Models.

      In this and in other places, the Advanced Guide seems to say that using only one input is the way to preserve a true mono input signal. So either you're right and the Advanced Guide is wrong, or there's some other sort of signal processing going on.

       

      Hi Phil,

       

      Interesting discussion here. I don't see that Advanced Guide satement to be "incorrect" though. I think we're just getting beyond that concept into a deeper understanding and different ways to refine the signal chain here. I do recall there being a prevalent problem early on with POD HDs where guys with hot pickups were complaining that they were getting input clipping. I think a lot of that problem was a result of them using the default input routing (where both inputs received the Guitar signal) and then placing a mono amp/effect in the Pre section. So the Guide's statement does serve as a good caution for people running into that problem. I didn't read that statement to be a hard rule to "never use both inputs" since obviously you need to do that (when there is no mono block in the Pre section) to feed your guitar to both paths. I bet that if Line 6 instead made the default that Guitar was only set for Input 1, then a LOT of guys would not figure out how to get their guitar routed to both paths for a lot of presets. So I can see where they probably had to set this to be the default (as well as to have Variax and Line In active by default - so in most cases, most things "just work" when you start using the POD!)

      • jimsreynolds Power User 2,227 posts since
        Jun 27, 43450

        TexLefty65 wrote:

         

        I bet that if Line 6 instead made the default that Guitar was only set for Input 1, then a LOT of guys would not figure out how to get their guitar routed to both paths for a lot of presets. So I can see where they probably had to set this to be the default (as well as to have Variax and Line In active by default - so in most cases, most things "just work" when you start using the POD!)

        This!

         

        Whether it is better or not to use both inputs, setting the second input to variax causes minor routing chaos downstream and this would leave most casual users in a real mess.

         

        The point of all this is that the routing and levels within the HD are complex. There are different scenarios for different users based on their requirements, shaped by choice of inputs, effects, effect locations, panning, mono/stereo, mixer channels in use, outputs in use, input pads ... and probably other stuff too.  

         

        It has taken several years of end-user fiddling to get close to the full set of scenarios (and the work here by perapera is a good contribution to that).  IMHO ... this forum is serving its purpose: a grass-roots method of flushing out all of the uses and issues with the POD and documenting them.  The primary documentation could probably do with some additional material covering these subjects but if that ain't coming then this will do.

         

        Perapera, I have little expectation that Line 6 will take up your challenge.  It just don't work like that.   It would involve a collaboration between support staff, technical authors and design engineers in a way that doesn't usually happen as an ad-hoc exercise within a business unless there is a very strong imperative.  Happy to be proven wrong.

        • meambobbo Iknowathingortwo 1,702 posts since
          Dec 13, 2007

          this is why i thought it would have been smart for line 6 to include some templates or use cases that could be switched back and forth on any patch that would go through the half dozen or so most popular use cases.

           

          1) mono guitar - single amp - stereo/mono post effects (no dual paths, no mixer)

          2) guitar + variax mixed - single amp - stereo/mono post effects (for mixing both mags and variax input into the same path...or switching between which is used on your variax) (input 1: guitar, input 2: variax, no dual paths, no mixer)

          3) guitar + variax - independent paths (input 1: guitar, input 2: variax, default 4 blocks each in Channels A and B, not pre-split or post-mixer, default amp in channel B to none)

          4) guitar + vocals - independent paths (same as above but input 2: mic)

          5) guitar + aux - independent paths (same as above but input 2: aux)

          6 play along - guitar + aux - independent paths - aux dry (same as above but all 8 effects blocks in Channel A)

          7) mono guitar - dual amps (essentially what we have now with input 2: guitar/same)

    • hurghanico Just Startin' 399 posts since
      Jan 28, 2007
      Currently Being Moderated
      Jan 4, 2013 2:51 AM (in response to phil_m)
      Re: What every POD HD 500 owner *REALLY* needs to know!

      phil_m ha scritto:

       

      This makes sense to me, and I appreciate all the work you put into it. I also like your wiring diagrams! The only thing that gives me slight pause is that the idea that the input signal is attenuated before being input into a mono effect actually contradicts what's actually in the Advanced Guide. On 6.2 it says this:

      Note that when utilizing both Inputs 1 & 2 (or when using “SAME” for either of these Input options) the two Input signals are combined to allow them to be fed into any Amp or mono FX Model within the Pre position, which can result in a hot signal level. Reduce your instruments’ volume as needed to avoid overloading your Pre-positioned Models.

      In this and in other places, the Advanced Guide seems to say that using only one input is the way to preserve a true mono input signal. So either you're right and the Advanced Guide is wrong, or there's some other sort of signal processing going on.

      actually the misunderstanding started exactly from what is written in parentheses (which I think is wrong and probably an oversight) in the phrase of the manual that you have reported here ..
      taken away what is written in brackets, the rest of the sentence makes sense, since you can send simultaneously 2 different signals from 2 different instruments to a single mono effect or amp ..
      therefore the 2 signals, even if halved, when combined together may give a too high signal level to the individual mono-fx/amp input..


      and in fact over there is written "instruments", in the plural

    • hollis1003 Iknowathingortwo 342 posts since
      Feb 6, 2007
      Currently Being Moderated
      Jan 3, 2013 10:36 AM (in response to perapera)
      Re: What every POD HD 500 owner *REALLY* needs to know!

      I think what most people on this forum want is an accurate representation of what happens when you plug in a guitar to real pedals and an amp. 

       

      IMHO the best way to do that is use input 1=guitar and input 2=same. 

       

      I wish someone would compile the long list of unanswered questions, even if we think we know the true answer, and let Line 6 respond.  Of course it won't happen, but I can dream.

      • spikey Just Startin' 378 posts since
        Feb 1, 2007

        hollis1003 wrote:

         

        I think what most people on this forum want is an accurate representation of what happens when you plug in a guitar to real pedals and an amp. 

         

        IMHO the best way to do that is use input 1=guitar and input 2=same. 

         

        I wish someone would compile the long list of unanswered questions, even if we think we know the true answer, and let Line 6 respond.  Of course it won't happen, but I can dream.

        What I wanted was somthing simple to use that sounded killer.... I think I got a little of the last part....

  • Jeffsco Just Startin' 37 posts since
    Aug 28, 2007
    Currently Being Moderated
    Jan 4, 2013 10:48 AM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    The links to the Dropbox details do not seem to be working. Any suggestions on how to access the flow diagrams?

  • PDKTDK Just Startin' 100 posts since
    Dec 24, 2011
    Currently Being Moderated
    Jan 16, 2013 6:08 AM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    Outstanding!

     

    Hurghanico (and now you) have been getting a lot of my attention lately.

     

    Does anyone know if this would apply to a L6 Link-ed DT amp?

    • drewfx Just Startin' 53 posts since
      Oct 22, 2008
      Currently Being Moderated
      Jan 10, 2013 3:06 PM (in response to perapera)
      Re: What every POD HD 500 owner *REALLY* needs to know!

      I ran into all this when I had an HD500 for effects only; I couldn't for the life of me get a clean signal-path. At the time it was more important to me to use the HD500 for effects, so I sent it back to the shop.

       

      Line 6 need to fix this really, although I don't know if they can?

    • MartinDorr Just Startin' 98 posts since
      Nov 3, 2011
      Currently Being Moderated
      Jan 11, 2013 12:18 PM (in response to perapera)
      Re: What every POD HD 500 owner *REALLY* needs to know!

      I can confirm your Stuido EQ finding that the dialed in dB gain is usually off by a fair amount (up to 2dB like you found) between -18dB and 0dB as well as between 0dB and +18dB. It really Also make sure you are not trying to get more than  -12dB output from the Stuido EQ. If you do the Studio EQ will add compression, soft clipping and finally hard clipping (distortion) at the point when you exceed -3dB output. You may also want to stay below -12dB on the input side if you are looking for no gain pass through as it will reduce your level depending on how high above -12dB you come in. In summary, there are 2 effects at work in the Studio EQ: Its dialed in dB value is usually not what it usually produces and if you come in or go out above -12dB it will compress and finaly distort depending on how much higher than -12dB  you are coming out. Once you get into the compression range on the output the gain dials of the Studio EQ are even further off (output is always lower than what you think you dialed in).

        • MartinDorr Just Startin' 98 posts since
          Nov 3, 2011
          Currently Being Moderated
          Jan 17, 2013 1:40 PM (in response to perapera)
          Re: What every POD HD 500 owner *REALLY* needs to know!

          I like your response! Thanks for sharing your deeper insight into this topic. I think you are right on that one need to consider what outputs are in use before getting all worried about the levels and how the modeling gets affected. I stumbled over the Studio EQ behavior (actually the Mid Focus EQ does the same) when looking at USB output signal levels. What cought my attention was that although my DAW meter said I was at -6dBFS peak (quite a bit away from a digital cipping point) the Studio EQ added compression and a bit of distortion. Something I simply did not expect.

          I also agree with you that Line 6 is probably just emulating what the real HW does at high levels in the -12dBFS to 0dBFS signal level range, essentially emulating the real behavior of analog equipment.

          By the way, my JTV comes in at about -16dBFS using the digital interface. So it's not so far off from the hot -12dB. Also, if you use high gain amps it does not take a very high Drive setting to hit into the -12dB range with channel Volume at or above 50%. Maybe something to consider when you can't mesure and care to not get any unwanted distortion or compression.

          • lindsayward Just Startin' 156 posts since
            Mar 7, 2007

            Hi!

            I don't use the 4CM or the FX loop at all. I just want good clean sounds - I want good dirty sounds too, but I don't want unwanted dirt

             

            I do use a Studio EQ as my standard 'clean boost' option, at the front of the chain. I just tried it with the Tube Comp on Threshold 100% and Level up enough to sound about the same output as the Studio EQ on +5dB, which was about 12% for me. I alternated between them but couldn't tell much difference if any, except that without a noise gate, volume turned up and not playing the guitar, the comp had a slightly dirtier fuzz than the eq... although I just tried it again and couldn't tell the difference.

             

            I'm using a simple JTV (Variax) -> POD -> PA (mono XLR) setup, no FX loops or amps in the chain.

            I want to know what I can simply get out of this whole discussion to make my clean patches as nice and clean as I can, and the overall sound as good as possible.

            Any useful distillation would be most helpful thanks.

            • Ed_Saxman Just Startin' 62 posts since
              Jan 4, 2010

              I want to know what I can simply get out of this whole discussion to make my clean patches as nice and clean as I can, and the overall sound as good as possible.

              Any useful distillation would be most helpful thanks.

               

              Put everything on path A, pan centered, with the mixer last in the chain. Mute Path B.

               

              http://i812.photobucket.com/albums/zz46/Ed_Saxman/Capturadepantalla2013-01-16alas145424_zpsd10819ec.png

              This is what as a HD500 owner I *REALLY* needed to know from the beginning.

                • hurghanico Just Startin' 399 posts since
                  Jan 28, 2007
                  Currently Being Moderated
                  Jan 22, 2013 4:26 AM (in response to perapera)
                  Re: What every POD HD 500 owner *REALLY* needs to know!

                  perapera ha scritto:

                   

                  ...still waiting for Line6 to officially confirm or deny of my routing graphs...

                  I do not think that Line6 will never give any confirmation or denial of this explanation of the facts ..


                  they prefer that people see the flexibility rather than all the details and the exact measurements, in the same way as they have not
                  more explained (compared to older modelers) which exact controls are actually provided by the objects that have been modeled, for example the presence or not of the presence and the mid controls in some amps ..


                  even though the models and the system very well take their cue from reality, the whole thing is given as a palette of colors with which to mess as you like to make your own creations, this also explains why some values ​​are expressed as a percentage and not in absolute value ..


                  and perhaps another reason could be that if they declared that every detail was 100% identical to the reality, someone might have to say that making comparisons and
                  measurements is not exactly so .. therefore remaining vague, they are saved from this occurrence ..


                  so I would say if this is the basic philosophy, all these details will never be revealed ..

                    • hurghanico Just Startin' 399 posts since
                      Jan 28, 2007
                      Currently Being Moderated
                      Jan 22, 2013 6:02 AM (in response to perapera)
                      Re: What every POD HD 500 owner *REALLY* needs to know!

                      perapera ha scritto:

                       

                      ...I wrote private messages to the Line6 guys here on the forum some minutes ago, let's see what happens,

                      I think that many "likes" to my original post would encourage them to make an official statement...

                      have you ever heard about NDA?

                      http://en.wikipedia.org/wiki/Non-disclosure_agreement

                       

                      the Line6 guys are constrained by that agreement

                    • phil_m Expert Line 6 User 4,243 posts since
                      Jan 25, 2007
                      Currently Being Moderated
                      Jan 22, 2013 6:14 AM (in response to perapera)
                      Re: What every POD HD 500 owner *REALLY* needs to know!

                      I'd be surprised if they issue any sort of official statement. For one thing, I think I most users don't really care about the technical details as long as they can get the product to sound good. And really, why should they care? The Line 6 guys who are on the forums here are customer service people. The most they can do is pass info on to others in the company. Perhaps the Advanced Guide would be edited a little, but I don't see them totally revising it at this point. We're already over two years into the HD's life cycle, for one thing.

                • Akeron Just Startin' 224 posts since
                  Jul 23, 2011
                  Currently Being Moderated
                  Jan 22, 2013 4:28 AM (in response to perapera)
                  Re: What every POD HD 500 owner *REALLY* needs to know!

                  perapera wrote:

                  P.S.

                  ...still waiting for Line6 to officially confirm or deny of my routing graphs

                   

                  http://memegenerator.net/Waiting-Skeleton

            • spaceatl Expert Line 6 User 4,456 posts since
              Jan 24, 2007
        • meambobbo Iknowathingortwo 1,702 posts since
          Dec 13, 2007
          Currently Being Moderated
          Jan 22, 2013 7:54 AM (in response to perapera)
          Re: What every POD HD 500 owner *REALLY* needs to know!

          one things i wanted to mention about the tube comp.  it sounds transparent for most frequencies, but it actually is a low pass filter, with the cutoff frequency around 8kHZ.  Not really noticeable for most clean patches, but it's very obvious on bright, high gain patches.  usually you want a low pass anyway, so it certainly doesn't make it a dealbreaker - just something to be aware of.

  • Ed_Saxman Just Startin' 62 posts since
    Jan 4, 2010
    Currently Being Moderated
    Jan 22, 2013 8:15 AM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    Meambobbo Wrote:

     

    this is why i thought it would have been smart for line 6 to include some templates or use cases that could be switched back and forth on any patch that would go through the half dozen or so most popular use cases.

     

    1) mono guitar - single amp - stereo/mono post effects (no dual paths, no mixer)

    2) guitar + variax mixed - single amp - stereo/mono post effects (for mixing both mags and variax input into the same path...or switching between which is used on your variax) (input 1: guitar, input 2: variax, no dual paths, no mixer)

    3) guitar + variax - independent paths (input 1: guitar, input 2: variax, default 4 blocks each in Channels A and B, not pre-split or post-mixer, default amp in channel B to none)

    4) guitar + vocals - independent paths (same as above but input 2: mic)

    5) guitar + aux - independent paths (same as above but input 2: aux)

    6 play along - guitar + aux - independent paths - aux dry (same as above but all 8 effects blocks in Channel A)

    7) mono guitar - dual amps (essentially what we have now with input 2: guitar/same)

    That would have been amazing!

    Although we could still do that, with screenshots and all that stuff! Something that is easy to understand, and useful for everyone.

     

    perapera wrote:

    and for the path-A only solution by Ed_Saxman:

    yes this routing is a simple solution for a straight fx chain, it's like an HD400 with more fx blocks

    also in that situation if everything stays on path A, the input-2 setting does not matter (same, guitar, variax, aux...) : you get anything you choose from Input-1 at the right signal level on path-A

    Yes, does not matter since Path A is a straight chain and Path B is muted, but you can also use the path B to have a unprocessed signal on input-2(Same) using this routing. Or a different instrument/mic on Path B. In this way you can record 2 mono channels (wet/dry) at the same time on your DAW (panning all the way L/R this time).

     

    Since I never use dual amps/cabs, this is the way that makes more sense to me. And the easiest by far, if you want to make things works without complicated tech-talk, trial-and-error, more-tweaking-than-playing, or any weird  effects due to the dual inputs headache. (ty again, Meambobbo)

     

    perapera wrote:

    anyway, what comes from my understanding of the signal routing in the PodHD is that even if you use a default "new tone" and just IGNORE paths A and B and the mixer you get the EXACT same result: an HD400 whith more blocks!

     

    so why changing the default?!?

     

    see also this post of mine which has pictures:

    http://line6.com/support/message/405169#405169

     

     

    Becouse the default "new tone" is/was very confusing to most people, including myself. I´m afraid I prefer go single-arm-chain, wear bib overalls and go moonshining all night long, probably like most users. (And no, I don´t want a 300/400!)

  • meambobbo Iknowathingortwo 1,702 posts since
    Dec 13, 2007
    Currently Being Moderated
    Jan 22, 2013 8:12 AM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    as far as i can tell on routing, everything Lore is saying is correct.  i don't know exactly about all the precise level adjustments (6db vs 5db, etc), but I would defer to his research.

     

    Let's do a walkthrough example.  Let's say Guitar in is 100% volume.  Input 2 is Variax/null.  in the case of a mono effect in pre-split position, you get a halving of each input signal (100%/2 and 0%/2 = 50% and 0%).  Then they are summed (50% + 0% = 50%).  The processing occurs (let's assume level-neutral) than the output is duplicated and sent to both outputs.  So the output of the mono effect is two 50% signals.  When the left/top one hits the split, it is duplicated and we have two 50% signals hitting whatever is in Channel A.

     

    Now let's assume there are no mono effects in pre-split position.  The 100% left/top signal from the Guitar Input is duplicated at the split and sent to Channel A.  So Channel A gets two 100% signals.  When it hits the first mono effect, they are divided in half (two 50% signals) and summed (back into a 100% signal). This signal is processed then duplicated to send to each output.  So each output is two 100% signals.

     

    Test it for yourself - Lore is correct.

     

    FWIW, I prefer Input 2: Variax, placing a Noise Gate and/or Distortion effect in pre-split position, and using dual amps (really the same amp but different cab/mics).  So I like the halved levels - I find I have more control over my distortion (I do use fairly hot pickups).  I also sometimes place a volume effect with a fixed setting of 60-80% to attenuate the signal early in my chain before it hits any level-dependent effects.  This is sometimes necessary to prevent EQ's from clipping (note that EQ's are stereo effects and aren't first attenuated like mono effects).  It's probably better to place a Noise Gate in front of them.  But I also use it to prevent a Distortion effect from giving ANY distortion whatsoever, so I can use it just as a filter.

     

    I also have no clues about the FX loop mysteries.

     

    Line 6 employees can relay questions to the engineers.  This is how we got an official answer to the harsh/fizzy/digital distortion thread - that the distortion was modeled crossover distortion.  It shouldn't be this hard to get an official answer on how the product works.

  • hurghanico Just Startin' 399 posts since
    Jan 28, 2007
    Currently Being Moderated
    Jan 23, 2013 5:19 AM (in response to perapera)
    Re: What every POD HD 500 owner *REALLY* needs to know!

    perapera ha scritto:

     

    .....2) the fx loop block is LOOSING 5dB on the send with the switch in the "stomp" position.

     

    What I wrote untill here were just implications of how the routing of a complex multifx (like the pod hd is) can work; but now we go to something couter-intuitive and *guiltily* not stated anywhere in the manuals.

     

    if you connect anything gain related (compression, distortion, preamps, envelope followers) into the fx loop you're getting the *wrong* result

     

    this includes the very popular four-cable-method (http://line6.com/support/docs/DOC-2504)......

     

    -------------------------------------------------------------------------------------------------

     

    .......if you connect a cable to just one of the fx return jacks (this works also with the Right return, not only the L/mono) the fx loop block acts exacltly like a mono fx block (see diagram above), so it attenuates and sums its inputs and then sends the result to the send jack (to both pins of the TRS jack to be precise), and then splits the return to both outputs of the block.....

     

    First, I state that I have never used the fx loop and then what follows is only a hypothesis, fruit of reasoning and is not validated by concrete experiments ..

    let us put aside the manual for a moment ..

    if we look at our HD500, we can see that the outputs and inputs that can be used to give/get a (summed to) mono signal are clearly indicated ..

    UNBALANCED.JPG                               BALANCED.JPG 


      FX LOOP.JPG

    on the
    FX SEND output the only indication that I read is TRS STEREO, so I thought: could be that this output is only and exclusively stereo? .. I know that it wouldn't make much sense if it was so, but if it was true, inserting a standard mono (TS) cable into an output like this, you would get only the left half of the signal, and in this case a way to recover the missing part might be to use a TRS-to-TS cable..

     

    PS.

    doing a little search on this site I noticed the the FX LOOP SEND output has undergone several changes in some firmwares..

    it has been only mono, then it became only stereo, then it became stereo/mono, currently I don't know what it is really..


    keep experimenting


     

    A bit of history:

     

    http://line6.com/support/message/331918


    --------------------------------------------------------------------------------------
    POD HD500 Flash Memory v1.40 RELEASE NOTES

     

    Bug Fixes


    • FX Loop – In a mono configuration the FX loop does not sum left/right signal properly – FIXED

    -------------------------------------------------------------------------------------

    POD HD500 Flash Memory Version 1.31 RELEASE NOTES

     

    What's new since v.1.22?

     

    • TRS-jack FX Loop Send is now sending a  true stereo signal, not summed mono. If you are using a mono cable, the Left audio path is sent. 
        • Ed_Saxman Just Startin' 62 posts since
          Jan 4, 2010
          Currently Being Moderated
          Jan 24, 2013 7:09 AM (in response to perapera)
          Re: What every POD HD 500 owner *REALLY* needs to know!

          Hi fellas!

           

          Just my two cents. I´m using a RC-300 Loopstation (that has a clip peak led) with the HD500´s FxLoop switch set to line in the true stereo configuration (and FXloop last in the chain). I usually need to set a range between -6 and -24 on FXLoop Send parameter to prevent clipping the RC300´s inputs. This varies depending on the initial input source (for instance, changing the bass model on my Variax Bass 705 I may need to adjust that parameter, since different models have slight volume differences)

           

          Besides that, I usually set the parameter Return to +12, to get back comparable volume coming from the Loopstation, and the Mix parameter set to 50% (which seems to give 100% of both sources). Finally, I use the HD500 S/PDIF Out going to my sound card.

           

          Of course all this doesn´t mean anything, just my personal experience when using both units together.

           

          But I'm glad to see what I was doing "by ear" so far, is pretty much the same than the "line, send: -7 , return: +8" or "line attenuated" solution by Lorenzo.

           

          As he wrote:

          - set the fx loop switch to line

          - set the send to -7 dB and the return to +8dB (could be e.g. -6 / +6 on different machines)

           

          now you have a unity send and a unity return AND you can boost or attenuate both if you need it!

        • hurghanico Just Startin' 399 posts since
          Jan 28, 2007
          Currently Being Moderated
          Jan 24, 2013 5:36 AM (in response to perapera)
          Re: What every POD HD 500 owner *REALLY* needs to know!

          perapera, considering the results of your concrete tests it seems clear that those missing 5 dB should be considered definitely a bug

            • phil_m Expert Line 6 User 4,243 posts since
              Jan 25, 2007
              Currently Being Moderated
              Jan 24, 2013 7:01 AM (in response to perapera)
              Re: What every POD HD 500 owner *REALLY* needs to know!

              This may be a dumb question, but why is having unity gain so important? I'm used to running all sorts of pedals in front of amps, and I do try to have it so that the gain staging behaves in a way that makes sense, but I've never been particularly worried that I have unity gain. Actually, I've found that for most tube amps, I like having the input pushed a little harder as a baseline.

              • hurghanico Just Startin' 399 posts since
                Jan 28, 2007
                Currently Being Moderated
                Jan 24, 2013 7:57 AM (in response to phil_m)
                Re: What every POD HD 500 owner *REALLY* needs to know!

                phil_m ha scritto:

                 

                ...why is having unity gain so important?...

                is not at all important to get unity gain as an end result, but for someone it is important just to know whether you have it or not.. to understand why the response of some models or real fx/amp can be too weak, as expected or perhaps exaggerated depending on your choices of routings and other settings..

              • spaceatl Expert Line 6 User 4,456 posts since
                Jan 24, 2007
                Currently Being Moderated
                Jan 24, 2013 9:30 AM (in response to phil_m)
                Re: What every POD HD 500 owner *REALLY* needs to know!

                "unity gain" is a misused term in this context and many others...much like "true bypass"...Most of the folks using these terms don't really know what unity gain is or the real implications of true bypass...but hey, they sound good...makes me feel smart when I use them...

                 

                reminds me of these other false absolutions...

                Class A is better than AB...it's an A right? The B means, not as good as A...

                 

                and there's the notion that "signal must be balanced"...most folks don't realize that means a -6db loss in headroom...But hey it's balanced...that must be better right?

                • phil_m Expert Line 6 User 4,243 posts since
                  Jan 25, 2007
                  Currently Being Moderated
                  Jan 25, 2013 7:25 AM (in response to perapera)
                  Re: What every POD HD 500 owner *REALLY* needs to know!

                  if I connect the pod HD with the 4-cable method,

                  when I bypass every effect in the section of the pod between input and send,

                  I want to hear at least the same gain as if I was connected the guitar directly to the amp,

                  does this make sense to you?

                   

                  It makes sense to some extent, but I don't know if it's really that big of a deal. If someone is really concerned about the level they're sending to their amp, they can always flip the line/amp switch to line, turn the master volume down, and make up the gain that way. I just think it's very easy to miss the forest for the trees in these discussions. I think it comes down a lot to the type of players who are using the POD. Personally, I've never been the type of player who's thinks the tone of plugging the guitar straight into the amp is something I aim for. I always have at least one pedal on, so I'm always "messing with" my tone. I'm less concerned about what the pure tone should be, and more concerned about getting the tone I want. And franky, I think the people who really are tone purists probably would have written off something like the POD a long time ago.

                  • MartinDorr Just Startin' 98 posts since
                    Nov 3, 2011
                    Currently Being Moderated
                    Jan 25, 2013 7:41 AM (in response to phil_m)
                    Re: What every POD HD 500 owner *REALLY* needs to know!

                    Contrary to Phil I am very interested in a tone w/o or with very little effect. But despite that I think Phil is on to something very important: It's the result (the tone you want or achieve) that counts. Along those lines I am only interested in the level discussion and do my own measurements to avoid running the HD500 in a mode that prevents me from leveling different tones and that runs individual effect or amp models on or beyond the margins of its intended operation (due to too low or too high signal levels). Obviously, you can live in the margins and enjoy the result, but it is unlikely that you can predictably adjust such a tone so it works together with other tones or for different venues. At the end of the day I need to get some predictability in how to make my stuff fit in the world I am playing in (and the world is changing even if I just play in my home: sometimes my wife is home and sometimes not ;-).

                    • phil_m Expert Line 6 User 4,243 posts since
                      Jan 25, 2007

                      Please note, that I'm not saying that I don't think it's important to understand how things are working, although, for some players, I think they are happier just plugging a cord in and being lilke, "and then the magic happens! ". I just think there's a line between spending too much time on analysis and not enough time, well, playing guitar. I guess it's something I've learned from being involved in multiple bands and groups through the years. The times when I'm happiest as a guitarist is when I'm playing with other people, and at the same time, those times are usually when I have the least amount of time to worry about the technical things like this.

                       

                      I just know that sometimes seeing all these diagrams and technical discussion can scare people off. I don't want anyone to see these threads and walk away from them thinking that because of them that the HD500 is really difficult to use. I think on it's surface, it's still pretty easy to set up and use. And I think there's a lot of useful info in these threads. But at the end of the day, it's about people getting the tones they want out of the unit.

    • drewfx Just Startin' 53 posts since
      Oct 22, 2008

      I just wanted to add something.

       

      flip the line/amp switch to line, turn the master volume down, and make up the gain that way

       

      As a proposed solution to matching the gain stages, this is inaccurate. The difference between line and amp is the impedance - line is a low impedance signal, and amp is a hi impedance signal. Plugging a low impedance signal into a unit expecting a hi impedance signal is going to cause signal loss, extra noise, and increase chances of ground hum. Adjusting the master volume will not account for this, because the master volume is pre-impedance conversion. You'll be turning up the signal sure, but you'll also be turning up the noise.

       

      You would need a DI box after the output if you wanted to use the line setting, to match the impedances.

       

      As for unity gain - unity gain is a pretty simple concept to understand... the level that goes in is the same as the level that comes out. If it isn't... you don't have unity gain.

       

      In my opinion anyway - don't mean to step on any toes, but I don't think the proposed solution is ideal. The better way to do it would be to get the gain staging correct, which seems like it is impossible as Line 6 don't offer you features to truly account for the -5dB drop off in the effects loop.

      • snhirsch Just Startin' 67 posts since
        Oct 17, 2012
        Currently Being Moderated
        Mar 5, 2013 9:54 AM (in response to drewfx)
        Re: What every POD HD 500 owner *REALLY* needs to know!

        drewfx wrote:

         

        As a proposed solution to matching the gain stages, this is inaccurate. The difference between line and amp is the impedance - line is a low impedance signal, and amp is a hi impedance signal. Plugging a low impedance signal into a unit expecting a hi impedance signal is going to cause signal loss, extra noise, and increase chances of ground hum.

        There is no inherent problem with driving a Hi-Z input from an output with low source impedance. The reverse is not advisable due to the potential for a Lo-Z input to "load down" a high impedance source and cause signal degradation (probably an increase in distortion).  In neither case does the impedance mismatch itself have any direct bearing on the level of hum and noise.  That's more likely to be a function of how the connected devices are grounded, whether or not a balanced line is used between them and the relative gain staging. 

      • meambobbo Iknowathingortwo 1,702 posts since
        Dec 13, 2007
        Currently Being Moderated
        Mar 5, 2013 10:08 AM (in response to drewfx)
        Re: What every POD HD 500 owner *REALLY* needs to know!

        Just use a studio eq before the loop to boost the signal...

        • drewfx Just Startin' 53 posts since
          Oct 22, 2008

          Heya Lore,

           

          I just wrote a whole response, and this bloody forum lost it! Garbage interface was also responsible for me misquoting you. I knew it was Phil I was responding to, but for some reason it didn't quote him properly. Don't know why, sorry about that! Anyway...

           

          All of what I'm about to say could be complete balderdash, but here is my take on it:

           

          The main outs can be switched from Low-Z (Line) to Hi-Z (Amp) using the 1/4" output switch on the top of the unit. Are you saying that this switch doesn't adjust the impedance, and only adjusts the output level?

          Likewise with the FX loop, it has its own Low-Z (Line) or Hi-Z (Stomp) switch. So logically (if these switches do switch the impedance) you'd set them both to the Hi-Z (Amp and Stomp) setting for a 4CM setup with a guitar amp.

           

          Going from Hi-Z to Low-Z will introduce muffling on the high-end (adjusted frequency response) and will also screw with the signal to noise ratio. This is where the extra hiss and hum comes from in that situation.

          Going from Low-Z to Hi-Z should be fine in theory, but not all guitar amps are made equal. The Marshall JVM for instance has a 470kΩ input. The Fryette Sig X has a 1mΩ input. That's a pretty big difference. The PodHD500 has a 1mΩ input impedance too, and AFAIK this wont change when turning the guitar input pad on - although it can be adjusted from within the setup I believe.

           

          I cannot find figures for the output impedances, but it would be easy enough to test with a multi-meter and an exposed patch cable.

           

          Ultimately, as I understand it, there is a difference between output GAIN/LEVEL and output IMPEDANCE. I'd be happy to be shown if I am wrong though.

           

          Quick story: I had a Pod HD500, one of the first ones. At the time I had a Fryette Sig X. No matter what I did, I couldn't get it to stop sucking all my tone - weirdly though, I was losing a ton of low-end, not high-end. Couldn't ever figure it out. Now I use a Marshall Satriani JVM, and I am tempted to try a Pod HD500 out again.

          • snhirsch Just Startin' 67 posts since
            Oct 17, 2012
            Currently Being Moderated
            Mar 5, 2013 2:34 PM (in response to drewfx)
            Re: What every POD HD 500 owner *REALLY* needs to know!

            drewfx wrote:

             

            The main outs can be switched from Low-Z (Line) to Hi-Z (Amp) using the 1/4" output switch on the top of the unit. Are you saying that this switch doesn't adjust the impedance, and only adjusts the output level?

             

            I cannot find figures for the output impedances, but it would be easy enough to test with a multi-meter and an exposed patch cable.

             

            Ultimately, as I understand it, there is a difference between output GAIN/LEVEL and output IMPEDANCE. I'd be happy to be shown if I am wrong though.

             

            Even without knowing the circuit, I will almost guarantee that the Line/Amp switch affects only nominal operating level (and indirectly, gain) but not impedance.  Impedance is not the same as DC resistance and measuring with a multi-meter is not an accurate way to determine it.  For example, it's common to drive an output through a capacitor and this "looks" like an open-circuit (infinite impedance) when checked with an ohm-meter.   You can loosely think of impedance as frequency-dependent resistance.

             

            Gain, level and output impedance are all different concepts that I think are getting confused in this discussion.

            • drewfx Just Startin' 53 posts since
              Oct 22, 2008

              Yeah man, I don't know if it does switch the impedances. I naively assumed it would though, since that is what the labelling implies. Bit naughty of them to label it up like that if they're not switching the impedance though - imho.

               

              Do you have the tube comp as the first effect in the chain, or as the first effect after the FX-Loop?

               

              I may just pick one up and see how it sounds with my JVM410JS - which has a fully serial loop, versus the regular JVM's paralell loop.

            • snhirsch Just Startin' 67 posts since
              Oct 17, 2012

              perapera wrote:

               

              I really don't know if the impedance is changing with the switches, but I think you don't know either: we are just guessing here.

               

              So my guess is: "No, it's just a -12dB pad on the amp or stomp position of the switches", and that's why:

               

              Lore,

               

              If you want to determine the output impedance, here's an easy way to get a ballpark:

               

              - Run a 1Khz. tone through the unit and get a usable level at the output you wish to test.  Make sure it isn't clipping. 

               

              - Measure the level at the output using an AC voltmeter or sound card + software that is known to have a reasonably high input impedance.

               

              - Note the voltage or dB level at the output.

               

              - Connect a 100k pot to the output, with the low side of the pot connected to ground and the wiper to the hot lead.

               

              - Leave the meter connected. Start with the pot all the way "up" (wiper away from ground) and slowly turn it down to decrease the load impedance.

               

              - When the meter indicates 1/2 the original voltage - or -6 dB - relative to where you started, disconnect the pot and measure between the low pin and the wiper with a multi-meter on ohms range.  Make sure the output doesn't start clipping from the decreased load. If it does, start over with a lower initial level.

               

              The value of the pot at the point where level falls 6dB (or 1/2 voltage) will be roughly equivalent to the source impedance of the output at 1Khz.  (yes, it does vary somewhat with frequency).  For a typical op-amp output, the source impedance is likely to be very low.  Audio ICs are generally designed to run into non-terminating or "bridging" loads that are much greater than their actual internal impedance.

               

              One common way to implement things like a "stomp/line" switch is to have it change the negative feedback around the final audio stage that drives the output.  On "stomp", it increases the feedback to reduce the gain of the amp and bring nominal level down to a point that floor pedals are happy with.  You can accomplish the level reduction by putting a pad in front of the output stage, but by leaving the gain "high" you run the risk of introducing noise.