Jump to content

cristofe

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cristofe

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    3

Recent Profile Visitors

226 profile views
  1. cristofe

    Missing Models

    I have a Pod X3, Toneport DI Gold, GearBox and PodFarm.....Sooooo therefore I have ALL model packs and ALL models available....in THEORY. Why then when I try to open certain patches I created on my X3 I get error messages in GearBox & PodFarm stating that models including "script phase" and "v-tron" are not installed. They fail to load and I get this error message: (Code 8000a002) Accessing a model that hasn't been added And, of course, I'm not alone in this frustration. What gives?
  2. If you like the GUI....fine. I'm happy for you. I don't. I've been DEEPLY involved with the development of both hardware and software ampsims and VST FX development since DAY 1. Some of you were probably in diapers then. You're entitled to your opinions as I am to mine. I've owned many Line6 products....I still have an X3 I use on occasion. But quite frankly, I have various hardware & software products that IN MY OPINION sound better and and are more user friendly than Line6 products. That being said, I will admit that Helix is a step forward both in terms of sound and hardware/software integration and the patch handling system is somewhat improved. If Line6 had gotten on the ball and made the Pod X3 compatible with PodFarm2 they MIGHT have kept my business.....but no they NEVER released a dedicated editor and forced us to use the already very outdated GearBox. I've moved on and I'm glad I did. Have fun with your toys boys.
  3. "UMNN....DISAGREE...A LOT" That's all you've got?? Wow....that really eloquently states your case. Care to explain yourself? The GUI is amateurish compared to even LINE6's earlier work. Symbols & sliders?? WTF?? It looks like something cobbled together in Synthedit. Tiny little pics of the hardware that can't be accessed and/or tweaked?? Super tiny text that causes eye strain after 10-20 minutes. Sorry....you need to come up with a better argument than that. IMHO the GUI sucks.....I given plenty of reasons why I think so. What are your's for disagreeing with me?? Oh or are you disagreeing with me that the software isn't worth $400 to non-hardware owners?? How would I know seeing as how you're too lazy too clearly explain yourself?
  4. And THIS is the best GUI you can come up with?? Even 'ol Gear Box had a better GUI IMHO.....REALLY dislike this one. And $400 for non-Helix hardware owners?? Good luck with that. IMHO there are much better values in VST ampsims....that are ALSO standalone.
  5. I've got some more news for you.....the latest drivers 4.2.7.4 also break the X3's ability to connect with POD Farm2 in Win7!! Same as all drivers in Win10....the X3 is recognized in MIDI but no ASIO. Fortunately, rolling back to 4.2.7.1 fixes this in Win7....but not in Win10.
  6. Ok, thanks......that's some good news. :)
  7. I get it.....but sometimes the line between reasons and excuses is finer than the line between art & garbage. :rolleyes: Any chance of THIS getting fixed? This update adds support for Windows 10. Due to a driver incompatibility with Windows 10, the following devices will not operate with the POD Farm stand-alone application in ASIO host mode: PODxt series PODX3 series PODHD series
  8. Yes, Gearbox does work.....BUT..It's not a DEDICATED X3 editor. Just tacking on X3 support and mothballing Line 6 Edit was a poor decision IMHO,(and many other users as well). http://line6.com/supportarchive/thread/20704/ Compared to PodFarm, GearBox's GUI is rather clunky. Even the lowly Pocket Pod had it's OWN DEDICATED EDITOR. After doing a bit of research, I've found that I'm far from alone here. But lack of better editor is comparatively minor. Allowing a break of compatibility between X3, & PodFarm2, the inability to load SOME files with the EXACT same file extension is not only ridiculous it's irresponsible IMHO. I'm of course using the latest drivers and most recent,(i.e....quite old), version of Gear Box. I am now "sifting" through thousands of patches.....a total PITA and waste of time that should not have been necessary Oh, and now that I've upgraded to Win10 I can't even use PodFarm1 with X3 as they do not work together under that OS. That being said.....Line 6 makes some great products....I've been a user for decades. But this constant half-baked mentality off....well, it's good enough let's move on....is simply infuriating. I realize that new products need to be developed and released. I realize that no company can provide indefinite tech support for legacy products. But Line 6 really left users holding the bag on this one. PodFarm2 COULD have been properly coded to work with the X3. It STILL could be. There should also be SOME way to "fix" .l6t files that have been corrupted by PF2. And speaking of PF2....HOW old is it now?? You guys have been making some great leaps with the hardware.....but you've really dropped the ball with the software.
  9. WOW!! My mind has been completely blown. I sold my PODXT and "upgraded" to an X3. Yes, there are some things I like about it. But the fact that it will not open MOST files in it's OWN NATIVE file extension .l6t is about the dumbest most frustrating bunch of BS I've ever encountered. After a lot of frustration and research I've come to find out that if an .l6t is opened/edited/save in POD Farm it is completely unusable in either Gear Box or the X3. It's going to take me weeks sift through the thousands of patches I've collected and created to find the few that still work. .....EPIC FAIL LINE 6!! AND as if that wasn't bad enough......I then find out that upgrading to WIN10 totally breaks the X3's ability to work with POD Farm in any way at all. And it's not like the X3 ever really had a proper editor in the first place......but, of course, all of this typical of Line 6. I honestly don't know why I bother with this stuff anymore.
  10. Ok, maybe this will help some other users with this problem. There is DEFINITELY something wrong with Line6's coding. It's either the current firmware or the drivers. Even tho I loaded my PODxt with Line6 FACTORY patches from GearBox I was still getting a MIDI timeout at 44%. However, being that it changed from 21% to 44% after loading said patches, it occurred to me that there must be some compatibility issue between the patches and the software. Now, mind you, I NEVER had this problem before installing the current update. Soooo I re-flashed the firmware one more time BUT, this time, I allowed the update to install the factory patches that came WITH THE UPDATE. And GUESS WHAT?? No more MIDI timeout!! Now that's all well and good provided I NEVER load ANY other patches. But, apparently, some older patches....EVEN THOSE WRITTEN BY LINE6!!.......are NOT compatible with this version of firmware/drivers.
  11. I'm really getting sick of this BS. I've tried everything. I've successfully re-flashed the 3.01 firmware. The MIDI timeout continued to occur at exactly the same point timing out at 21%. So I thought perhaps this was being caused by a corrupt tone from the user library. Sooo, one by one, I loaded the unit with factory patches in GearBox. This caused a change but did NOT solve the problem. Now the MIDI timeout error occurs at 44%. This happens at EXACTLY the same point whether connected via MIDI or USB and it happens at EXACTLY the same point on THREE pc's and THREE OS's. It SUCKS not being able to load and save bundles but least GearBox allows me to edit and save individual patches.....Line6 Edit isn't working at all.
  12. Well....the Monkey may not have permanently bricked my POD but there is still a severe lack of joy here. The latest drivers/firmware/monkey are still messing me up. EVERYTHING worked just fine before updating. But NOW, even after solving my POD's "Invalid Code Error 1" bootup message, Line6 Edit no longer works properly. It recognizes my POD but will not complete sync. And there's nothing wrong with my USB cable, it's not a USB hub problem.....EVERYTHING worked fine before the update...NOTHING else has changed. I also tried connecting via MIDI AND USB on three different machines and on three different OS's. I even tried using Gearbox. It DOES work.....partially. I can send and receive single patches but it still times out when trying to load the POD's memory. I've tried just about everything....uninstalled/reinstalled EVERYTHING, rolled back drivers and Java....nothing works. I REALLY wish I'd read all the threads about this out there BEFORE I made the mistake of updating my POD. I am FAR from alone in this boat.
  13. Well....the Monkey may not have permanently bricked my POD but there is still a severe lack of joy here. The latest drivers/firmware/monkey are still messing me up. EVERYTHING worked just fine before updating. But NOW, even after solving my POD's "Invalid Code Error 1" bootup message, Line6 Edit no longer works properly. It recognizes my POD but will not complete sync. And there's nothing wrong with my USB cable, it's not a USB hub problem.....EVERYTHING worked fine before the update...NOTHING else has changed. I also tried connecting via MIDI AND USB on three different machines and on three different OS's. I even tried using Gearbox. It DOES work.....partially. I can send and receive single patches but it still times out when trying to load the POD's memory. I've tried just about everything....uninstalled/reinstalled EVERYTHING, rolled back drivers and Java....nothing works. I REALLY wish I'd read all the threads about this out there BEFORE I made the mistake of updating my POD. I am FAR from alone in this boat. Everything looks fine in the Monkey but no Line6 Edit:
  14. Good to know......thanks. I wish support had suggested this to begin with. There is clearly some sort of glitch with the current software versions and online updating procedure when updating PODxt's. After much research online it's apparent that more than a few users are ending up with the dreaded "Invalid Code Error 1".
  15. Alright...I got the RMA# from line6 and I was getting ready to send it back. BUT...I had to convince myself that I'd truly exhausted all possibilities before paying for shipping and giving up my unit for who knows how long. So first I tried to do the firmware update on another machine. Same results. NO JOY. I was about to throw in the towel when I remembered a little factoid from earlier years in line6's evolution. There was a time, in the dark past, when the aforementioned !@#$% MONKEY allowed us humble end users to update our firmware OFFLINE with the "update from file feature." In their infinite wisdom line6 decided that the end users were either too incompetent or too lazy to do a manual update so this feature was eliminated in the !@#$% MONKEY thereby forcing users to update online....ok, get the picture? I searched the high and low and finally found the firmware FILE: PODxt_3_01.xtf and an outdated version of the !@#$% MONKEY that would actually allow me to USE the file....AND GUESS WHAT?? My PODxt is now fully working!! PRAISE JESUS it's FRIGGIN' MIRACLE!! Not only did the MANUAL firmware update unscramble my POD's memory chip but, apparently it MUST have re-soldered that cold solder joint that line6's tech was so certain was the cause of my POD's failure. In any case....in closing...kudos to line6 for willingness to attempt to make things right. MUCH appreciated.
×
×
  • Create New...