Sorry if I mention possibilities you might have read on other pages or you've already considered, but
1. Are you just running the standalone pod farm plugin?
2. Could your computer have been getting less space on your drive running the software/drivers?
3. Do you have maybe more things running in the background than you once had?
4. Is your usb cable fine?
Just the other day I decided to put a little (10-20 cm or so) usb extension cable between my usb cable and the pc because I was concerned that the constant unplugging of the cable from the back of the ux2 might wear out the metal contacts. I didn't want to plug the cable into the front of the pc because I had read that front usbs can be slower etc., so I needed something which I could reach without having to pull my pc out everyday to disconnect it.
Anyway, things were going fine until I got static etc. when I opened my recording programme. I checked the usb cable connection to the ux2 and suddenly the noise stopped. I am not sure if there is a problem - I think that it might have been that I now wasn't connecting that cable everyday and so it slowly overtime might have been getting pulled slightly and coming slightly loose from the the ux2 and because I now wasn't touching that part anymore, it wasn't getting pushed in.
Concerning other things running, I sometimes go into Task Manager and go to Processes and right click maybe two thirds of them (ones that I know, or have discovered, which are not required at the moment, and click End Process.) If I had a lot of things going on in my recording programme, it would cut in and out because something started running in the background, like a virus checker or upgrade.
Its funny that you usually get some sound but now nothing though.
Does your ux2 output sound if you play something in an audio player like winamp or youtube video, and if so, is this usually fine and not choppy?
Also, concerning meters on ux2 - when you try your guitar or mic in it - you are saying that the meters on the front move back and forth I think.
Could you possibly go into 'Line 6 Audio-Midi Devices' (on mine its in control panel) and select 'Inputs and Recording', and in 'Hardware Meters Show' select 'Output'. Then apply and close, and open podfarm standalone. Now, when you play guitar or talk into mic, are the meters on the ux2 moving? Maybe also try repeating those steps but try 'Send 1-2' and 'Send 3-4' each too (in Hardware Meters Show) and see what happens.
I am not saying this will help with anything, but if the meters are not moving, then it might help determine which general area the problem might be in.
Hulbert, I have had several interfaces and UX2 is by far not the hardest, but I get your point.
I'm responding because just today I had the clicking issue and fixed it. First I noticed it on REAPER tracks, a clicking...randomly.
Then I checked CD, and other mp3 files ....all clicking the same.
I went to the GEarBox HELP and set everything for 16/44.1, because my pc was set for that. I matched all, as suggested.
Then continued to the sound card WINDOWS MIXER and set to 70 not 100, to prevent clipping, kind of centered the VU meters.
Then I went to the GEARBOX LINE 6 the "latency scale" to medium and the data at 16bit /1024.
All was cleaned up.
Checked recordings for latency, checked CD's playing, checked mp3 in RealPlayer etc.....all perfect.
I dont know what all this is about, but the settings I noted down on paper. And also I dont know if all the settings will stay "permanent", which is something to be aware of.
Anlother thing to remember is when recording seriously, all other USB's need to be unplugged, your wireless cards need to be disabled, and all your WINDOWS crap turned OFF....like Updates and BS. When Windows does stuff it steals CPU time causing clicks, on any brand interface.
Also WIndows Updates are famous for messing up USB ports!!!! sometimes changing them and making them inoperable which someone told me about.
Basically dedicate your pc to sound (and off the internet) if wanting pristine , uninterrupted, music streaming....
ADD: some info from Line 6 posts
*Some upgrade a video card and eliminated clicking while running other apps.
* some purchased a USB 2.0 card and clicking stopped.
of course as it says in the FAQ pages, turn off all internet, virus ware, etc..
thanks, just realized Rick325 was having the clicking issues..
i'm learning as I go too and reading a lot, if someone is having same type issues, maybe my inputs will help?
today during recording i again had clicks on playback only, increased my old pc to 2048 and it works smoothly.
as I read it this si common but tracking the size can be greatly reduced.
the audio cards on the Computer, Systems, Device Manager were checked.
the settings all ensured to be the same between the DAW and GearBox
the Playback mode and Record modes were found to both work fine (no delay or double outputs) by muting everything on the Windows Mixer except the main out. (new change).
but on playback from Reaper, a few tracks I heard minor clicking and incrasing the buffer from 1024 to 2048 seemed to work. on the Gearbox setting.
Others have said they too, on various interface brands, have to turn up the buffer size for playbacks and on tracking can lower it .
Is this due to my pc being an old AMD 64 Athalon, Compaq1530? 4gig Ram, 160gig HD.?
Anyway, all has been really working well with small adjustments (learning curve).
Three things I now check each Recording Session-
1) Gearbox Soundcard settings.
2) Windows Mixer/ Device Manager settings and all other stuff turned OFF.
3) Reaper/DAW settings are the same (still learning this new DAW too)
still to read the manual again!
Yes, good points cc51. Also, yes. I am sure others would be very appreciative if you posted how you are working out solutions to problems.
I forgot about the buffer settings.
Rick325, where these settings are, they are in Line 6 Audio-Midi Devices (on my computer this is found in Control Panel) and under ASIO settings and also the bar below called Tonedirect and usb audio streaming. Mine is set at 512 and 24 bit and the bar is all the way to the left. If you haven't tried playing with these, try changing the buffer size in the bar (and maybe the other 2 boxes too. Further right means bit more latency but less cpu pressure.
I think this is the same thing as what cc51 has already said except in a different place. I don't use gearbox, so I only know about the control panel one.
In my DAW (Podium) I also can go into a menu called Midi/Audio Interfaces and select Audio and also can set Podium's default sample rate too to match it.
David, I am wondering what these all are. Do you know?
I think this thread is mentioning the clicking and popps....in addition to No Sound.
No Sound is probably a Mute is on, either in the GearBox/Pod Farm Monitoring or the Windows Mixer/Audio...or rare cance its the USB is bad but that can easily be eliminated by trying other USB's. Of course, Active Monitors are needed, or PAssive speakers with an Amp.
The Clicking and Latency issues are usually only tricky for a initial period until they are setup for the specific computer.
I understand that and have been through numeorus interfaces etc.. once setup, probably pretty solid.
But Latency in the sampling, the depth and the "buffer" is what? I dont full understand.
What is the slider exactly?
What is the slider setting doing? We can go Extra Small or Medium but what is it adjusting specifically? curious.
Also what is the buffer size, 512 common, 1024 or even 2048 for mixing sometimes, what exactly is this number?
Hopefully Rick325 chimes in with his findings.
I'll be back, going to fire it up and see if the last settings held!
add: today no issues at all
When I power up the pc for recording I do the following.
1) Disable/Turn off wireless card in device manager, turn off/disable ethernet card. Disable any soundcard other than the UX2 in Device Manager. Turn off all Virus and Scan softwares that might use CPU .
2) Open ux2 soundcard preferences- 2048/ 24bit or 16bit nochange- Extra Small on slider
3) Open Reaper to record. UX2 selected Auto mode (I guess)
4) Windows Mixer shows 3 Icons, Only my Speakers main Icon is ON, the SYstem SOund and Line 6 is OFF/Muted on Windows Mixer
Now to do numerous tracks and test it alittle harder....
this is a great in depth aritcle -page
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
thanks that was a helpful addition.
that was good stuff, it was what I was wondering....to reiterate the bit depth is for the recording part of it, 16 or 24...hadnt heard of 32.
i put mine back at 24bit and it works fine. but might need to make sure my DAW is at 24bit, I thought i read they need to be the same setup.?
the marbles analogy was good, I knew what LAtency meant delay effect, but now understand it better, the "slider" is the input and Gearbox incoming signal...ok.
and the ASIO part, is some other buffer (still a little foggy) but the larger value allows my playback to work better for all my stuff even the Media Audio ectc..
the ASIO, it seems more tied to the DAW, how does that work? WHat DAW do you use and how exactly does the ASIO work with it?
I found this in a manual-
my results coincide with this too. it doesnt really explain in depth , but it helps set it up!
rick, did you get it going?
you get it going sporadically, that means its probably being reset to a default somehow in your windows...possibly a conflict of your soundcards (do you have your old soundcard disabled?)
the clicking is probably what Hulbert has explained.
check the basic three things first, slider to extra small, 16 or 24 bit depth, and increase the 512 to 1024 or more if possible.
The bit depth and sample rate etc. is for the signal going from the ux2 to the computer and also the computer stuff out to the ux2 then speakers. So, it is both ways. When recording in a daw, it also has a bit depth and sample rate itself, for it to take the sound and record it. I think this is meant to always equal what you have set in the "line 6 audio-midi devices" thing.
The buffer slider I think adjusts the speed of the input and the output. This is for "Tone direct monitoring" - what you are hearing if you use pod farm standalone instead of the plugin in a daw. The daw plugin will be under the governance of the daw's asio own settings. Tone direct bypasses this and uses it's own asio settings and works quicker.
Asio is the "fast" type of drivers for audio things, unlike other types of drivers. I don't know if other drivers 'can' be as fast, but ASIO is normally seen as being fast.
I have looked up the default bit depth/buffer selection boxes, and the default asio bit depth and buffer size is for your daw, like you said. The PodFarm user guide says that it is for using if you are not using standalone podfarm (I would imagine the same for gearbox), and so it just adjusts the speed and quality that your daw works at. If you didn't use standalone, then there might be a time delay, and the buffer can adjust that. I also noticed that in the "Line 6 audio-midi devices" thing, if you turn on your daw while this is open, you will see the daw name appear where it says asio client.
I am 'guessing' that this asio buffer size/bit depth is bypassed when standalone is on. I don't know if these settings affect the tone direct monitoring latency as well. I suppose if the daw is using it's own system, then two things are running. One for daw, one for podfarm/gearbox standalone. Maybe changing this for when both are running could put less strain on the computer, and in turn give standalone a bit more power and speed to play with.
I use Zynewave Podium. It has a selection box for interface and drivers etc. and it allows me to have "asio ux2" set. Mine says "4in, 2 out" I don't know if all daws say this but so it is set for 4 inputs and stereo output.
Concerning the numbers in asio, you must be right. The larger numbers must I think mean bigger 'bags of marbles', therefore taking more time and less computer effort to rush things, and therefore the things running can play smoothly.
We’re sorry to see that you’ve experienced undesired audio performance from your computer system, even while using the improved driver that has worked on numerous Windows systems. Our engineers have not been able to reproduce the issue on our systems. I personally run W7 64 bit on my Dell and have not experienced any problems with any of our interfaces.
As you may know, almost every personal computer is a unique hardware and software environment. If one or more variables, including a given device driver, in the system don’t interact well with the rest of the system, the result can be undesired performance. Thus, we have provided a USB Audio Issues FAQ that describes what configuration variables numerous users have identified as the root cause of their audio issues: