Jun 27, 2011 8:53 AM
Podfarm 2.51 is another Botched Fix. Why aren't L6 listening?
-
Like (0)
Pretty much looks like it to me. This time the Drivers wont 'Apply' a reduced buffering size. The result is that the sound remains full of POPS & CRackles. Aren't Line 6 Listening I have told that in my other discussions about Driver issues and they go and release this half fix for the doomed PF 2.5. This is just not good enough. Now I want to revert back to 2.02 but something has been left from getting rid of the 'NASTY 2.51' and it wont now initialize. Also noticed that the 2.5 failed to recognise my licence to use it as ELEMENTS in Cakewalk Sonar DAW. This is just not good enough again. Why wont my 2.02 come back and work. All I am left with now is 1.12 I think although I haven't checked yet. MY ADVICE TO ANYONE THINKING OF GETTING UPGRADE TO 2.5 OR VRS 2.51 IS DONT. I WILL BE STICKING TO 2.02 IF & WHEN I CAN GET IT TO RUN AGAIN ON THIS COMPUTER WITH MY UX1.
THIS IS A CONTINUATION OF MY PREVIOUS THREAD WHICH I MISTAKENLY MARKED AS ANSWERED WHEN ITS CLEARLY NOT!
uPDATE
Tried to go back to 2.02 which was working reliably before the PF2.51 download but now I am having problems with this. Dual tone settings are not functioning correctly especially TONE B which works intermittently and then may just stop altogether after a 'COUGHING FIT' leaving no sound from either output. Tone A on its own works fine when its on a single TONE and yes I have plenty of CPU headroom. Seems the 'NASTY PF 2.51' has left its mark on my UX1. Alll this is just so mind numbingly tiresome having to unistall, install , then un-install, restart , check again and still nothing works. I am constantly changing the drivers to my UX1 which seems to be getting pretty confused itself.This is just ruining the LIne 6 experience. I have paid to use at least one version of the PF2 in whatever form but frustratingly nothing is working and its constantly driving me back to use the PF 1.12. I WANT MY PLAYING TIME BACK. I AM NOT PAID TO BE A LINE 6 TECHNICIAN. DO YOUR JOBS & LET ME GET ON WITH MINE. FIX THIS ISSUE!
Got a Reply from Line6Dom states
Hey Whitie60,
We have recently released updates to the following applications:
Line 6 Monkey - 1.41
Line 6 License Manager - 1.01
POD Farm - 2.51
Mac OSX Drivers - 5.9.3
Please use the instructions at the page below to completely remove all instances of POD Farm:
http://line6.com/community/docs/DOC-2304
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.
If you are having trouble with the driver options, make sure you have the most recent drivers for your operating system installed as well as drivers for your 3rd party interfaces. Make sure to try all port connections as well.
And this is reply to that -
fOLLOWED YOUR INSTRUCTIONS TO THE LETTER AND GUESS WHAT - IT DONT WORK.
Despite my better judgement I TRIED IT OUT as you suggested so to cover all angles to make sure that i hadn't missed anything. Guess what/ I wish I hadn't. But it doesn't work. what made you think it would have you tried it yourself? Why dont L6 just admitt that the 2.5 & now 2.51 are just DUFFERS. You are just buying time L6 It dont work. Yes you get a version, yes you can change the Amps & fx and I have all models of my Add ons but the sound is just CRAP. It SQUEALS,it POPS, it CRackles , IT COUGHS & SPLUTTERS its friggin USELESS. changing the buffer size makes not difference at all I have had it on the highest buffer setting and its just the same. Whats wrong with L6 they give you advice and a fix & you expect that they have at least tested it first. Obviously not. This is no fix. Now I have to go through the whole damm thing again to get back my 2.02. L6 ARE USING US AS THEIR GUINEA PIGS HAVE THEY NO TECHNICIANS THEMSELVES WHO CAN VERIFY THAT THE PRODUCTS THEY ARE RELEASING ACTUALLY WORK BEFORE THEY RELEASE THEM. 2.5 & 2.51 ARE A TOTAL WASTE OF TIME.
It appears that L6 are just digging a bigger and bigger hole in which to bury both the DOOMED and FAILED release of PF 2.5 (& VRS 2.51) along with their reputation. Just admit it the whole thing dont work and you have just wasted everyone's time. I bought into PF because I liked the versions 1.12 and 2.02 but maybe the 2.5 & 2.51 were just a step too far. Why tell us the problems are fixed when they are not. This is a serious downgrade in sound quality. I have been stating all the time they need to look into the Driver Issues yet they do a new release of 2.5 in the form of 2.51 and its still got the same Driver issues it had in 2.5. L6 are clearly not listening and neither are the technicians who answer these threads. What gave L6Dom the right to suggest a fix that clearly doesn't work & that he oviously hasn't used because if he had he would know that there are still sound issues with this version.. We deserve something thats tested and that works. Its simply not good enough! I HAVE A BUSY LIFE I DONT NEED TO BE TAKING PART IN PRODUCT RESEARCH. WHEN I BUY INTO A PRODUCT I EXPECT IT TO MAKE MY LIFE SIMPLER NOT MORE COMPLICATED. MY ADVICE TO L6 IS DONT TAKE YOUR CUSTOMERS FOR MUGS.
Went Back to 2.02 and 1.12. Dual tones dont seem to work in the 2.02 or not very well at all no matter what drivers I use and I have tried them all. However Dual Tonein 1.12 with the same Drivers works perfectly normal without any problems. Its difficult to tell if the problem with 2.02 has always been there because I haven,t used it before. My feelings are that it should work as well as it does in 1.12 but it just dont.
Ok, heres where I'm at:
In the midst of Whitie trying to talk me through how he got PF 2.02 back working, the following instructions were given on the correct procedure for setting up 2.51:
Please use the instructions at the page below to completely remove all instances of POD Farm:
http://line6.com/community/docs/DOC-2304
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.
So, considering the last time I de-authorized my UX2, I couldn't re-auth it (this thread):
http://line6.com/community/thread/65267?tstart=0 )
I figured that issue may have been caused by a bug in the License Manager (which we received an updated version for). I followed the procedure posted above and then, as you can guess couldn't re-authorize - I posted a question about the issue here:
http://line6.com/community/thread/66822?tstart=0.
Once everything was authorized and setup as indicated, Serge@Support stayed on the line with me while I tested the sound - I strummed the guitar and I could hear distortion coming out the headphones, whoo! I thought, great it's sorted - but, as soon as I selected a preset, back to unprocessed dry sounds. Serge said he was going to escalate this to L6Hugo, so hopefully the next patch will work this out.
But here's something interesting: I decided just to mess around since I had it plugged in and I found if I clicked here:
And then used the arrow keys on my keyboard to quickly cycle between amps or effects and believe it or not - intermittently, it works! But, (probably because of the fast switching) quite often, the 'lux is sounding like the treadplate, or some other amp it's not supposed to - this behaviour exhibits on any and all amps and effects...For example choose from distortions, cycle quickly through the choices until the sound randomly activates - but then, the pedal displayed onscreen may sound like a random other distortion pedal.
If 1 is your first effect, amp, whatever and 1) is the correct effect, amp sound that it's supposed to be connected to, when working properly the numbers would be:
1 - 1)
2 - 2)
3 - 3)
4 - 4)
Etc. However, after key-cycling the selection quickly to attempt to activate the sound, the numbers could be:
1 - 3)
2 - 4)
3 - 5)
4 - 6)
Sometimes cab 'air' works, mostly it doesn't, doesn't make a difference which cab choice you make, the key-cycling trick doesn't seem to work with the cab 'air' as it does with everything else. All other effects options I've tried work *intermittently* with this key-cycling method.
Crazy, huh?
Anyway, hoping this info might help the L6 guys get us a patch!
Sheesh, TLDR! ![]()
Kelvis 360 - good to know you are still trying. I managed to get my PF 1.12 working and the 2.02 works in a fashion. The main problem I have with the 2.02 is that Dual Tone just dont work its splutters, dies, comes back and dies again. I have tried all Drivers including the ones that came bundled with the programme but nothing improves it. The Problems seem to be related to either the ABY control or the gate as it happens when i am messing with these switches. The single Tone settings work just fine. I have no Problems in Dual Tone with the PF1.12 which works great and the same drivers behave differently when i connect 2.02 into the equation so me thinks its more to do with PF2 than anything else. The 2.5 there is even more degradation in sound to the point that Single Tone is effected as well and the sound just splutters. The whole PF2 thing seems so glitchy but PF1.12 has no issues at all. I really dont know whats going on at all. L6 have suggested that its the USB ports on my Computer but I dont buy that because the same Port works fine with PF1.12. I am not using a USB hub and there is nothing wrong with my Computer. The Problem is also because i have never really got to use the PF2.02 so dont know whether it has developed this behaviour recently or not. I bought into the release of 2.5 but since that refuses to work properly I have had to take a version of 2.02 instead which works only partially.
Based on your experiences i am not alone in questioning how Glitchy the whole PF2 and 2.5 thing is. I feel now that L6 should be offering us some Support Tickets for those who still have problems after the 2.51 fix. It sounds like they may be realising that they are not out of the Hot Water yet with these issues. However I have heard from some users that the 2.5.1 has fixed all their problems. They are so lucky! this is really doin my Head In!
Kelvis360 - couldn't help just ****** myself at the thought of you just clicking and pressing your keyboard whilst playing your guitar. You must have more hands than one of them Hindu Gods. Wow you are really gettin into this. I really dont know what all those codes are supposed to mean. All I can say is try to KEEP YOUR SANITY. GOD KNOWS ITS HARD WITH ALL THIS HAPPENING. I tried all that stuff suggested but it didn't work . NOW ALL I WANT IS FOR PODFARM 2.02 to work. I am not asking for much not even the Dreadful 2.5 ,just one working version of Podfarm 2 would be nice. I've taken Licence manager off my computer again. I'm sick of all the downloading I have had to do I must have exceeded my quota of downloading since I have had 2.5 so i'll probably get stung again for some more money as a by-product in relation to this L6 product.
lol, yeah mate it's comic alright! Not that I'm getting to play much guitar at the moment ![]()
What I mean by the codes is, well I'm just assigning a number to a function: Lets say you have the AC30 amp selected - the graphics will display a vox amp (and I'm using a number just to represent the amp) [ 1 ] , and the software will sound like a vox amp [ 1) ].
But after key-cycling to get the sound to activate (instead of the dry, unprocessed sound) the software seems to get confused:
The graphics will display a Vox amp [ 1 ] but the software sounds like a Marshall [ 3) ]
Heh, I know it sounds crazy but it's the best way I can explain it
It's like whatever amp/effect you select, the software is 2 or 3 selections behind (or ahead of) your choice...
Whatever works for you I suppose but DONT LOOSE YOUR MIND with it. But it really is enough to drive anyone INSANE. I aint playin too much either the time I do spend on it is used up like yourself in Similar EXPERIMENTS testing what is best what works or dont or just installing and re-installing it and chasing all the problems it produces. I FEEL MORE LIKE A SCIENTIST THESE DAYS than a GUITARIST. What the hell have we become?
Kelvis360 Mad Scientist - its a MAD WORLD ! CRAZY. You want to know something even more absurd. You'll like this. ! I have just noticed that L6 have put the price of PF2.5 up ! Thats a joke NOT!
Heh! PF 2.5x should carry a warning sticker
Was kinda hoping for some feedback from the support guys yesterday regarding these issues...Bump?
Hey Kelvis360 Mad Scientist - where are are our 'Golden Tickets?'. 'We need our GOLDEN TICKETS!'
Hi,
If your UX1 is popping and clicking it is most likely related to connection issue or driver conflict.
Have you tried connecting to different USB Ports?
Are you using a USB hub?
try the optimizations in our USB Troubleshooting Guide:
http://line6.com/community/docs/DOC-4282
Also, I notice you are on a Toshiba laptop is it an AMD based computer?
http://line6.com/community/docs/DOC-2215
Disconnect any web cams, digital cameras, or third party audio interfaces and see if the pops and clicks still occur.
Finally, make sure your video card drivers are up to date.
Thanks,
David
Line 6 Customer Support
Line6David - you may wish to study my last reply to Kelvis360 although it seems that some of our issues are different they both are sound related. I am only connecting the L6 hardware UX1. PF1.12 works absolutely fine in the same UsB port but when I bring any version of PF2 into the equation I get sound issues. In PF2.02 its only when i select Dual Tone otherwise its great. With any version of 2.5 is total corruption. Yes I am changing the drivers each time in my UX to the drivers related ( or that came with those Programs). I have tried other driver combinations such as those that come with PF 1.12 with PF2 and this seems to work better than the drivers that came bundled with 2.02 itself. however the same issue with the dual Tone is still there no matter what. 2.5 just coughs and splutters no matter what I use. All the time though the PF1.12 remains absolutely solid with no issues. I am not using a Usb hub. My Computer is a Toshiba AMD I believe Dual Core dont know the sound card may be Turion64 or something. The Computer is equim A210 or something. never given me any issues i use all sorts of programms like Cakewalk Sonar, Cakewalk Studio instruments all sorts but hardly ever atr the same time as PF. when I have been having these issues the only thing plugged in the UX1 running a single version of Pf. I dont even have my DAW running because I mainly use the Standalone version. Is there any chance of Support Ticket for these issues given that we have already gone through all the recommended fixes? Oh yes I have done all that increasing the size of the Buffers etc and used the highest settings but it did not work either. One thing that may be significant is that if you unplug usb then replug it in whilst using 2.02 in Dual Tone the sound partially returns but again only very briefly. It degrades again soon after.
News in - Studying some other discussions post 2.51 i am relieved but still dissappointed to hear that I am not alone with the 2.5 and 2.51 sound issues in Standalone. I dont know how common it is but for some at least these issues remain a Problem Post 2.51
Message was edited by: Whitie60
Indeed mate. I think the thing to keep in mind is that previous to the release of PF 2.50, Monkey 1.40 & Licence Manager - *everything worked like a charm* - on the same PC systems that the aforementioned software currently exhibits issues with (for us, at least).
The hardware hasn't changed fellas, just the software. Kinda indicates where the problem lies, huh?
Problem is that the thing exhibits different bugs and behaves different in each system. Its just so weird! looking at other discussions I have found one person with exactly the same issues I am having with the sound. I am also trying to find out whether 2.02 had these problems prior to release of 2.5. the problem I have is that I never used it then and only just recently decided to upgrade & by then 2.5 had been rolled out to replace it. If there were problems with 2.02 before release of 2.5 then i guess I will be stuck with 2.5 as they are unlikley now to make any improvements to vrs 2.02. Since 2.5 is currently not available to me because of the Sound issues i am having then I am left with only a part functioning version of PF2. That really ain't good enough ! lets hope they can at least offer us some Support Tickets.
L6David - perhaps it may be related to issues with the sampling rate. I have tried the Buffering but not altered the sample rates. To be honest its not something I like to do as i have no guidelines about what I should be doing and dont want to adversely effect the performance of the software. Bit depth i feel should not alter as it has to be either 16 or 24. I feel 24 is the standard and as such the software should be able to cope with this otherwise it would not be up to its spec. Perhaps you could give me some values to try with the sample rate to see if this has any effect on the sound issues. Or some other guidelines would be helpful.
be sure to set your bitdepth to 16 and your samplerate to 44.1kHz, these values are standard for homerecording and will give you cd-quality sound.
24bit is used in topnotch studiorecording setups but unless you''re a professional studioengineer and/or recording artist with matching equipement, this will give you no additional soundquality and will only stress your CPU.
Increasing the buffersize should help if you''re experiencing pops/crackles but it will also increase latency (time between the instrument played and the sound heard).
FYI: the digital soundsampling that takes place in your computer has two parameters: the samplerate (ie the amount of samples taken every second, 1kHz=1000samples per second) and the bit depth (ie the amount of bits per sample). Multiplying these values gives you the bitrate: 16x44.1=705.6 kilobits per second. This is the amount of bits stored every second for one mono channel, so for stereo the bitrate is 1411kbps (kilobits per second) which is cd-quality.
Hey Vries,
cheers for the info mate, but my gripe is that my UX2 worked A-ok previous to the 2.50 & 2.51 releases. I've gone through the setup exactly as stated by the support guys, even called UK tech support and got the fantastically helpful Serge to go through it all with me step by step until everything was as good as it was going to get...
Still, no processed sound on PF2.51, same as on 2.50. There was nothing more the fella could do to help, aside from raising and escalating the issue to L6Hugo. Whitie, he said he would raise a ticket for me, but I don't see anything in my suppport tickets window...Maybe that's another glitch? ![]()
To be honest, I think the support guys are just avoiding these 2.51 issues for now, as I noticed they were answering questions last night dated *after* some of our 2.51 complaints from a couple of days ago.
Or maybe I'm just losing my sanity true enough! ![]()
Kelvis 360 'Mad Scientist' - you are bang on with YOUR THEORIES. I too feel they are avoiding this SOUND ISSUE with 2.5 and 2.51 because they dont have a clue. As Vries states the PF2 & 2.5 & 2.51 should be able to process sound to a standandised rate which is currently 24 bit. Anything less is really less than what we would expect in terms of performance. Its simply not on asking us to reduce our expectations in terms of this quality as it should be able to process CD quality sound. I think its a bit of a cheek asking us to reduce the bit depth to make the thing work. I just dont get any sense that they onto this issue with the sound at all. They dont even seem to read through the problem. I have said that i have tried ever combination of Buffering high and low (Fast & Safe) nothing works yes it should as Vries states that should have some bearing on pops and crackles but it dont. They need to give us these GOLDEN TICKETS to get the matter sorted out. I for one wont stop putting these discussions on about this issue until its cleared up.
Vries - thanks for the reply. Surely the PF2.5 & others come with a standard set of values in relation to sampling rate. I really dont have much clue as to why I should deviate from this. I understand your arguement for the 16 bit rate that makes sennse but i dont know enough about resetting sampling rates to be sure what I am doing and really why I would be doing it. Surely it should just work 'out of the Box ' so to speak without me having to do too much messin about. I never had to mess about with PF1.12 which still works like a dream and that has a pre set up sample rate thats served me some years. Any more thoughts?
Theory confirmed?
http://line6.com/community/thread/66654?tstart=90 - posted 24th June, no reply from L6 support as of 30th.
http://line6.com/community/thread/66857 - posted on the 28th, reply from L6 support on the 29th!
Come on guys, give us something to work with (or at least, that L6 are aware of and are working on the problem) other than stock suggestions about USB cables and reinstalls.
Any opinion on what might be causing the 'key-cycling' trick to cause the effects to partially work for me? Has your QA had any luck reproducing it?
Yes Kelvis 360 'Mad Scientist' you are correct. There is nothing at ALL SCIENTIFIC about the fixes that we have been offered so far. WHO on earth thought about the PULL THE USB CABLE OUT & REPLACE IT. Its laughable and even more laughable that it worked for some. BUFFERING - everyone knows about BUFFERING but that dont even work in logical way in PF2 or PF2.51. Surely the Boffins at L^ did not intend PF2.5 it to be used in such a PREHISTORIC, CAVEMANLIKE way. ITS NOT SCIENTIFIC. Perhaps its the lack of REASON & SCIENCE that is defeating our LOGICAL HUMANOID BRAINS so much so that we simply cannot work it out at all. ITS AN ENTITY!.
Just to let you know that there is another thread of discussion & I know that you are aware of it ( because I have seen you have commented) its called 'RE Pod farm 2.5 not working correctly, models missing' its full of others who are having issues post release of 2.51 - it has reached 2,750 views post the Community Crash - thats lots of people looking for answers. JUST THOUGHT I WOULD SHARE THAT.
Here I am again replying to myself which is a true sign of MADNESS all I need now is a Ball called 'WILSON' or yes & a working version of Podfarm 2 I nearly forgot. 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.
Update on that last post (decided to create a new reply) - Regarding the 'key-cycling trick'.
Depending on whether I cycle through the cabs or delays first, the second choice will not work; So, it's cab simulation, or delay - not both at the same time.
For example, if first of all I choose a cab, cycle quickly through the cabs until I hear the sound change (at this point, the cab 'air' function will work A-ok) and then attempt the same with the delays afterwards - the delay will *not* work, 100% no matter how many times I try the key cycling trick.
The reverse is also true. If I choose a delay first, key-cycle till it works, and then attempt the same with the cabs afterwards - the 'air' function will not work, 100% no matter how many times attempted.
The problem with the amp/effect you choose randomly sounding like a completely different amp/effect seems to be a side effect of the key-cycling trick.
Kelvis 'Mad Scientist' how you do this cycling thing must be AMAZING TO SEE - you must be into shredding its a good job you have those crossover skills coming in useful. EXPERIMENT< EXPERIMENT. Seems like you are doing their job for them my friend. I am all alone on my ISLAND waiting for the LINE 6 or LINER 6 RESCUE SHIP. JUST ME & WILSON HERE waiting, waiting, waiting, waiting waiting waiting waiting --------------------- -------------- - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - & still waiting. Carry on with your experiments MAD SCIENTIST
lol
Well, I was a lead tester at a QA firm for a few years...Mibbe that explains it!
Yo I can identify with that !
Here is my new experiment -
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 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.
Hey Whitie60,
You might be on to something there, although I dare say we'll never find out. I'm getting pretty sick of stock replys. My PF2.51 won't even load up. Interestingly this appears to be because of the drivers which cubase appears to understand but my UX1 doesn't want to talk to. It's not only 2.50 and 2.51 that are the problems, driver v4.2.4.4 is also part of the problem. That may go some way to explaining why there is such a range of issues.
My latest wierdness is that when I try to rienstall the drivers, the installer package for 4.2.4.4 puts in 4.1.1.7. What the hell is going on?
Meanwhile, I can't track, about which I am heartily p**sed off.
Steve
I have been complaining about these drivers ever since they came with the POD HD300. they have been nothing but trouble. Sometimes they have even registered as Inactive when using them linked to the HD300 editing software. I have mentioned this issue to L6 in a number of forums 'Isn't that Right Wilson?' He says yes by the way. I have a sneaking suspicions that my UX1 just wont let go of them or something to that effect and there may be some legacy of them left on my computer. they are horrible and the worst drivers I have ever known L6 to send out. I have now gone back as far as Pf 2.01 which has been archived,.I think the drivers are 4.01.7 or something like that they seem better but still have issues in the Dual Tone setting when using or adding a Tone B. It sound like a Blockage to me preventing the tone getting through or a badly tuned in radio, its cutting in and out in a rapid cycling or high frequency sort of way. Tone B on its own sound muffled. - Been nice talkin to you but WILSON wants his lunch now!
Steve Townend - have you had anymore sucess with your issues with 2.51?
Nope,
Rolled back to prehistory and I currently can't record. No output to Cubase, although it more or less works in stand-alone. Interestingly, I completely wiped all L6 off my system, defragged and cleaned up then started with the driver. Opted for v4.0.2.7, downloaded it, installed it and gues what, yep, that pesky v4.1.1.7 had been installed instead. How? Who knows. There shuold have been no trace of it on my PC, I even checked the installation directories to make sure there was nothing there. Anyway after that I installed PF 2.2 and I'm now not particularly far removed from where I was.
Thought I'd got it there for a while. but my money's on that driver being a big part of the problem, but it's "dug in like an Alabama tic", to coin a phrase...
Arse
Steve
vries wrote:
be sure to set your bitdepth to 16 and your samplerate to 44.1kHz, these values are standard for homerecording and will give you cd-quality sound.
24bit is used in topnotch studiorecording setups but unless you''re a professional studioengineer and/or recording artist with matching equipement, this will give you no additional soundquality and will only stress your CPU.
Increasing the buffersize should help if you''re experiencing pops/crackles but it will also increase latency (time between the instrument played and the sound heard).
FYI: the digital soundsampling that takes place in your computer has two parameters: the samplerate (ie the amount of samples taken every second, 1kHz=1000samples per second) and the bit depth (ie the amount of bits per sample). Multiplying these values gives you the bitrate: 16x44.1=705.6 kilobits per second. This is the amount of bits stored every second for one mono channel, so for stereo the bitrate is 1411kbps (kilobits per second) which is cd-quality.
24-bit recording should certainly not stress any modern computer - it is nonsense to say otherwise, and for some of us 16-bit simply isn't good enough but that's another story altogether.
Also, 1kHz has nothing to do with a sample rate - it is a frequency and has 1,000 cycles per second not 1,000 samples per second. At CD resolution you have 44,100 samples per second - not 1,000!!
L6David - as i already said to Vries surely the software should work without the need for me to make changes to the settings such as Sample Rate
Vries - thanks for the reply. Surely the PF2.5 & others come with a standard set of values in relation to sampling rate. I really dont have much clue as to why I should deviate from this. I understand your arguement for the 16 bit rate that makes sennse but i dont know enough about resetting sampling rates to be sure what I am doing and really why I would be doing it. Surely it should just work 'out of the Box ' so to speak without me having to do too much messin about. I never had to mess about with PF1.12 which still works like a dream and that has a pre set up sample rate thats served me some years. Any more thoughts?
Later Steve Townend said about the drivers
My latest wierdness is that when I try to rienstall the drivers, the installer package for 4.2.4.4 puts in 4.1.1.7. What the hell is going on?
You really have to ask what the Hell is going on here? Where did those drivers come from? This could be the result of of the Whole Unistall function not working correctly, leaving legacies all over the place
Whitie60,
I have opened a support ticket for you concerning the problems you are experiencing. Please use the following link to view your ticket:
http://line6.com/account/tickets/view/
Regards,
Line6Hugo
Line6Hugo - sorry I cannot at this time see any evidence in my account of the Support Ticket you are referring to.
Hey Whitie,
If I can also add that I'm supposed to have a couple of these 'Golden Tickets' from Serge @ UK Tech Support - but there's nothing showing up for me in the Support Ticket section either.
P.S. don't know if you seen my 'authorised/deauthorised at the same time post' - I think my UX2 is dead...
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?????????????
Still no sign of any Support Tickets though! there is no evidence of any Support Ticket in My Account. I have recieved email to say that a ticket has been generated but the links on those email are not working and lead to dead ends. None of the links seem to lead anywhere really. this was really not the understanding about Support Tickets that I researched when I watched the video tutorial about them.
thanks for your Nice Smug G** attitude - we paid our dues to L6 and bought into something that dont work for us. we have the right to be dissatisfied. ".5 and 2.51 has issues for some of its customers - just butt out with your opinions they are unwelcome on my Discussion!
Hi Mark,
Thanks for sharing.
Although, it's hard to take anyone who tells you to "grow up and be civil" (while at the same time calling you a monumental douchebag/fool/sarcastic spoiled brat) seriously in any way, but I'll give it a shot.
I hope sometime in the future the Line 6 hardware & software that worked perfectly (on the same unchanged hardware) pre-Monkey+Licence Manager/PF 2.5x works again. This is the support forum - if users have issues with the hardware & software, this is where we go to make some noise about it.
Congratulations on your hardware working. Ours doesn't. That's why we're posting on the support forum. You seem to be posting here simply to complain and insult the people who are having problems with their gear, even though you have no issues with your hardware & software. Good for you!
Perhaps if you had a problem, posted an explanation, received a reply from support that completely ignored the explanation in favour of a cut and paste stock reply then maybe you wouldn't feel like having a drink and playing through your real amp either. Then again, maybe you could do something completely different, like not play your guitar or record anything at all:
You could maybe even go row a boat, take in a football match, give blood, donate to charity, take your dog for a walk, jump off the end of a pier...There are a million things you could do in this world, eh? For you though, I'd recommend the last option.
You see, the people posting on this Line 6 computer-based recording support forum tend to want to play or record their guitars/instruments/vox on their computer based-recording setups (because their Line 6 hardware/software isn't working) and despite the amount of information given by some of us to L6 Support, particularly by Whitie & Steve Townend, we are basically being told 'uninstall/reinstall/authorise/deauthorise'. Which doesn't work or help.
Also, some of us may not use (or even own) 'real amps' and just jam/record through our computers and pods. I know that's the case for myself and a few of the other guys posting on here for the past month or so. Only problem with that - our Pods aren't working and there's no solution for us, and the majority of the posters on here are posting about, wowser - PF 2.5x problems.
One last thing I have to ask, do you have any evidence to back up your claim of 'thousands upon thousands' of users that are happy and have working setups of PF 2.5x? Of course you don't, you just pulled that assumption out of your bung-hole. Meanwhile, this thread alone has 1,456 views as of now. If you could note as well, that PF 2.51, Monkey 1.40 & License Manager 1.01 were released very quickly after Monkey 1.01, License Manager 1.00 & PF 2.50...Those programs must've needed some bugs fixed, huh?
Maybe I should just say there are gazillions of us having problems to further my foolish sarcastic monumental douchebag spoiled ranting brat agenda?
Nah...That'd just be stupid.
P.S. Don't want to derail Whitie's thread, so if there's any need to reply to these comments it should be via P.M.
More weirdness to report now so take note also those of you who believe that we are simply making this up and wasting the time of the L6 Support Guys. This time i thought that it may be something to do with me not having the most UP to date Service Pack installed for Windows Vista. When you talk about wasting someone's time you should also think on to the amount of time I have already wasted on this problem. the amount of install -uninstall and the checking I have been doing which is wasted time that I could have used playing my guitar. whereas as in both Kelvis's view and mine we get very glib standard responses from the Support Guys who seem to be saying the same thing all the time and sometimes dont even read through the whole threads properly. we have certainly put in more time on these issues than they have yet its their product and our purchase that we are trying to get to work.
Anyhows last night I got the new Vista Service pack a massive 300 + MB to download it took ages and ages to get so long I had to leave my computer on all night. Installed it and checked Podfarm 2.02 for improvements however I would have done if the programme had not failed to initialise again. Did a uninstall and reinstall - still fails to initialise so now i have no working version at all of PF2. The next thing I tried is the ever reliable Podfarm 1.12 and guess what that works perfectly. what the Hell is Going on with PF2 in all its versions? Still feel i have nothing to gripe about - now got to install , un-install and try and get PF2 to work again now.
One further gripe revolves around my support ticket referred to in this discussion. Yes I have one or at least i did but thats stopped updating now I dont know if thats a technical issue with the L6 site but I am certainly not able to currently access much Support from L6 with these issues.
Whitie60,
What driver are you using? You may have gathered that I've managed to get 2.2 to work in stand alone or as plugin (but still not to record audio) using v4.1.1.7. Major caveat here is that I'm running XP. I was on W7 but ditched it because the UX1/PF driver (both versions 4.1.1.7 and the latest) ware causing conflicts and CPU spikes. As Vista is essentially W7 that wasn't written properly, you may be falling foul of similar architecture.
For what it's worth
Steve
steve - thanks for the reply. it was interesting to hear what you have to say on these matters. There may be something in it but if thats the case why did the Developers @ L6 not pick this up when developing PF2 and PF2.5. I have to reason that actually PF2 in its earliest version /encarnation was actually out before the release of Windows 7. If there were issues and the L6 developers were only developing PF2 for a newer version of Windows 'yet to be released' then why did they not specify this at the time and why have they not warned that actually PF2 in all its forms doesn't actually work with Windows Vista. There is nothing in the advertising to warn off Vista users and state that it dont work with that Platform. Perhaps it should I dont know but it is certainly misleading if this is the case and it doesn't advertise this. i simply cannot believe this to be the case. there must have been or probably still is Vista users that can use a fully functional PF2 version. Also have to say that PF2 is not really that much more complex than PF1.12 botyh have Dual Tone there is only some additional features and these relate more to MIDI functions than anything else. My PF1.12 works like a dream with Vista without issues - works in Dual Tone - everything works. I know Vista ain't the b's & e's but it aint that bad ,most of the updates have corrrected alot of its issues that it had on release
Edited - Sorry steve seemed to have misinterpreted you when i read it again it suggests that you are going backwards to early platform architecture such as XP to make PF2 work. that suggests that PF2 has no relevant or current Windows platform with which it will work? I think I would find this hard to believe!
Message was edited by: Whitie60
That's pecisely what I said.
I had my PC disected by my local independent (who specialise in building PCs for Audio and built mine in the first place). I opted for W7 and to be fair, the guys in shop shook their heads a bit 'cause it was, and still is to a degree, an unproven audio platform and Vista is known to be disatrous for audio specific PCs. While I had 2.2. running, it sort of worked but always crackled and sputtered with momentary graphics freezes. It turned out that the UX1/PF driver was not happy with W7 architecture and was causing off the scale CPU spikes. So, I rolled back to XP to stabilise it, 5 days before 2.5 was released, and we all know what happened then.
What remains to be seen, of course, is whether it's my motherboard or any other element of the hardware that the drivers are upset with, given that I have similar issues running 2.2 on XP.
So, as far as I'm concerned there is no stable version with W7. I can't help but feel that can't be right though. There must be people out there running PF and W7 quite happily, which brings me back to hardware...
Steve
Steve - I thought that i was onto something with the Global gate and A/B issue but that dont seem to have got any support for that theory despite it clearly being an issue with my versions of 2.02 & 2.01. There are questions over the Drivers as we have discussed. there are suspicions about the Hardware as well there may even be some Virus lurking in the Programme. L6 have been and are still being very silent and playing their cards very close to their chest in all matters and have not given neither credence to any theory nor rejected it either. they must be looking into it for some cause. I think their silence is just fuelling the speculation and we need an indication of as to where the problems lie.
Just to chip in Steve - I had been running Gearbox, PF1 & PF2 standalones & recording using the PF2 plugins for Ableton & Sonar with *absolutely no issues whatsover* on Win 7. From the discs in the box, to the upgrades when I registered, and every other software upgrade & driver worked perfectly up untill to the ones that arrived alongside PF 2.50.
On a bog-standard Lenovo laptop.
Judging by the posts on this forum, I've got a doubt it's your purpose-built PC that's at fault! ![]()
I just want one more pop at you pal - & thats to say that despite your defense of the L6 Support Guys you have to bear in mind that these guys do it for a Job. They dont have to waste their precious spare time worried about how messed up their Hobby/or even professional gear is. they dont have to waste their spare time trying to fix a programme with issues that prevent it running on their computer. I am sure they do have the best interests of the customers at heart and do worry about L6's reputation for providing a working product and a good service. i have every confidence that L6 Support will eventually fix these issues we are experiencing ( some of us) with PF2, 2.5, & 2.51. However what concerns me is that it may not actually be in MY Lifetime.
Let me try and make my point again...I will use very small and easy to understand words. Mkay?
The need for customer support is most certainly where you are at and absolutely have some very real issues with your gear that need to be addressed. Nobody doubts this as far as I know and I most certainly don't. In fact I feel bad that so many talented musicians are unable to use gear that they have purchased. This includes YOU
NOW my point, Pal...That will never change...things break and need repair or new releases are shipped with bugs and much needed bandaids. It is the way of the world. To act as though you and your grouping here were so important and powerful that Line 6 stop whatever it is/was doing and shut down whatever assistance they were giving other folks just to satisfy your technological needs is not only rude but selfish and arrogant.
I challenge you to go back to the start of this wahhhh fest of a thread and read with an open mind the tone and overall demeanor you all have been using.
QUESTION:
Lets say someone came up to you in the real world and asked you for a bit of help or assistance because you were well qualified to help in this arena! You asked what was wrong and when they finished their story, then told these folks that they were going to have to wait a bit because you were looking at this same problem for a few other people and didn't have an answer yet. Then without skipping a beat these people told you that they came to you in spite of the fact that you were a a lazy, stupid, uncaring jerk that doesn't care about peoples feelings and puts them last because you had better things to do.(it continues..)...Not only do you not care about peoples feelings but more blah blah .....would you help him or smack his lights out? I know the answer and so do you.
Grow up and have a beer...relax and hope that they get it handled soon...because they will get it...just maybe not in YOUR allowed time parameters.
Make more sense?
tldr - see comments regarding PMs. P.S. - Whitie,you were right - I guess I owe you a can of coke ![]()
Question to all: Does this forum have 'ignore' functionality?
Hope your guitar isn,t as out of tune as your sentiments! Get real man and stop being so sanctimonious & smug. Go play with - -- -- -- - -- -- your working version of 2.5!
Aaaaaand back to the troubleshooting now, yes? Dude shouldn't read this thread: http://line6.com/community/thread/63722?tstart=0 he'd probably have an anneurysm.
While I understand that my opening coment was indeed smug, I can not for the life of me see what you found offensive or wrong about the rest of my remarks. Did you bother to read them? Nope I didn't think so. Go on then! Continue to whinge and complain and stomp your feet, it certainly doesn't become you but it does seem to suit you. Can't even bring yourself to respond to my question? That is not surprising.
This is indeed a complete waste of my time. Trying to get a couple fellow musicians to act a bit more civil is not a reality when they have no desire to be so. I hope that when Line 6 gets you the help you need and makes you happy that you will at least have the decency to apologise for your over the top douchebaggery displayed throughout this thread.
So I went to that thread that it was said I would sponaneously combust if I read it and lo and behold I read through 5 pages and found the group to be civil and respectful all the while expressing their dissatisfaction with their issues. And that, of course, is understandable. here is a snippet of what I am speaking about. From the OP 3rd page
Re: Pod Farm 2.5 not working correctly, models missing
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...
Thanks for helping me make my point!!
Message was edited by: mcolquitt
lol.
Didn't read...Again. As stated previously, save whatever your comments are for PM's.
Either that or *let it go*.
Yes you did...you read it. ....I am dealing with children here! How sad!....*sigh*
look the only person that values your opinion is yourself. You dont have anything constructive to say about the issues with PF2.5 & 2.51. You only seem to want to critise and now insult people on this discussion. Isn't it about time you just gave up before making a bigger fool of yourself? L6 Support are supposed to help us deal with these issues & we have a right as dissatisfied consumers to ask L6 to look at these problems. Thats the whole purpose of these Support Forums for people with issues or questions about L6 products. Its not to aire your opinions nor to personally insult people. If anyone has got the wrong end of the stick about how to use these forums :then its you. You have said your bit now just go and annoy someone else.
Kelvis - lets get back to the issues about 2.02 & 2.5. Managed to get 2.02 running again. At the moment i am completely ignoring 2.5 & 2.51 because I dont really have confidence to put it on my system again. However after doing massive download of SP2 and additional updates that seem to come after its release another 40+ MB I seem to have it running again. But just let me say that the issues are the same and again revolve around the Global Gate & the A/B button in Dual Tone B. So nothing has changed but it at least rules out the Servive Pack issues with Vista. I had to do a complete un-install again. this time though i did a Computer Shut Down and Re-start after. This seemed to do the trick and 2.02 is running again in the sam,e state as it was before but its at least useable as liong as I avoid the Global gate when in Dual Tone. Sometime in the future I may try the 2.51 again when i can summon up some effort and enthusiasm to do it. AND WHEN I CAN FIND THE TIME.
Any more news about how your UX2 is progressing? I will be interested to see what happens on its return.
I spoke to someone at L6 Europe support this morning . Initially it was on other matters relating to the use of MIDI with PF2. then started talking about issues i am having with PF2.5 & 2.51. he suggested looking into system optimizations as he believed the matter might be specific to my platform and Computer.I had a look at this and most of them I have already done but one i haven't is the latency monitoring Tool by Resplendence. this would locate if there were any issues that might effect the sound in my Computer. anyone had any experience of this / would it be useful? I suppose I have to rule everything out. i will give it a try but if it comes back negative i will have to go back to suspecting the software application itself again. As I have said before this is extremely time consuming , repetetive & frustrating. Meanwhile both PF 1.12 works perfectly and so does PF2.02 to an extent if i avoid Global gate. I really cant believe its my computer but i will give it one more try just to make certain.
Hey Whitie,
Jebus, I just saw that dude posted something in BIG FONTS, so I scrolled past it again. BIG FONT = AUTHORITY, right? ![]()
Good to hear 2.02's working for you again - did you see this post? http://line6.com/community/thread/67626
Bloke says he managed to get 2.5x working by installing 2.00 first. You know, L6 support's replies have always stated to install 2.01 or 2.02 previously. Didn't even try 2.00 because of that.
So whaddya reckon? Time for more 'testing'? (I notice the L6 guys are actually just saying that outright now - 'Try this before testing'.) Who needs QA when you've got a customers who can do the job for you, huh? ![]()
That's my UX2 been away almost a week - another week to go...Then it'll have been 2 months all in I've been without the use of my L6 equipment. I've just got a horrible feeling that it'll come back with a big 'nothing wrong with this' sticker on it. Then I'll plug it in, and be back to square 1 with dry, unprocessed sound that support are unable to provide a workaround for me, and for many others with the same issue. To be perfectly honest, I've pretty much given up on any hope of anything being posted here (aside from a new software release) helping since I have a thread from the 5th of June http://line6.com/community/thread/65267?tstart=0 which received a stock reply on the 6th - and still has had no feedback or update 1 month and 2 days later.
As you already know, the amazing Serge @ UK Tech support (perhaps the dude you may have spoken to yourself) sorted things out for me in around 1 minute flat. Bit of a difference there. Guy gets respect because he delivers.
Edit, just seen your second post mate - again, like Steve Townend, I'd be very surprised if your system was causing the problem, since like me, everything else you throw at your system seems to work A-ok, as did PF 2.00, 2.01, 2.02.
Ah, wait PF 2.5x doesnt' work - it must be your computer then. ![]()
Kelvis -yeah BIG FONT SAYS IT ALL REALLY ! Anyhows I see you have earned that title of 'Mad Scientist ' again. It seems to me that you are missing this whole experiments thing now you are Ux2 less. what are you doing with all this Time you now have? yes when I can summon up the motivation and energy i will give it a Go i suppose. When i get the time. at the moment my partner is on the verge of divorcing me because of the amount of time I dedicating to resolving the L6 2.5 & 2.51 issues.However that aside it is interesting that this be the case. i really dont know why 2.00 should be any different to 2.01 or 2.02 though. can you leave these on the system whilst you have 2 or even 2.51 on your computer or do you have to take them off first? it was also interesting that the guy who wrote that had problems as a new customer to PF2. i too had not had any previous version of PF2 before I downloaded 2.5.
I know really thats its not my Computer and anyone with any powers of reasoning would say the same because you are right throw any other combination into the mix and my computer comes up smelling of Roses. i am just going through the motions so i dont get any more Cut and paste replies from L6 Support which puts the blame on everything but themselves. the Product was not developed enough for release at the time it was released and anyways you look at this is the case. looking for Support for the L6 support Guys you have to ask who and why have put these guys under such pressure - the answers lie closer to home and less about the customer pressures being exerted in such Forums as this. i really hope this fix does lead to resolution before my relationship falls apart!
Mad scientist? I'm the *maddest* mate ![]()
I think the fella who got PF2.51 to work done it by installing the later versions 'over the top'...Would kinda make sense if there's something that should be in your system (perhaps installed by 2.00) that isn't there with 2.5x. I'll give it a whirl when my UX2 gets back (if it still gives dry sound only on 2.5x). Hopefully, I'll plug it in and all will be well.
In other news, I'll hopefully win the lottery this week! Nah, to keep myself busy I swirled a strat for a local studio's wall:
Want one? ![]()
fantastistic - love one mate. thats where my heart is: psychedelia. Shows there is sometimes much better stuff we could be doing than getting PF2.51 to work!
I'm sure we could work something out! P.M.d ya. ![]()
just to update. i have now completed all the Vista tweaks recommended. i have also downloaded the latecy monitor tool by Resplendence. the monitoring tool said that my computer appeared to be Good and certainly adequate for Direct Sound monitoring purposes. no issues identified in respect of latency. I did prts 1-3 of the tweaks and i did notice some improvement in respect of issues with Global gate and the A/B. Some of the patches worked ok in the Tone B setting with Global gate on. or at least there was a noticeable improvement in PF2.02. However this was not consistent in all patches. There are still some patches and fx chains in Dual Tone Mode that have not responded to any yweaks. In fact one of the patches ( presets) which is one of my own I should add when i have a Global gate on and in Tone B of the Dual Tone it simply refuses to allow any sound at all to pass through. Then if i go back to Tone A with the A/B button it still has no sound. This preset appears to be behaving different again. I am now suspicious that this matter may be something to do with the fact of the presets history which may be in PF1.12 where I first made it. however i dont know and this matter needs to be checked further. last night I completed all the tweaks by completing part 4 of the Video tutorial. I have not yet tested if this has had any further effects on the sound & Global Gate issues. However before I did this ,and after completing steps 1-3 of the Video tutorial, my DAW was working ok. After completing steps in part 4 it is no longer working and keeps on telling me that an Error has occurred setting these parameters and that No audio outputs have been selected. In my DAW it states that I have selected the outputs. OUTCOME - now cant get any sound from the samples io recorded in the DAW. I dont know whether there was anything in Step 4 which would have effected this but it seems a bit suspicious that it was working ok before i did thetasks in Step 4. Now I have to go back and check what I did and possibly undo it bit by bit to see if i can get my DAW working again.
Given the improvements I feel that I now must go and check out 2.51 by putting it back on my machine again. Does anyone know if I have to uninstall the PF 2.02 first or can I leave it on my machine without having to uninstall before 2.51? Or to put it another way can 2.02 co-exist with 2.51 without having to first uninstall 2.02?
Hey Whitie60,
We went ahead and resent the ticket information.
An email will be sent to you from Line 6 containing a link if a Line 6 support representative determines that a ticket is necessary to troubleshoot your issue. Please follow the link in the email to view your open ticket to work one on one with Line 6 Support.
I think it's a very simple thing: Line6 employs horrible programmers and when it really comes down to it, because of that, I see them unravelling at the seams. I know that because of this ordeal I will no longer be using Line 6 products. I've reinstated an older interface that is at the very least reliable in doing what it is supposed to do.
With Line6 you pay for a product that provides a certain functionality and Line6 cannot provide proper software to insure that functionality. Am I wrong in saying that we've all been ripped off?
Thanks but no thanks.
Hi,
If you are planning on installing 2.51 again I would definitely recommend completely uninstalling POD Farm 2.02 first:
Completely uninstall both POD Farm 1 and POD Farm 2 using the Line 6 Uninstaller within Programs/Line 6/Tools folder before installing 2.51.
Thanks,
David
Line 6 Customer Support
Got 2.02 working sweet. Tried 2.51 . Firstly my saved download just stopped responding all the time when it gets to the bit connect to internet to let C++ redistributable work. tried 3 or 4 times all the same. Did a download of New version Monkey which then ,when I used it ,kept on telling me that it could not connect with L6 Server said it was downloding when it clearly wasn,t. After about 1hr and half of trying gave up and put 2.02 back on system. oh and yes my Internet Connection was working all the time as i tried it to make sure. It also appears that the Licence Manager was on the system as a result of the Monkey download. again these dont seem to be speaking to one another . It appears to me that each time the Licence manager is on the system there is a conflict. i think I will have to face it this version of PF just dont want to work with me or my equipment. i can see no reason for the program exe not to work in the way it was intended without having all these problems. all other saved versions of the PF are able to work from the program exe setup request but this one refuses to behave in a similar fashion. One other thing I did before i got New Monkey was to try to update and older version of Monke. I think i had 1.4. before the newest version. when I did the update to Monkey it took absolutely ages. i decided to abadon it at half way as it had altready taken almost 30 mins by then. i went to the L6 site and got the New version of Monkey 1.41 in a matter of 2 mins flat.
just thought I would add this which is a reply to sound issues I posted into another discussion -
I managed to get 2.02 working without sound issues. I did this by working through all the recommended Tweaks for Windows & Vista PCs. One that made the most difference but was not included in the tweaks was the Disable Wireless Adapter done in the Device manger section of Windows. That has made alot of improvements for me. it solved the issues I was having in Dual Tone when using the Global Gate and A/B buttons. i thought that this might help for when I moved back up to 2.51. however when i have tried to load and exe the 2.51 programme i am running into difficulties in getting it to load onto my system. this seems like a new problem now and so far i have had no sucess but wasted alot of time on it. I really dont know whether I really want the 2.51 now as 2.02 works so sweetly. My advice to you if yyou are on Windows based platform would be try the tweaks. Some are not for me like disabling User Control and switching off Screen Saver however some are good such as switching off Indexing etc.
Did a reinstall of the Pf2.51. Due to problems with C++ redistribuatble L6 Hugo suggested that I leave out the RTAS sections as they were not essential. Did this & got it onto the computer. Tried Standalone did work slightly better than before. Less Pops and hicupps. But some remain whereas 2.02 has none at all. Problems again are worse when using a Global Gate with A/B. Tried settings with different size of Buffers but nothing worked that well there was always some pops & hicupps but much less than before probably due to the tweaks I have worked through. Nothing gets rid of them all & thats what makes 2.02 superior because it doesn,t put you off while you are playin. Tried Plug ins with my DAW and these all work perfectly. Confusin ain,t it! Yes they worked with no pops at all. Therefore in my HUMBLE OPINION I HAVE AGAIN TO START SUSPECTING THESE DRIVERS THE 4.2.4.4. These are used to communicate with my UX1 and this is where I have the problems in Standalone when I am not communicating with the UX1 then things run smoothly.
Support Tickets are not working - they are refusing to update. Alsoi since changes made to the Community it has been difficult to post any replies to the Discussions going on!
+1 to the support tickets not updating...I've got a bunch of info for Line6 Hugo that I can't add to my ticket anymore.
Counting down: 25 days left on my warranty.
Status: UX2 not worked since 5th June.
Sorry guys, something happened to the ticketing system since last week. We are currently working on it, hang tight.
Regards,
Line6Hugo
Hey Hugo,
Thanks for the update
- I managed to speak to Serge again this morning and he added some further info to my ticket that I had for you. Actually just mailed him some more there...
"Just to confirm I tried the UX2 on a different internet connection (BT Internet) than my own (BE Unlimited) – plugged straight into the router and attempted reinstall firmware/de-authorize/re-authorize using different USB ports each time...Same result: 0xfe from server – forbidden."
So now I'm back at the 'de-authorized' stage with no way of authorizing the thing.
![]()
Hi,
At this point, I recommend you contact the ISP to make sure there is not a firewall blocking the port/connection.
http://bt.custhelp.com/app/contact
Are you experiencing any other programs or wepages that are giving you issues similar to this one?
Thanks,
David
Line 6 Customer Support
Hi David,
I already contacted my own ISP and they confirmed they do not block, limit or firewall any ports - using a program called 'Netlimiter' captures and displays data going between Line6's servers and my own connection. I had included this info on my support ticket, but we can't update them at the moment so I fired the info up here.
The info above was a test on a different ISP than my own, and of course the same problem exhibits. I have no other programs or webpages that give issues anything like the above.
I think the ISP factor can be ruled out ![]()
Support Ticket updates are working again folks ![]()
As I said in my first post the 2.51 is a Botched fix. I have been working with L6 support through my Support ticket and the result has been that 2.02 works just sweet but 2.51 is non functional for Sound in Standalone mode however as a Plug in it works without issues . As it stands L6 are now suggesting that I go back through all the back catalogue of Windows Updates to see if I am missing one somewhere(they dont specify which they are leaving it up to me to fin that out for myself). Well thats just ridiculous and a waste of my time. I have already updated to Windows SP2 a massive download and the fact that 2.02 works already with all the updates I have made just shows that this is not the case at all. They dont specify what downloads /updates need to be on the system they are basically asking me to do all updates which is ridiculous and smacks of really not having a clue.Also would say that in general my Puter is pretty much up to date i do take updating very seriously.
In reality I am happy with 2.02 as I wanted to buy into the PF 2 and getting the 2.5 was the only way in which to do this as it was not possible to buy a earlier version because to use PF 2 you have to buy the 2.5. I am slightly dissappointed that 2.51 did not work in the way it should but at least I have one working version of PF2 that works in almost all I want it to do - so I have no regrets in purchasing the PF2.5. I just wish they knew more about why the 2.51 would not work for me. It is obvious that L6 need to work on these issues and find out why 2.51 works for some and not others until they do I just can,t be bothered to waste any more time on these issues.
As I said in my first post the 2.51 is a Botched fix. I have been working with L6 support through my Support ticket and the result has been that 2.02 works just sweet but 2.51 is non functional for Sound in Standalone mode however as a Plug in it works without issues . As it stands L6 are now suggesting that I go back through all the back catalogue of Windows Updates to see if I am missing one somewhere(they dont specify which they are leaving it up to me to fin that out for myself). Well thats just ridiculous and a waste of my time. I have already updated to Windows SP2 a massive download and the fact that 2.02 works already with all the updates I have made just shows that this is not the case at all. They dont specify what downloads /updates need to be on the system they are basically asking me to do all updates which is ridiculous and smacks of really not having a clue.Also would say that in general my Puter is pretty much up to date i do take updating very seriously.
In reality I am happy with 2.02 as I wanted to buy into the PF 2 and getting the 2.5 was the only way in which to do this as it was not possible to buy a earlier version because to use PF 2 you have to buy the 2.5. I am slightly dissappointed that 2.51 did not work in the way it should but at least I have one working version of PF2 that works in almost all I want it to do - so I have no regrets in purchasing the PF2.5. I just wish they knew more about why the 2.51 would not work for me. It is obvious that L6 need to work on these issues and find out why 2.51 works for some and not others until they do I just can,t be bothered to waste any more time on these issues.
Whitie60,
POD Farm 2.51 seems to somehow be problematic the way you describe (getting pops and clicks within POD Farm 2.51 standalone only after trying many of my recommendations that cleared up all of your other problems except the pops) only on your specific computer system. As we have had many thousands of downloads of this latest POD Farm 2.51 release, we do not have a flood of people having the same problem.
Your specific problem is isolated to your computer system. This is why I opened a support ticket to help you 1-on-1 with this problem. At this point, it seems highly likely like there is some conflict on the system that is causing these audio artifacts.
Sorry for all the trouble you have had with these latest releases, but I'm glad you are at least able to use the POD Farm 2.02. I have left you new message within your support ticket.
Regards,
Line6Hugo
i highly recommend getting and running slim drivers from here: http://www.driverupdate.net/
it's free, but it will update chipset and other non-obvious drivers that can have a dramatic impact on usb performance.
Hey Zap thanks so much for the information and link to slim drivers. I downloaded and ran it and was able to update 12 important system features that I didn't even know needed updating. I wanted to wait untill I used the system with it's updates before responding. I have had enough time now to recognize how badly these updates were needed. System is running tip top with thanks to you and your excellent find!. Thanks very much.
Mark
thanks for the feedback, i personally noticed improvement when i used it... and it's nice to know that others will find it useful as well.
I just dont get how Podfarm 2.02 can be so different from 2.51 in Standalone. As I said 2.02 runs sweet on my Computer now with no issues. Can 2.51 be so different and what makes it so different to the point where it dont work correctly in the Sound department? My computer is not temperamental and all previous versions of PF have run ok with it.
I have encounter the A/B box and gate problem too. I have notice that appears only with pod Farm standalone. I have check the DPC and I Remark that the DPC increase significantly when we got all condition together.
I have some PoPs and Cracks with my UX2, but it comes from my wificard! When I switch off my wifi card, there is no pops remaining.
Find a DPC latency checker and test you computer without your UX1 connected. If you find a high DPC latency, the probleme come not from your ux1 but come from another deficient driver.
PS : English is not my mother tong, so excuse me for my misstake (i'm french)
Yruama - your English is good my friend. I understand. What version of Podfarm have you been using is it 2.5, 2.51 or 2.02? My issues with the A/B & A+B plus the gate seem to have stopped since I did the tweaks and in particular the tweak related to the Wifi card but that only applies to use of Podfarm 2.02. However my sound issues with 2.51 continue even after the tweaks made.
Have to ask what is DPC as i have said I am not too much into Computers other than what i have had to pick up to use Podfarm. I have done a Latency monitoring as advised and that turned up that my computer appeared to be ok to use for direct sound monitoring
In fact, I have notice this problem since the 2.02 version but I didn't pay attention (I didn't use the A/B box often in this time). In fact, I was testing (ver 2.5) a dual tone picked up from net when I have understand they should be a problem (other than the wifi). In this preset, passing from A+B to A or B alone causes a crappy sound (sounding like a big CPU overload).
So I trying to solve this problem by updating many things ( Windows, Pod farm2, UX2 driver). And finally I started to search for this particular problem. I have open a new thread because I found nothing ( I didn't use the right keyword
). By chance, I have find a link to your thread.
Have to ask what is DPC as i have said I am not too much into Computers other than what i have had to pick up to use Podfarm. I have done a Latency monitoring as advised and that turned up that my computer appeared to be ok to use for direct sound monitoring
If you monitor your DPC lantency and your CPU usage, you should see a big difference when you use Podfarm 2 with conditions of bug. (you must obtain a big DPC latency and a significantly higher CPU usage).
Wow !, I thought that the probleme was limited to the standalone version, but I have just check CPU usage of plugin version (using performances meter of reaper).In the same condition the CPU usage of plugin increase significantly but in this case it's not enought to do CPU overload on my computer
I'm wondering if anyone on here ever got their problems actually resolved with Pod Farm 2.5.1?
I called and talked with tech support before I purcahsed the thing. I still have the old Toneport DI-S box (came bundled with Gearbox software). I was told PF 2.5.1 would work with it. Well, it does work with it through the USB connection. However, the latency is terrible!
Howver, with my Gearbox software I can use the microphone inputs (with a connection from the line out mono port on the back of Tone Port DI-S box) and it works great! I have zero latency!
Pod Farm 2.5.1 I thought was supposed to be "hardware independent." So, it looks like it would also give me a choice to use the mircophone input as the device to capture the signal from. But it does not! The only choice it gives me is to listen through the USB connection and no matter how many steps I follow (and I've done everything I can find on this website to do), the latency is so bad I might as well just forget it.
Wish I had never purchased it and am going to contact the bank first thing to dispute the charge and uninstall the mess, if I don't see some solutions before weekneds over.
Very upset. Wish I had read all of the complaints on here before I purcahsed.
Stay in the mix and in the know.
Latest offers, special deals and insider updates.