Pod Farm 2.5 not working correctly, models missing
by woodhenge on 2011-05-17 22:22:39

I've used Pod Farm Platinum and Pod Farm 2 Platinum on my Mac workstation with no issues ever until I installed Pod Farm 2.5... now all hell has broken loose. When recalling songs with either Pod Farm 1 or 2 loaded, cabinet models are missing, reverbs don't work, preamp models have no effect on the audio, etc. VERY frustrating! I've uninstalled all of my Line 6 software and re-installed everything a couple of times now, and the 2.5 installation breaks things every time. I've managed to revert back to 2.01 and I'm staying there for a while, 'cause at least it actually works! I really had my hopes up for using this in 64-bit mode in Logic, too...

Is this a known issue? Anybody else having these troubles? Surely this can't be an isolated problem...

I'm running Pod Farm 1 and 2 Platinum, which require an iLok liscense to authorize. It includes all the model packs by default, which is why I'm so ticked about this update messing up both my Pod Farm 1 and Pod Farm 2 plug-ins. If I look at the info screen in the plug-in, it shows that it sees my iLok and that all model packs are enabled. I think there is a serious issue with the 2.5 version... judging by how many posts have popped up in the last day, I'd say I'm not the only one.

Well it HAS only been out for a day. I found a few bugs myself, I'd like to get my Power Pack back, but since I only need to plug in my hardware to get it back it's not that big of a deal for me. Sounds like your issue is a little worse though. Have you tried going into the License manager and authorizing the computer itself? I wonder if it will work that way.

I'd like to be able to move from one machine to another and mix the same songs without needing to swap the hardware around all the time.

I tried authorizing the computer, but it didn't make any difference whatsoever. The weird thing is that everything shows up in the GUI as usual, but certain modules don't do anything to the audio. The API eq module is a good example of this... or the 412 greenback cab model. Stuff that worked perfectly fine before.

Even scarier, once I did the 2.5 update, Pod Farm 1 started behaving this way also. I had to completely uninstall everything and reinstall... I stopped at Pod Farm 2.02 the last round and everything is back up and running on my system now. I just hope they get this figured out soon!

