CC51,

   Ok, the latency refers to the 'time period it takes between hitting the string of your guitar, and the sound actually coming out of your speakers'. I used to use a different guitar processing thing on my computer and back then "live" playing just didn't work (at least not on my computer at the time). You would strike a string and there was a big gap before the amplified sound would be heard. The Line 6 tone direct system somehow kind of works independantly of the DAW's "latency", and it speeds up the gap tremendously. If you play straight into your daw with the plugin alone on (not standalone podfarm), you might experience the 'latency' problem.

The slider is a thing that can on a scale, decrease computer cpu effort, but this means more "time delay" (latency) being heard. If the slider goes the other way, it increases cpu effort, and shortens the time delay heard. In my view, for my own comfort, I want as little latency as possible. I used to think that the faster you made it the less quality signal (as I think this was the case with  the other software I mentioned), but I don't think that that is what is happening. Someone can correct me on that, but I think it basically just makes the chunks of digital info into smaller groups, but you get them being sent in quicker time, a bit like this example:

Say you had two bags and you spent time filling them up with marbles and you threw the bags individually into a running river.

Now, say you had the same marbles but you divided them into three bags (and because the bags needed less, it didn't take as long to fill each bag before you could throw them),  and you threw them in faster than you did before.

All of the marbles are going to be in the river just as they equally would be if you put the marbles into two bags, but with the extra effort of the bag packager and thrower (computer cpu), you are getting some marbles running down the river quicker than if you waited to fill two bigger bags.

The "buffer size" I think refers to the amount of marbles in each bag (the number might go the other way - I am not sure, but I think I am right). The less marbles, the quicker the sound. The more marbles, the slower it is.

The speed vs cpu effort thing is different for eveyone. I think Line 6 recommend a certain thing (I don't remember if it is what I have i.e. 512, but I haven't changed it since I got my ux2, so I am happy with it at the moment. Maybe in the future I'll play around with it.

The bit depth is to do with the amount of info the computer records (or samples) in each chunk.

So, pretend that you are scanning a picture on a scanner and you are deciding what resolution to make the scan. Lets say it gave you the option of 4 dotsto make up the whole picture (not each little section). The picture would be unrecognisable. Say you chose 100 dots. The picture might be getting recognisable. You might get to a stage where you don't see any difference at all until you zoom right in.

People who can't 'let things go', (I've been there) might always feel a nagging in them saying "if only I could get more dots......", Doing this, you are never going to be satisfied because you can always feel you want more.

16 bit is what cds are done in I believe, but I think lots of studios like 32 bit or even higher for recording and then they mix it down to 16 later. It just supposedly works better for recording (more manageable). Again, some people hear differences, others don't.

I am not 100% sure about podfarm/ux2 and 32 bits as I have read that it is 24 bit tops and yet it has a 32 bit setting in the box. Anyway, I have my daw at 24 bit ( I think it still does its' work in 32 bit somehow anyway) and 48000hz.

If you knew this already, forgive me. I had to look up bit depth again just to make sure I was on the right track

David