whitejs

I've rarely seen a company just kind of NOT KNOW how to solve an issue like this and seeming NOT HAVE THOUGHT ABOUT IT prior to me brining it up several years ago. Crazy. I called them (Win 7 64-bit) and they said "Well, you can use your own soundcard now, so just have Pod Farm 2 use your soundcard." That was a pitiful answer, because the Line 6 setup gives us such nice low-latency and whatnot. I have to call up the driver in Windows, ask it to make a tone in the device, then the Windows driver starts using it in 48/24. I use it standalone exclusively because ASIO drivers don't work with two devices simultaneously in a DAW and my main ASIO device is a very nice soundcard that handles my audio in Sonar. ASIO devices CAN be used simultaneously by different programs at the same time, so I boot Sonar for recording and boot Pod Farm 2 standalone, then record through the audio outputs of the TonePort instead of by USB. Sure, it's a longer signal path, but I've never noticed any degradation. I DO, though, want it at 48/24, so I have to do the Win 7 driver call-up thing each time to get Pod Farm 2 to use it at the higher rates. What is pitiful is that Amplitube 3 and many other software modelers HAVE THE SETTING IN THEIR SOFTWARE, making is simple as pie to just set to 48/24. Line 6 told me "Oh, we left that to the Windows system to set." Well, sorry, but it doesn't work. So, go to your Windows audio devices and set it there, then tell it to make a tone on the device. It will reset to your desired rate. After you close it, it won't come back that, so remember that.

Pod Farm 2 is no different, it seems, than the other software. They all act as clients to devices. The Line6 control panel does not show Pod Farm as a client under any circumstances, though. It might if I used the UX2 as a sound card, but I don't because I don't want to switch all the time in my DAW, which only supports one ASIO device at a time. When I use my Lynx card as the Pod Farm hardware, it is forced to run at 44/16! I can't change that, and this is what I'm asking Line6 to fix. Make Pod Farm 2 do what every other software does: act as an ASIO client that demands settings from the driver -- settings that are created in Pod Farm 2 just like EVERY OTHER modeling program. Also, when I use the Lynx as hardware for recording in Sonar, I'm forced to use Pod Farm and Amplitube 3 as plugins, requiring direct channel monitoring to hear the processed sound, and having to reamp to hear it in playback (that is, it never records the processed sound, and requires the amp model at all times to hear the desired sound). I simply want Pod Farm to set the ASIO parameters in standalone. It is a wish list item. By the way, thank you very much for responding so carefully to my post. I appreciate that. Jon

Yes, the techs at Line6 suggested the same. My question is this: How do I achieve low latency recording through any interface other than the TonePort? I've tried it. I'm one of those players that can't deal with 10ms of latency in live recording of my guitars and bass. It just sucks. So I record analog via the TonePort. I tried using Pod Farm 2 with the Lynx and it was a mess. Any suggestions on setup and settings? And if it means active channel monitoring in Sonar, forget it. Too much lag.

Let's just start simple. I just boot the Line 6 Audio-Midi Device Manager with no other ASIO devices active. When I boot Amplitube 3 or TH2 or any other amp modeling program, the Device Manager activates them as an ASIO Client, plain and simple and expected (and per the setup schemes in the respective programs). When I boot Pod Farm 2, it makes no such impression on the Device Manager. It says "Inactive", and therefore has no command that tells it to run in any mode in particular. THAT is the core of my question. Why can't Pod Farm 2 tell the Tone Port to run in a certain mode, if all the others can? And another interesting thing is, when I'm in Sonar, using the Lynx card to record my Tone Port's analog outputs, and I have any of the other modeling programs going, the ASIO Client shows that software and the res and bitrate are set accordingly. So it seems that Pod Farm 2 is the only modeling software I have that doesn't control the Tone Port driver -- it's own product line's driver! I'm stuck at 44/16. That seems very short-sighted and limited.