Since you're on Leopard, that tells me it's not a problem limited to Snow Leopard. (I'm running 10.6.7 here)

Hopefully a Line 6 guy will chime in on this soon. Fortunately, I have a meeting with the midwest rep tomorrow morning and I'll hit him up about it. I know he won't be able to fix it, but he can definitely put me in touch with someone who might have more insight to this issue.

I wish I could help above, but thought I would write my experience with upgrade and ask for help too.

The license manager does not recognize the pod hd500. Also, the pod500 cannot control the pod farm from what I can see. It would be nice if it could with midi assignments. Any help would be appreciated on the HD500.

Just to clarify, I'm using the Pod Farm 2.5 Platinum iLok version. I also own a PodXT Pro and PodXT Live fully-loaded with all the model packs, but I'm not connecting any of those to my system to enable the plug-in model packs.

The info screen in the plug-in shows that my iLok is recognized and that all model packs are enabled. They're just not functional...

Installing 2.5 also killed the functionality of Pod Farm 1 Platinum iLok version, with the same lack of functionality. Uninstalling and reverting back to older versions was the only way to make my plug-ins work correctly again (versions 1.12 and 2.02 work fine until 2.5 is re-installed, then it's all toast again.)

I don't mind the other issues on this thread, but I don't want to have my problem get lost in the shuffle. Thanks, guys! Hopefully we'll all get some helpful news today.

Woodhenge, I have exactly the same problem. Version 2.02 (for iLok) worked properly, but when I updated to 2.5 it brings this crappy bug with bypassed cabs and other messed things. I tend to switch back to 2.02 unless guys from Line6 will release patch in next 2 days.

I tried running 2.5 standalone and it totally freaked out my Mac Pro... the program hung when I tried to quit it and caused a HUGE squeal out of the internal speaker (?!?!?!?!). Sounded like a UPS alarm through the loudest megaphone you've ever heard! Surely, that can't be good...

I had to force-quit it for the noise to stop... My wife ran in 'cause she thought I'd set off the fire detector somehow. (Wouldn't have been the first time... lol!)

I have similar issues with my update. I'm running Win7 64bit using a Focusrite Sapphire Pro 24 DSP as my interface with Cakewalk Sonar X1 Pro as my DAW.

I've been using Pod Farm 2 since its release with no issues. I ran the iLok update using the default installation directory, deselected RTAS and redirected the VST plugs to my primary VST directory.

In standalone mode the default patch works, but most of the effects do not. Changing the amp model in the default patch makes little difference, ie, changing the model to say the AC30 will change the graphic but the tone still sounds like the Marshall 800. Very strange. No user patches work, either factory patches or ones I have written in V2. I have the audio hardware configured correctly in preferences, and I am hitting the in and out led's, but with anything but the default patch, basically it is a direct sound. No amps or FX have any effect.

As a VST plug in Sonar I'm having pretty much the same results. Nothing but the default patch works. Some of the Elements will work in an insert, but it is very random. And to make things worse, my 2.0 32bit VST effects now exhibit the same issues.

Basically my entire Pod Farm setup is broken.

I reinstalled the 2.5 update with no change. I've been doing computer based recording for over 15 years so I've gotten very good and troubleshooting installation and configuration issues, but I've hit the wall on this one.

I am tempted to completely uninstall Pod Farm and get my self back to a wiorking version of 2.0 but I am holding out for a possible solution here on the boards.

In scanning through all of the 2.5 posts from the last two days I am seeing a whole, whole lot of people with issues. Hopefully the Line6 support crew will come up with some solutions. I use the Pod Farm plug on a daily basis in my studio and think it is an excellent piece of software. I hope we see a fix in the not too distant future.

Sounds eerily similar to what I'm seeing as well. I wonder if the iLok authorization is screwed up in 2.5? That would explain a lot of things... like why installing 2.5 messed up my PF1Plat install as well (doing the same goofy crap as 2.5). If it's messed up on both Mac and Windows...

Yeah, I was looking for a way to do the support ticket, but I can't find a link to do it anywhere. I'd imagine they're aware of this thread, though, seeing how it has about a trillion views now. Hopefully somebody from Line 6 will let us know whats up soon... or at least that they're aware of the problem(s).

After uninstalled all of the versions of POD Farm from your computer, which versions did you reinstall? Did you install 2.02 and 2.50? If so, please try uninstalling all version except 2.50 and please let us know your results.

Please provide as much information about error codes or steps taken to encounter them as well, it is much appreciated.

I'm having the same problem and I also can't even revert to Pod Farm 2.02 I have a Pod XT, POD X3 Live and I have Podfarm Platinum on iLok Key, can someone please help me, I wish I never updated it!!!!

I just uninstalled absolutely everything from Pod Farm 1.12 and Pod Farm 2.02 and ran the Pod Farm 2.5 installer. I chose to customize the install, installing only the AU plug-ins and the stand-alone application. Upon opening a previous project in Logic, I'm still having the same issues...

The modules I'm using in the Pod Farm 2.5 plug-in in this particular session are the tube drive pedal (works fine), the Double Verb amp model (front-end of amp works, but the cabinet and mic models are completely non-functional even though they appear visually to be normal), the American Classic mic pre module (appears normal but the controls have no impact in the sound whatsoever), Standard Spring reverb model (again, visually appears ok, but there's no reverb happening), and the Compressor model (again, does absolutely nothing audible to the signal.) All the ineffective modules sound like they're bypassed, even though they're not. (This same preset works perfectly when I have 2.02 installed)

Other presets behave similarly erratic as well.

Another thing that's REALLY bugging me is that when the Pod Farm 2.5 plug-in window is selected, I can no longer use my spacebar to start or stop playback in Logic... definitely ANNOYING!!!

I've attached a screenshot of the "about" page of the plug-in, clearly showing that the iLok is recognized and that all model packs are enabled.

I've never had any error messages pop up at any time, so I can't help much there...

I've been poking around a bit and am curious about something. Are there any other files that get installed besides the plug-ins themselves and the stand-alone application? The reason why I ask this is because when I removed the 2.5 plug-ins and moved the 2.02 plug-ins back into the "components" folder, 2.02 was behaving as erratically as 2.5 does (as does Pod Farm 1). Is there an underlying framework that's installed in the Mac OS somewhere? If there is, and if I were a betting man, it would make sense that that's what's causing this issue. If I could remove the framework (or whatever) from 2.02 and do a fresh install of 2.5, we could be on to something...

The only thing that returns functionality to 2.02 is to trash the 2.5 plug-ins and stand-alone application and re-install 2.02 from the installer. Very interesting...

This is such an abomination of a bug, its like this is some type of beta test joke. I just wasted 2 hours trying to debug the crap that is being called an update. If its not ready for prime time, don't release it and subject your loyal user base to this type of unnecessary torture

I hear you... Imagine my horror when I opened up one of my client's projects tuesday night (after installing 2.5 earlier that day) and had to explain why their guitar tracks sounded so jacked up. I'm usually fearless with updates, but this has definitely made me think twice before I jump on one!

Yes it does suck that people are having problems, but realistically I was quite happy with the older 2.02 version of Pod Farm. I just got really excited because 2.5 is 64-bit, which means one less 32-bit plug-in I have to run through the 32-bit bridge in Logic. (A necessary evil, but kind of a PITA, too.)

Getting ticked at Line 6 doesn't help solve the problem, though. Personally, my hat goes off to the software developers... seems to me like that would be a pretty tough gig. Nobody is perfect...

No official word yet... Don from Line 6 didn't reply to this thread until yesterday. I'm sure they're trying to re-create the problem...

After some experimentation last night, I'm curious if people who aren't doing upgrades from 2.0x to 2.5 are having the same issues with the iLok version as I am. Personally, I'd like to see it fixed, but I sure as hell don't want them to do a "quick fix" that may cause other serious issues elsewhere. My DAW's functionality is my lifeline and major source of income, so it has to be rock-solid.

I'll bring everyone up to speed as to where I am with the 2.5 update issue. My installation is the iLok version, no Line6 hardware, on a Win7 64bit system. I have tried all of the suggestions here on the board with no luck. I moved all of the 32bit .dlls, reinstalled the update, and downloaded and installed and ran the updated License manager. Still I can get nothing to run in Pod Farm other than the default patch. This is both in standalone mode and as a VST plug. None of my projects in Sonar X1 using Pod Farm are working properly. Pulling up a project using Pod Fram v2 sound basically as if the plug is bypassed. The odd thing is that some of the effects are working, say a phase shifter , but most effects do not work and the amp and cab sims sound as if they are bypassed.

I am now going to completely uninstall Pod Farm and reisnstall to get myself back to a working v2.

The is a real shame. I installed the update without reading any users' reviews here. For other products, that is something I would never do, but I have had such good luck wih all updates coming from Line6 that I installed it without research. (In addition to Pod Farm I use the M13 FX board and an older POD)

Hopefully we will have a fix in the next few days. I was really excited about having a standalone version and being able to run the plug @ 64bit. But for now I have to get my projects stable and be able to get back to where I was before the update.

I'm running Win7 64bit system too, so i would have benfitted from that update very well. I'm sure they will sort it soon, there can't be just us in this forum talking about how it's all gone wrong, all will be well soon me thinks.

I've done some deep hacking and finally got the 2.5 plug-in to work correctly but with a few major catches... I'll share the fix, er... kind of fix... with you to try. WARNING: If you don't know your way around the Library folder on OS X, don't try this!! You can seriously jack up your system if you foul up in the Library.

Make sure you're on an administrator account. You'll have to enter your password a bunch of times doing this, too.

Also, I'll tell you this in advance... one of the catches is that with this fix, 2.5 WILL NOT WORK IN A 64-BIT DAW! The plug-in will fail to load, or may completely crash the DAW if you're using 64-bit mode. (Personally, that's almost a complete show-stopper for me right there... I have to use 64-bit mode due to the intensity of some projects I do. If you only use 32-bit mode, you should be safe... er something...)

Ok... here's what I did to get this puppy to work:

First, make sure you've installed 2.02 on your machine from the actual installer. We need to snag the resource files from this install. (I also have Pod Farm 1 loaded, so I'm snagging those in this, too...)

Open the Library folder on your boot disk. (NOT the one in your home folder!) Open the "Application Support" folder and drag the "Line 6" folder to the desktop.

Go back to the Library, and open the "Audio" folder. Open the "Plug-ins" folder. Open "Components". Select all the files that say POD and drag them to the desktop. (Putting them all in a folder is a good idea...) If you use other formats of plug-ins, do the same in the respective folders until you get 'em all.

Again, back to the 'ol Library, and open the "Frameworks" folder. Grab the "L6TWXG.framework" and "L6TWXY.framework" folders and drag 'em to the desktop.

Back to the Library (or, Liburry, if you're Sean Connery... lol!) and open "LaunchDaemons". Drag "com.line6.l6ksettingmgr.plist" to the desktop.

Now, run the 2.5 installer. I chose a custom install, only installing the plug-ins and nothing else because that's all I use, so I haven't tested the stand alone mode. I'd imagine it'd work, though...

After 2.5 is installed, go back to Library>Audio>Plug-Ins>Components and drag "PODFarm.component" back in from your desktop if you had Pod Farm 1 installed. (Obviously, repeat this for the other plug-in formats if you need them, too. Just don't drag in PF2 or any of the elements.)

Now, drag all the stuff on the desktop you grabbed (EXCEPT for the plug-ins) and put them back into their respective original folder locations in the Library.

Take a deep breath, and fire up your DAW. Try a session and let me know what happens...

Oh, yeah, I have a couple of screen shots of what the version numbers look like on the way that works vs. the way that doesn't, too.

Also, I'm happy to report that this hack allows the spacebar to start and stop playback in my DAW again when the Pod Farm 2.5 plug-in window is selected!!! Fantastic!!! That alone was worth all this effort!!!!!

I just want to say good luck... we're all counting on you. Lol!

PS- Sorry, Windows guys... I wish I had a fix for you. And I don't mean that in an Eddie Haskel sort of way, either.

The same thing is happening to me, this is really frustrating. Even more so that I when I uninstall 2.5 and install 2.02 I get the same problems. Looks like pod farm is not useable for me untill they fix this bug.

I completely uninstalled Pod Farm and did a reinstall with the 2.02 update. Everything is back working. I'll wait until Line6 gets 2.5 straightened out before attempting that update again. I'm just glad to have the app back in working order.

For those that have models missing it's probably because when you have eg. the POD XT Live connected it included the FX junkie and the Power pack are part of the onboard ROM and are therefore connected to your hardware.

When using POD Farm as a plugin with out the POD connected you can't access any sounds from those particular packs.

It's a shame they don't offer us a discount on buying the 2 packs involved but I'm not paying another $100 for 2 packs that I paid for with my hardware.

Sorry about that. By the time I got through 3 pages all I could remember was that some programs wouldn't work so my answer was tailored to what became the commonly presented problem which unfortunately was not your problem connected with having the Platinum Pack on a Mac.

In that case I don't have an answer for you. all the best with getting a solution.

Nothing to be sorry about... I just wanted to clarify in case you'd hoped to find answers for your specific problem on this thread.

Actually, I think I'm on to something and posted a lengthy way for Mac users to have a work-around until Line 6 can do a proper correction and issue an update. I just hope my hacking can lead them to the core of the problem.

How do I do a complete uninstall. I do the driver uninstall and then drop the line 6 pod farm, monkey and liscense manager into an application called "appdelete" and when I install the older pod farm, the GUI is all messed up and it wont process anything.

If you're using a Mac, the files you need to remove to do a full uninstall are in the Library folder. (I've pointed them out in post #34, above.) If you pull all of them and re-install 2.02 (From the installer), it should work without issue. (Save them, just in case, though!)

Unfortunately, I don't know the method on Windows. Maybe someone else can chime in on how to do it?

When I remove my ilok with the platinium licence on, I've only what seems to be the basic free podfarm models, my computer authorized model packs (Metal+classic that I get previously for my Pod XT Live) but the bug seems to disappear.

Again, this is a thread about problems with Pod Farm 2.5 Platinum iLok version. No hardware is required for this version; the problems we're having are quite different than the more common "no audio/no input" issue. That work-around has been posted on numerous threads elsewhere in this forum, but won't fix things in our particular situation. Thanks anyway, though... I appreciate it!

If you're on a Mac, the easiest way to roll back to an older version is to restore the "Library" files I mentioned in post #34 from a Time Machine backup... has worked every time for me without a hitch whatsoever.

You DO back up your system, don't you? If you don't, maybe it's time to start... My system is my lifeline for income, so I keep at least 3 current backups of my boot drive at all times. (2 clones and 1 Time Machine backup)

If you restore the Library files from a backup from before last tuesday, you won't touch any of your DAW session data. Just highlight each Library file from the archive and click "restore". (I'm not suggesting rolling back the whole machine, if that's what you were thinking.) This method has saved my bacon quite a few times, actually.

I also had some weirdness trying to re-install from the 2.02 installer after deleting things... mostly graphics issues. However, I was able to restore 2.03 though from the archive and it's all rock-solid again... no hiccups in any current sessions. It's like my Mac never knew 2.5 existed.

Yeah, when I tried to re-install 2.05 that is what happend to me as well. Major graphics issues. I think i'm going to wait for them to do an update, which really stinks because it's putting me and my clients on hold. We will have to use something like guitar rig untill everything is situated.

Wow... the lack of response from Line 6 is becoming extremely disturbing. This thread has been going for a week now, and we still haven't heard any official word on this issue! I'm a very patient person, but for only so long...

I work as an audio tech support guy during the daytime (For a Line 6 dealer, too!!!) and have received numerous phone calls about this update. It really disappoints me to have to tell customers, "Sorry, be patient... no official word yet.... not sure what the details are... they're working on it...." They're getting sick of hearing it at this point. They just want their bricked software to work correctly, and I can't say that I blame them. After all, I'm a customer, too....

You know , I've got quite a bit of cash rapped up in Line 6 stuff such as: HD147 "Double" stack oh about $3800.00 there , I own the Line 6 UX8 w/Podfarm Platinum 2.2 Oh $400.00 there , A PODXT Live that was oh $500.00 there , So basically almost and or $5000.00 in equipment from this company that wont answer knowone back on an issue that's crippling your meens of making money at a mistake that they've made ... Hmm Makes me think about whether in the future i'll want to purchase anything from them anymore . Now "Thankfully" you've posted this thread and i did the research on this damn 2.5 update , I haven't experienced the downfall of it. But already not liking the turn there head attitude that seems to be happening . I'm just a concerned customer of Line 6 that hopefully when i need help, They wont turn there back on me . Hope they help and fix the problem soon for you dude. We can't afford to wait and play games these days ...

wow, i was about to upgrade from pod farm 1 to 2 platinum and im keeping my $, this is too scary, i can't make my clients wait knowing i use pod farm for all my guitar sounds. The worst of all is that line 6 don't show up to keep their clients up to date of their work to fix this BIG problem.

Seems like they are no longer replying to any of the threads about 2.5, despite continuing to answer other questions. In fact, they're recommending other people download 2.5 to fix problems on 2.0x. Would be nice to see some acknowledgement that it's at least being worked on.

I'd be happy to know that they actually were doing SOMETHING, even if they don't know what the problem is yet! Just admitting that they know something is wrong would be enough for me, but that's not even happening.

My guess is they are freaking out because this is their first product which doesn't require hardware/iLok authorization, and within days a crack was up on BitTorrent. Who knows if it actually works. Personally, and besides the obvious moral issue, I can't risk running some hackers' code on my studio laptop with clients' projects on it. (I back up regularly, but still)

Anyway, they might be worried they are providing support to those who stole the program, which of course sucks for those of us who doled out the $ and aren't getting any help.

Thank you for for provided us with screen shots. Corruption of the graphics in POD Farm is related to having duplicate plugin files installed within your DAW folder, or having the audio units plugins installed to custom file locations. To fix this, you need to make sure reinstall POD Farm 2.02 or 2.50 in the default location.

To uninstall POD Farm completely from your computer please do the following:

-Back up your tones files into a safe folder on your desktop or other neutral location.

-Place all versions of POD Farm into the trash.

-In addition remove the Line 6 Folder from Username/library/application support.

-Remove the line 6 folder located at HD/Library/Application support as well.

-Run a spotlight search for pod farm to find any of the left over Audio units files if there are any and delete those as well.

-Empty the trash.

-Open the disc utility, located within your utilities folder and repair the disc permissions for your primary hard drive.

I thought about trying that, but there are a few threads on this board about users losing their model packs out of their hardware with this update, so I'm not gonna risk that one. The whole point of me buying Platinum in the first place was to get away from having to hook up any hardware to my DAW to authorize the plug-in. I'll stick on the old version that's working until I know the smoke has cleared... if I even bother updating at all.

I totally agree... this is seriously wrecking the chances of me buying a DT-50 head and a Pod HD500 at this point... and this is coming from a guy who's considered a Line 6 Fanboy by all my friends.

The cool thing about this ordeal is that it's forced me to get my old Boogie out and lay down some tracks with that setup. Man, does that thing sound awesome! A triple-rec, a greenback cab, and a Royer 121... how can you go wrong? Not as convenient as Pod Farm, but at this point I really am not caring anymore... I have music to track and deadlines to meet.

I thought about trying that, but there are a few threads on this board about users losing their model packs out of their hardware with this update, so I'm not gonna risk that one. The whole point of me buying Platinum in the first place was to get away from having to hook up any hardware to my DAW to authorize the plug-in. I'll stick on the old version that's working until I know the smoke has cleared... if I even bother updating at all.

Yikes. I said I wasn't going to diagnose - but now I'm curious after reading the titles of the last 5 pages of posts.

So while I don't want to install it - I have a few thoughts/questions.

According to monkey - the licence manager does the authorizations.

I had the UX1 plugged in but the X3 turned off. It saw a couple of model packs on the UX1 and a button to authorize my PC. That's all.

Now if I had opened Cubase and inserted the Pod Farm Vst to make it communicate with my iLok - would the licence manager then see it and authorize it?

If model packs are missing on hardware devices - is that because 2.5 has disabled other forms of authorization and therefore addons like the power pack are then not authorized if the licence manager is screwy and therefore disappear?

In my case, I only have an iLok license for Platinum, and possibly if I hook up one of my Pod Xt's (They both have all the model packs loaded on them). I tried to authorize my computer, but it said I needed to buy a license for 2.5 even though I own 2 copies of the model packs, and authorized computer, and a Platinum license. It's really not too clear as to which will override the others.

One thing is for sure... the folks using L6 hardware as their authorization method got off easy with their problems compared to us iLok users. Seems like the guys with the computer authorization aren't too bad off, either... Lucky me/us!

I am having the "no input" issue after installing the new drivers and Pod Farm 2.5 yesterday. You mention that the fix for that is posted elsewhere on the Forum, but for the life of me I can't find anything about it. I have dealines to meet and would appreciate it if you could possibly point me in the right direction. I need to get this resolved asap and it sounds like there's a fix available if I can just find it!

The fix that covers the "no input/no device found" issue is posted earlier (#48) in this thread. Note: this only applies if you're using Line 6 input hardware. Here's a copy of the post:

**********************************************************

To regain inputs in POD Farm 2.5 please try the following:

-Launch POD Farm 2.5 with your UX1 connected to your USB port.

-After the program launches, disconnect the USB cable from the UX1 for about 5 seconds.

-Replug the USB cable into the UX1.

-Open the preferences menu from the file menu.

-Reselect your UX1 and click apply.

-You should then see the Inputs tab appear and now receive sound.

**********************************************************

This is the only official fix so far, but does not apply to those of us in this thread... there is no fix for iLok users except rolling back to an older version of Pod Farm and waiting for Line 6 to issue 2.51. I did post a way to hack 2.5 on a Mac and get it to work, but it's more trouble than it's worth, as functionality is limited and it's fairly unstable.

Good to know someone responded! As long as they're working on something, I'm cool... but they still should communicate with us more on this forum, ya know? Especially when this is the main avenue they use for tech support.

One thing I've learned about Line 6 from my day job is that it takes a little while to make things happen with them... any warranty issues go through a few different people before it finally gets to the right guy, so I'm sure our situation is similar. (They're not the only well-known company that works this way, either...)

Either way, I'll be patient... and I don't think I'm gonna take a sledgehammer to any of my Line 6 gear just yet.

Sorry for the delay in a response, as you can see I have been trying to help as many people as possible with this issue, all the while collecting error information as we go. It took us some time to process the information received as well. Thank you for your patience and understanding.

An update should be supplied sometime this week, sorry for the inconvenience. Please refer to the document below for information on current issues and workarounds:

1. On one machine the workaround for windows works. It survived reboots and application restarts. Running 2.5.

2. On another machine the workaround worked once but did not survive after a reboot. I could never get the workaround to work with my GX after the first time.I had to revert to using podfarm 2.02 so I could have something. Fortunately for me I don't need to have the need for what was in 2.5 as of yet.

How can LINE 6 not test there upgrades before they release them? I have only had problem since day one with this product. It all started with my serial-key that was already in use!!!! And it took 2 weeks for the lightspeed-support of Line 6 to got it to work... NOW THIS!!! Now i use Amp designer in Logic and it works great without problems. With a little tweaking it is just as good.

LINE 6 should compensate their customers in some way.... And get a better support

I know that Ableton has a reputation for crashing a lot, but my experience with it has been very stable. That is until I installed Pod Farm 2.5. I really hope that this is one of the issues that will be fixed with the update.

I'ts been almost a month since I upgraded to pod farm 2.5 and no REAL SOLUTION has been instated! This company is loosing all credibility! Can't believe they come out with a product that doesn't work and then a month after..... No solution!!

Yes whats going on didn't they test this product before release :its almost completely unusuable. Standalone does not work and its just messed up my previous version of the product. I have posted some discussions on the matter but Line 6 dont seem to want to respond. I believe that it could be Driver related since my standalone version simply states that Drivers are inactive. I sometimes get the same response in the Driver Panel with POD Hd300 using these new drivers.

Please keep in mind that there are some users who aren't having major issues with this software like those of us on this thread... therein lies the problem. If it was broken for absolutely everyone, it would be way easier to nail down the issues from a troulbleshooting standpoint. But, that's not the case...

This is another good reason to reinforce the notion of keeping an accurate backup of your data... you guys DO back up your drives, don't you? If not, you should start TODAY, RIGHT NOW...

Yes I agree they should stop marketing the product immediately and withdraw it before some other mugs go and buy it or be prepared to get the issues fixed post haste. O really belive that its a driver issue. These drivers dont seem to agree with HD300 either. Maybe its the drivers that become bundled with the software or something. I might try downloading the drivers separately to see what happens but its all very time consuming and frustrating. Or its just something to do with people who have bought add ons or something.

I wish I would have seen this forum before buying Pod Farm 2.5 as I would have passed on it. I am having the same issues as everyone else. I didn't upgrade as this is the first piece of Line 6 software I have used so I can tell you that these errors are not an upgrade issue since mine was a clean install.

I did try Woodhenge's fix and it didn't work for me. The only part of 2.5 that is working is the tuner and regardless of which plugin I use I am still getting the raw unprocessed guitar track. I have tried it in the stand alone mode and as a plugin. On the plugin side, I am using it in Logic 9 in both 64 bit and 32 bit and I get nothing. When I tried the standalone Pod Farm hung and then also gave me the loud squeal. I find it really hard to believe that Line 6 would keep their product availible for download when it is clearly not working.

I also tried the fix. Although I did then get the inputs back the sound was awful full of pops and hiccups. Altering the buffer rate made no difference. However the sound in the VST plug in seems acceptable enough. This fix was therefore not good enough and did not solve all the issues. Mine also was not an upgrade from Podfarm 2 although I was using an older version Podfarm 1.2 which was faultless for me until I downloaded Podfarm 2.5. Now even Podfarm 1.2 fails to start in standalone mode with my UX1 connected and neither will Podfarm 2.5. They just state that they failed to initialize and give a code WXYZ or something. My UX1 is now useless to me as a device. I have done a new download of Podfarm 1.2 and that was just the same. Line 6 need to get their act together now to fix this. I would encourage anyone with similar same issues to make themselves heard on this forum or other discussion threads of mine such as 'Podfarm 2.5 has made my UX1 unuseable'. People have been reading them but not posting a reply it may be because they have issues and are waiting to see how it all pans out. People need to make themselves heard to see the real extent of these problems that Podfarm 2.5 release has caused and to increase the pressure on Line 6 to act with some solutions..

I am no Computer buff at all. I just have a very basic understanding of computers. I read through the link by Line 6 Hugo in which he describes the current issues with PODfarm 2.5 and he mentions the Windows based problem issue with Microsoft Visual C++ Redistributable (is it 2005 SP?) not updated or installed correctly on the computer system. i have no clue as to what he is referring to. This has never been an issue before with my system or i have not noticed it. I dont have a clue about where to get this. i have put it into search engines who come up with loads of sites. Can anyone tell me where to obtain this safely. I would have anticipated that if its already on your computer you should be able to get it from Microsoft for free. Is this the case or am I going to have to pay out more. I am very dubious about downloading this from any other site other than Microsoft because of the poossibility of further infection or virus attacks from unverified sources. Anyone got any ideas on this. Its a real load of more hassle to just get this software working though.

I already have a set of Podfarm 1.12 saved on my computer in my downloads but re-installing it did not work.

I 've just seen this from LIne 6 Perry in response to the fail to Initialise code - it might be a fix but I cant understand why line 6 have not been pushing it in these discussions

I've seen that message before with a few users; the issue was that the downloaded installer for the software was corrupted (in those cases by an Anti-Virus scan).

In those particular cases, a fresh download of the software installer with Anti-Virus disabled solved the issue.

My recommendation would be to uninstall any previously installed Line 6 software applications. Then, just download POD Farm 2.5 Installer.exe with Anti-Virus disabled. Do a clean install.

Note: you should see that the installer will attempt to install a Microsoft Visual C++ Dependency related files. This should be done. If it fails, you may need to go into your Control Panel/Windows Updates and manually check for the C++ Dependency update through Microsoft in order for POD Farm 2.5 to run correctly...

Come on, they're just buying some time... if C++ is the problem, what's with OSX? Coming up with sollutions like this just means that they still haven't got a clue on what's happening...and this is almost for a month now.

A question for Line 6:

Who will compensate the lost time for those of us who do this for a living? Right now, I'm losing 4 days of studio time because of your inability to properly test your software! Who will pay for that? And please, do not suggest any "temporary fixes", because that takes even more of my time.

Yep, i'm a teckie too! C++ thing is pure BS! Still the lack of quality and poor customer service lingers!! I Agree we should be compensated for lost time! I bought this software with a fresh install of Pod Farm 2.5. So I have never been able to work with it!!

Finally managed to do a decent download this time I had previously downloaded another version of Microsoft Visual C++ and ran its repair function first. Then I downloaded 2.5 with my firewall off. Then set up exe the 2.5. This time it worked and has all my amps of my Power Pack add on and all show. The standalone runs with my UX1 but the sound from the drivers is still the same - not good !Pops and hicupps that just put you off playing. In my opinion, if this is it, then there has been a downgrading in the sound quality department. Its not nearly as good as my version 1.12 which I am running with DRiver version 3.4.3.6 which are great drivers. These new ones just dont cut it. So I decided to try and use these with the new version 2.5. Thats when it went wrong again and both versions failed to initialise again. I am getting rid of the 2.5 and now waiting until all mattters have been resolved and hopefulllythen I may be able to get a better sound out of it than my version 1.12 which to me sounds brill still. Is the 2.5 a step forward in sound at the moment? I HAVE TO SAY NO IT SEEMS LIKE A BACKWARDS STEP! Perhaps functionality has improved but sound quality seems to have suffered. I have successfully re-installed my 1.12 version again.

For example - one poster says it works in Ableton with the cpu at 80%.Another says it crashes Logic (I think) when he adds a second instance of the plugin. Well that would be likely if one instance uses 80%.

Now the biggest problem for Line6 is to explain that they've made a mistake...they tried throwing the ball to the users first, then the usb hubs, then Microsoft, just trying to get some time... Why don't they just put a sticky on the forum, and TAKE down from the server the 2.5 update? After all, much bigger companies had problems, for example Skype was down for days a couple of months ago.

Take down the 2.5 update, you're only generating more unhappy users. Say that you've made a mistake, and try to deal with it.

I initially started off having a problem with Gearbox (this thread http://line6.com/community/thread/65267) as I didn't use PF as much - of course, if Gearbox is fecked, then PF is what I turn to next...Which is also fecked. Tried all the 'fixes', different OS's, different computers, USB cable swaps, Firewall's disabled, Anti-Virus disabled, system restores, uninstalls, reinstalls multiple times in a vain attempt to get something to work.

I keep seeing the support guys suggest using the Line 6 uninstaller, but I'm quite certain in Windows there are a few folders left behind in various places even after the uninstall procedure takes place. In the hidden Program Data and \\users\name\Appdata\Roaming folders, for example. Goodness knows what else is still left behind in the registry after the 'uninstall'.

Would be nice if there was a list of these folders, their locations and whether or not they can be safely deleted (or if the uninstaller actually uninstalled everything)

BUT....What's worrying me at the moment is the messages the support guys are currently leaving - y'know, 'This is an issue we are currently looking into. An update should be supplied shortly, Sorry for the inconvenience' - yeah, that's cool. it's the following line 'We should have an update avalible within the next week'.

It was ok to say that *last week*, but if I can count, then the 'next week' mentioned in the context of the first time that sentence was used is over in 2 days....Or, does it just reset to a full 7 days each new day that message is posted??? What's the sketch going to be if they're still posting that on Friday? Another frustrating week's worth of Line 6 products being used as paperweights (with a fix due 'within the next week')?

Line 6 I work in the Education Sector Promoting Music Technology if this is the support you give to your professional customers I am disguest with your response that I have been reading on this thread for the last few weeks. Seriously pull your game up!!!! or you will loose confidence with your customers of your professionalism of your lack of Technical support which is basically a PLAIN JOKE

If I bought something from a shop and it didn't work, they would give me my money back, this should be no different, after countless uninstall/reinstalls it just plain does not work! if they have any morals they will refund and get back in touch when they have a working product we can purchase, I would rather use cruddy old Guitar Rig than lose more hair over this... and I hate Guitar Rig...

WOW.... looks like I'll be hangin' at 2.02 for even longer! What a tragic comedy train-wreck of events we're all witnessing here.

Personally, I'm not even bothering with this update on my system at the moment until either A) I have all my critical projects finished or B) I know other Mac/Platinum/iLok users aren't having any more issues. Until then, I'm gonna pull up a chair and have some popcorn... and watch more of the festivities!

Exactly what happened to me, I nearly lost an eye through the sheer stress of it, I ended up unistalling every thing and having to go into the terminal app on my mac and repair disc permissions, but then installed 2.02 as 2.51 is just as bad as 2.5

If anyone is having a nightmare below is what they sent me, and if you follow it to the letter you can then reinstall 2.02 and it will at least work, but, why are we having to do this, they should run check before releasing insanely badly coded updates that destroy everything!!!

INSTRUCTIONS (but don't install 2.51 its shite)

Please follow the instructions at the link below to completely remove all instances of POD Farm from your computer:

After completely removing all instances of POD Farm from the computer, please launch the disc utility program which is located within the utility folder on your hard drive. Select your MAC HD and then select repair disc permissions. After this has completed successfully, restart the computer. Upon restarting the computer, please download and install a fresh copy of POD Farm 2.51 from from the link below:

Yes i tried the lot installing/unintalling, starting again, clean install of 2.51 and it didnt change a thing. So sick and tired of trying different work arounds, we shoulnt have to work around anything !!

I'm not 100% sure, but I don't think the support guys are following this thread any longer - perhaps due to the issues concerned relating to v.2.50...Might need to get a 'PF 2.51 issues' thread or something

Please update Line 6 Monkey, which will include the update to License Manager. Then use Monkey to download and install the new driver update. Upon completion, download and install POD Farm 2.51. Then use the newly updated License Manager software to de-authorize and re-authorize all of your computers and devices.

I have v.2.50 and it is working fine for me on vista 64 Intel Core 2 Duo cpu E8400 @ 3.00 ghz ram 2gb.

I only have the normal PFarm i.e. no extra amps purchased.

Also, I only started with Pod Farm on version 2.01 and not a v1.

Perhaps this has something to do with why mine is working whereas other peoples' are not?

I thought the input source box was missing from standalone but using it today, I think it was there. I just go into control panel and to the Line 6 settings box and select source there (but now I'm thinking I don't need to do that probably).

Just thought this might be of some possible help to people/developers i.e. maybe there is some link between PF2.5 working/not working and which version was the first one you installed? I know everyone has uninstalled etc. I'm not doubting that. I am just wondering if maybe there is something though that for some reason affects later updates?

Good to get help from someone who has a working version. Good of you to think of those less fortunate than yourself. nice one. My suspicions now lie with the Hardware that people are using. i think the Program development has outgrown its hardware component and been too developed . Why I think that is because when the Pod Studio UX series was developed and possibly the others they did not envisage correctly what they would be asking it to do in the future to the point that it has developed and can no longer be sustained by its hardware. I really get the feeling that my UX1 is struggling to keep up with the demands now and this complex relationship that has developed between Monkey, Lcence Manager and possibly the increasing complexity of the Drivers being used.

AND BY THE WAY 2.02 is NOT WORKING FOR ME IN DUAL MODE. I KNOW NOT WHY ! 2.5 & 2.51 WILL NOT WORK AT ALL. YOU ARE ONE OF THE LUCKY ONES.

Not sure where you want me to go Rockfer with the link it dont seem to lead anywhere. Yes you're right I feel I have more faith in the Community than in the support. Think I have tried that fix but it didn't work if I am right it has been superceeded by the 2.51 fix. That did clear up some issues in that I got access to all my models and my add ons such as Power pack etc. Its the sound issue. Cannot get a sound with 2.5 or 2.51 that doesn't just COUGH, CRACKLE, SPLUTTER , POP however you want to describe it. I gave up and decided to try to use PF2.02 because that would do. The only reason I went from PF1.12 to PF 2.5 was because of the MIDI CONTROL. Anyhow could not get 2.5 to work so went to 2.02 instead. It works except in Dual Tone where I get issues with sound again similar to that I was getting in 2.51 etc. Dual Tone just cuts out and cuts in the dies . Single Tone is fine. I went backi to 1.12 but that works in both Single Tone & Dual Tone and gives no issues. Its all very weird. I have tried to folllow the supportb advice but nothin is working to fix the sound issues. I am using Vista 32 bit as the platform. I have done all the changes to buffering FAST & SLOW but nothing is working. I have tried all combinations of drivers including older version. Nothing. L6 aren't coming up with anything. All thye time 1.12 runs like a dream but I want to run a version of PF2 for the Midi.

just downloaded 2.01 (Archived) that works better but still problems in Dual - its a rapid wavering or shimmering type sound that only seems to effect the second tone in Dual mode rather like a badly tuned in radio. Messin around with the Global Gate seems to make a difference bad or worse but whatever it seems to have some effect. Go back to Tone A on the ABY switch and it works fine again. Therefore ll problems are when you factor Tone B in. Tone B alone sound a bit muffled when compared to the sound coming out of Tone A alone. All a bit weird.

Rockfer this is a reply I sent to Kelvis360 in another of my discussions

Sorry to hear that Kelvis 360 'Mad Scientist' I have replied directly by email to L6Hugo to see where my Tickets are supposed to be. I also thought my UX1 was dead at some point after installing 2.5 but I did get it back by removing 2.5 from my system and replacing it with 2.02 and even 2.01. I too have been EXPERIMENTING Again and I have found something. I have now got PF2.01 to work and this is how I did it but before L6 think they are off the hook THEY MOST CERTAINLY ARE NOT. Bear in mind that 2.01 version is an archived version of Podfarm so all its problems should have been sorted by now. Well to get it functioning correctly first I had to look at the buffer rate in preferences I took this down from 512 in the Audio- MIDI devices to 128 but it also works on 256 set the buffering around about medium. Noticed that I had sound in both loops of Dual tone and messing about with A/B & A+B buttons was working without that cutting in and out frequency thing I was getting. Continued to use for half an hour without issue and then (I hope L6 are listening to this bit) as soon as I hit the Global gate on it all went Crazy again and started the dot dash dot dash stuff again then lost sound completely. Further experiments reveal that it happens more when you are messing with the A/B than with the A+B thats because this thing only effects tone B in the loop as I had revealed before. Then the next thing I found out (Listen again L6) is that if you go to next item in the setlist and its just a single Tone chain the sound comes back. If I then put Global gate back on its fine but if I go back to the previous tone Dual Tone with Global Gate on again it immediately effects the sound again. There seems to be a definate glitch there which seems to be working (listen again L6) between the Global Gate and the A/B switch. There may be something linking this to where the sound patches were first made as some of them could have been made in earlier versions of PF such as 1.12 or maybe earlier. I have done the Refresh Tone Database thing though so that should have no bearing on current problems . I have also saved these tones in question before so they have been UPGRADED as well. There may be some link there I know not. Anyway my job is done its up to L6 to look further into these matters.Job done then with 2.01 but still need to find out what the sound issues are with 2.51. Also I dont know if it makes any difference all the while while I was carrying out this experiment I had the MIDI selection in the Preferences 'unchecked' for my UX1. Didn't seem to make any difference as i had nothing plugged in that sends or recieves any Midi messages. Hope you get something sorted with your UX2. I can at least use PF2.01 if I am carefull to avoid switching on the GLOBAL GATE for the time being.

Me again - talking to myself and Wilson of course to stop the madness. Just some more thoughts on this sound issue that I am having with PF 2.5. & 2.51. The last thread did not answer this directly I realise however it has just occurred to me that if there was a problem with 2.01 and that never got picked up before it is likley that the developers never addressed it in 2.02 either. Now 2.01 is archived and replaced by 2.02 but that did not address any fix for those issues & so to 2.5 and then 2..51 all without these issues being addressed could be something in it that is perhaps responsible for sound issues with 2.51. I think maybe as I know quite a few people with similar sound issues. I will do some more experiments to see if the Global gate has any noticeable effect but I know that it was not picked up as an issue in the fixes for 2.02 ( at least it says not in the release notes of known issues)where it seems to occur again. Ok may be something to do with my computer being more sensitive to such issues but its most deffo highlighted that there are some glitches between the A/B switches and the Global Gate going on.

Sometime later Wilson & I decided to take PF2.01 off ( uninstall) and re-install 2.02 to check our theories and seems they are spot on. 2.02 suffers with the same glitches between the A/B and the Global gate. As soon as you put the Global gate on whoa dot dash dot dash until it just cant take any more and sound eventually goes. It wont return again until I scroll to another Single Tone preset in the setlist and then its ok again. Everytime I touch Global Gate and the A/B is set to send Tone B it does it without fail. This seems to confirm our suspicions hey Wilson? He's rolled off for the time being. Anyways it seems so. Could be the developers have overlooked this problem right into 2.51?????????????

IT WON'T BE LONG NOW AND TWO MONTHS WILL HAVE PASSED BY THE RELEASE DATE OF 2.5. MAKES ME WONDER WHY THE LINK http://line6.com/community/docs/DOC-2304 HAS NOT BEEN UPDATED SINCE JUNE 20TH. MAKES ME WONDER IF THOSE OF US WHO WERE PAID CUSTOMERS BEFORE 2.5 WILL JUST BE DISCOUNTED AS LONG AS THEY "LINE 6" CAN KEEP SELLING THE APPLICATION WITHOUT KEEPING THOSE OF USE WHO WERE ALREADY ON BOARD UPDATED BETTER THAN THIS............... THIS IS JUST HOW BILLY BOB GATES AND HIS BOYS RELEASE SOFTWARE FOR THE PUBLIC TO TEST IT FOR THEM............. RATHER THAN TEST IT .......... REALLY TEST IT........... THEMSELVES..........

Nice first post, ijapos. Take a very civil thread and turn it ugly on your very first post. Nice work.Have you put a support ticket in yet? Have you searched for some help for the issues you have been having? Have you posted anywhere these troubles you are having? Ask a forum member for help? What precisely have you done to better your situation? I mean other than come here and regurgitate your disdain for Line 6!

MR. MCOLQUITT, YES I TRIED ALL THEIR "FIXES" AND ONLY DUG IN DEEPER MISERY. SO I ENDED UP AT 2.02. I AM A "RETIRED" 56 YEAR OLD PROGRAMMER THAT WORKED IN THE BIGEST BANKS IN THIS COUNTRY. THIS TYPE OF RELEASE WOULD NEVER BE TOLERATED BY GROWN UPS. I ONLY COMPLAIN WHEN I THINK IT IS WARRANTED. AND I NEVER JUDGE ANYBODY ELSE'S OPINION BECAUSE WE ALL HAVE ONE. "EVERYBODY" HAS THE RIGHT TO SPEAK THEIR MIND ABOUT THE SUPPORT THEY HAVE RECEIVED OR NOT RECEIVED, ME INCLUDED. IF YOU FELT VIOLATED, THEN MY APPOLIGIES TO YOU. I THOUGHT MY COMPLAINT WAS WITH LINE 6, THE WAY I WROTE IT. AND I THOUGHT THAT IT WAS A FACTUAL ACCOUNTING OF MY EXPERIENCE WITH THE UPGRADE ISSUE.

In your thread, please make the request as clear as possible by just getting to the problem. Provide a description of the problem, any hardware and software (with version #'s) you are using, and a detailed recipe on how to reproduce the problem you are experiencing. Please make sure to mark the thread as a question to be flagged for support.

I nuked the last few posts because people are getting carried away. We understand some customers have been negatively impacted in using POD Farm 2.51 and are rightfully upset about it. Hugo has tickets for Whitie and Kelvis, among others, to help us try to get to the bottom of the various issues people are presenting, which may take time to reproduce and address. Mcolquitt kind of alluded to this process, and we're sorry it's taken this much time to try to wade thru all the complaints, organize them, understand them and gather data so we can escalate them correctly and efficiently in an effort to resolve these issues. It's a process who's speed depends on a number of factors, some of them beyond our control, but we will do our best to get Engineering the info they need to move forward.

Don't mind at all Tony. Thanks for understanding our frustration and not taking the comments to heart. I actually thought about editing the collection of posts from this thread out myself today (as the point of it seemed to have been lost on it's intended target) but you beat me to it anyway, fair play.

Serge @ UK tech support said he opened two tickets for me, one for Gearbox & one for PF - never seen anything about them tho', and the support tickets section in 'my account' has nothing on it.

Cheers Tony. Of course you are working on it. It is ridiculous to imagine any of the accusations hurled at L6 as remotely possible. You have ALWAYS proved your integrity as a company by ALWAYS making things right.

To openly say "Where is Line 6" "why are they not paying attention" "They don't care about their current customer base" blah blah blah is just plain baseless. Look at a companies history of action in these situations and say those things with a straight face...I dare ya!! LOL.

I am sorry for getting mouthy with people that are upset. There are, however, more tactful and civilized ways to go about getting information and help than slamming the company and acting all entitled! It will always disgust me, I will try and keep my comments to myself in the future.

Na, I don't think it has anything to do with that at all. It has more to do with the fact that with so many major errors in this release that were found within hours by the public make independent thinkers wonder what they did to test the release. It is embarassing to LIne6 that they released the update with evidently little or no testing. They just need as many brown noser's that they can get to feel good through the storm.

ijapos, You are an amazing individual but hardly a free thinker. You blast into the thread AND the forum and start shouting in caps about all the horrible pains you are having to suffer without mention or indication that you have followed ANY of the troubleshooting procedures that folks need to do to get things in process for resolve.

You are right I shouldn't ask you what you have done to remedy your situation before your temper tantrum of a post; I shouldn't have too.

You may wanrt to go back and read through some of my past postings before you make a statement like I have nothing to offer. You sir, have nothing to offer thus far and whats strange is you offer NOTHING to yourself either. You just want to yell and vent and have everyone around you make things ok all the while never move in the right direction for your own troubleshooting

You are just exactly like two other kids in another thread that were ranting and yelling about how the world is against them and Line 6 won't help.

It is dispicable behavior that amazingly still gets responded to by Line 6 staff in the effort to satisfy their customers issues. So instead of pointing the finger at me and line 6 go look in the mirror and have a word with that guy. I imagine you have a great deal of trouble maintaining friends and relationships in real life and are constantly wondering why. Again that is a conversation you need to have with the mirror.

Have a nice day and I honestly hope your problems are solved sooner than later. I don't like knowing fellow musicians can't make music. I know Line 6 feels this way also.