I find the UX2 indispensable for live and recording work, although I may use it a bit differently than many. I use it "live" all the time. That is, I use the standalone Pod Farm (and other modelers) and send the UX2 output to the mixer. I record this way, too, because I can't use two ASIO devices at a time, and prefer my Lynx card to the TonePort as a Windows soundcard. SO, I want the best analog quality at the outputs. That means, I want 24-bit/48KHz action going on in the UX2 drivers. I want that spec creating my final analog output from the UX2. Even if I'm just jamming in my studio, I want the TonePort to be at its highest digital depth and resolution. But the Pod Farm software does not "tell" the UX2 driver that it is present. All my other modelers (Mark Studio 2, Amplitube 3, etc.) directly identify themselves as ASIO control clients for the UX2 driver. It says so in the control panel the minute you fire up other modelers. It says "ASIO Client: Amplitube 3.exe" and such. And their settings (set in their software, unlike Pod Farm 2!) tell the driver to go to 24/48K. It's that simple. When you close the software, the "Driver Operating at:" line says "inactive". When you load Pod Farm 2, it goes to 16/44K, and no ASIO client is identified. Line 6, can you fix this, please? I mic my upright bass and have found the perfect models in Pod Farm 2, but it doesn't control the ASIO settings in its own-brand UX2 driver! That's crazy. Please put a setting in the Pod Farm software that controls the driver as an ASIO client like the other softwares do. Jon

I'm sending the Aux out of the mixer to my DAW via my Lynx Audio card inputs. All analog, mainly because ASIO doesn't let you use two devices at once, so I record from the UX2 just like its a preamp going into a mixer. I just want it to do its thing at higher res and deeper bits. The Line 6 software settings used to include this setting, but now it delegates it to Windows. Well, I don't even need the UX to be a Windows device -- just need it to model for me and give me the sounds out of its analog outs. So, if I name the UX2 as a Windows device, I can tell it to be 48/24, but it won't go to that until a Windows app tries to use it. When Gearbox or Pod Farm open, it does not change. They aren't using it as a Windows "speaker", which is what it configures as when enabled as a sound device. Only things using it as the Win soundcard will trigger it up. Talked to tech support about this, but the guy didn't know about this in detail at all. Very disappointing. I really like the UX as my guitar interface. He offered me Pod Farm 2, very generously, and said I could use my main soundcard (lovely Lynx 2) and leave the UX2 out of things. Hmmmm. Essentially what this says, to all our 2013 readers, and to anyone thinking of buying a Line 6 device to play models through: It only supports 44/16 operation unless you use it as a PLUGIN device in a DAW. If it is your Windows soundcard, things like Media Player and whatnot will send it up to 48/24 if you set it for that. But on its own, just using Pod Farm or Gearbox, there is no way to make it work at anything higher than standard CD-quality bit depth and sampling rate. That, I'll say, is way behind the times.

Thanks for taking the time for my query, Trir. Still, though, since the modeling is applied to the guitar signal, I would think that A/D and then D/A conversion is taking place, and I wonder if it actually does matter because of this. The guitar signal gets sent to the computer for processing in the digital realm, then gets sent back to end up in the analog outs. See what I mean?

Hi all, I simply want my UX2 to run in 48KHz/24-bit mode all the time in standalone mode. I don't use it as a VST ever; I just call up Pod Farm and play it into a mixer and route that to recording gear. Since some number of drivers ago, there is no longer a Line 6 configuration setting for sampling rate and bit depth -- you have to use the Windows 7 (my OS) setting under sounds in the Control Panel. Well, that is settable and all, but setting it there doesn't make it change to that. IT ONLY CHANGES ONCE YOU "TEST" THE DEVICE in that same Windows Sound control panel. After you leave Pod Farm or Gearbox and come back, it is right back at 44/16. Why is this? Why did they do that? Why can't it be set within Line 6 setup software to just stay at what we want it to? Any help would be great. I'm not going to go to the control panel and test it every time to make it trigger up to 48/24. It just seems odd. I don't even need the UX2 to be a Windows device at all, actually. It works fine (although at the lower settings) when disabled. I only need Line 6 modeling software to drive it, not any Windows apps. ???? Best to all, Jon