Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Teerexness

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by Teerexness

  1. 2 hours ago, voxman55 said:

     

    Something sounds very wrong, as the Pod Go tones are quite frankly excellent and (up until the latest Helix v3.1 that has a slightly higher sampling rate) has exactly the same modelling.

     

    Are you on the latest v1.22 firmware?  

     

    Exactly how are you using Pod Go? Headphones, powered cab, amp? If the latter, what amp and are you going through the fx return, 4 cable, or front end? If headphones, what model?

     

    If Pod Go sounds that bad with everything, I can only think you must have a faulty unit particularly if you are using Helix with no problems. Go back to the store and ask them to check it, and if it is defective request a replacement. 

     

    I use Pod Go with Audio Technica ATH M50x headphones, through a Headrush FRFR108 powered cab, and through the fx returns of my Laney Cub 12R 1x12 all valve combo and Mk1 Marshall 1x12 80v '8080' Valvestate.  It sounds really good through all of them and its particularly stonking through the FRFR108. 

     

    I'm a live gigging player so am not a 'recording/studio' guy and the only thing I've put together was a very simple recording of a patch where, based on an idea by someone who posted a patch on Line 6 Custom Tone, a used a Soldano Clean amp model in a single patch that could cover a whole range of tones from cleans through to rock eg for a covers gig. It's not an amp model I'd have thought of using but it was an interesting experiment.  There are 4 snaps plus a chorus to kick-in.  Try the patch out in your Pod Go (https://line6.com/customtone/search/?submitted=1&family=pod_go&search_term=Soldclean+SCsnap ) - if it doesn't sound like this then there's definitely a problem somewhere.  

     

     

    I'm just using the headphone out into a Midiman mixer and out to a nice set of Logitech computer speakers. Exactly the same as my POD 2.0 was, and it sounded great. On the POD GO pretty much every patch has a little or a lot of that terrible digital distortion sound when I play hard. The only way to stop this it to turn the drives and gains down so far that it sounds ridiculously weak. Also, the output EQ sounds it going through a tin can. Very artificial and metallic. Like everything is some variation of The Kink's "You Really Got Me". I'm trying to be patient, because I despised the POD HD and the Helix when I first got them also. But I don't seem to be able to edit my way into loving this little unit. The POD 2.0 it replaced sounded so much better, and that's pretty sad for a 20 year old unit.

     

    Aha! It was a bad cable! No wonder. I loaded your lovely patch and it sounds perfect now. Thanks!

     

    • Like 1
  2. I have the same issue. I got my POD GO yesterday and I can't get it to sound anything but....broken. The overdrive and distortion all sounds very unnatural when the sound decays. Like all the amps have a bad tube or a broken speaker. All of them!? I've tried it with two different guitars and many presets. My own, the defaults and ones I downloaded. Same exact rig that I've been plugging a POD 2.0 into for years. And it sounded MUCH better. I have a Helix floor at my studio, so I know how to build presets and what things SHOULD sound like. And this aint' it!

  3. I am using the original Helix floor model. Lots of holes on the back!

     

    I'm assuming you have the big Helix and not the LT. If that's true then connect one FX loop send from the Helix to the Leslie's  input and then connnect the two outputs to two of the FX loop returns on the Helix. You then need to program that input and those outputs to where you want them in the patch's path.

  4. Both my Variax 500s work just fine with the Helix. Model changes in Helix presets work great, the VDI cable works just fine, etc.. The one thing that doesn't work, and it doesn't seem like it would have been so terribly hard for Line 6 to have supported it, is using the Helix as an interface between an older Variax and the original Workbench software running on your computer. 

    So, if you need to use the older Workbench software, you can use a POD HD500 (or 500X) or Firehawk etc., or the original interface that came with Workbench. Save your changes/tunings to the custom preset slots and then move back to your Helix. 

    So your older Variax should work fine with the Helix, but not for editing in Workbench. If you are like me, this isn't a big deal. 

  5. What happened to the tuner on this thing? It was never great, but it seems like it's nearly unusable since Firmware 2.20. Sometimes it works, sometimes it's deaf as a post. And deaf is it's default reaction to my Variaxes. It's also flat. I can recheck using SteadyTune on my Mac, and a great little Korg tuner I've had for many years, and they both show that it's consistently flat.

     

    I nice, convenient feature, with a lovely display has become nearly worthless!

  6. What version of Helix Edit are you running on your Mac? If it is not also v2.11, that could be your issue. Also, firmware 2.12 is out, but the latest editor is 2.11

     

    The Edit version is 2.11. And since things seem to be trending downhill regarding stability with firmware updates, I think I'll skip these for a while. Thanks for the suggestion though.

  7. Every time I try to import a bundle (that I have to reload due to the ridiculous reset process required after a Helix firmware update) the Helix app crashes. Restarted the MacBook, restarted the Helix, same thing. Every time. Not cool.

     

    Helix firmware 2.11 and Mac OS 10.12.3

  8. Yes they could. But then how far into the beta do you wait before you can say this is near to what will be released? Should Line 6 (and everyone else for that matter) be writing drivers only to have them useless with the next beta version, wasting useful time and resources? Personally, if I was a software developer I would either have a dual boot or more likely a dedicated machine for work.

    There are testimonies of people right on these forums who were aware of a problem in their own, non-Line 6, endeavors in the pre-release versions of El Capitan. They found it. The problem probably didn't change much. And from what I can tell, everyone is having trouble with a final release of El Capitan. I think is a time for humility from those representing Line 6 and patience on the part of Line 6 users. Doing a superior dance regarding the wisdom of early adoption of a long awaited, major company's final release OS, or trying to distract by pointing fingers at other company's supposed incompatibilities doesn't seem very helpful. 

    • Upvote 1
  9. Radical thought: how about not updating your OS? That's the free option and works for sure.

    Here's another radical thought. Perhaps Line 6 could have gotten involved with some of the pre-release developers versions of El Capitan, found the problem and had an update ready at or even before OS 10.11's official release?

    • Upvote 2
  10. Since updating to the latest USB Firmware and Flash memory updates on my POD HD500, I can't switch between patches using "FS5" through "FS8". I can step on the UP or DOWN switches, and once my patches are displayed in the LCD, I can step on the appropriate foot switch, and it will switch then. That's obviously incredibly clumsy and too slow in a live situation though. 

     

    Did anyone else have this issue, and if so, were you able to fix it?

     

  11. Mac OS 10.11 "El Capitan" is a thing of beauty and has improved the performance of everything I've used since updating. Meanwhile, my POD HD can no longer pass audio through USB. Given the fact that updates via "Monkey" have been less than sturdy since day one, and the last POD HD update from Line 6 destroyed the normal functionality of the foot-switches on my POD HD500, I'm going to lay the blame at Line 6 on this one. Were they unable to participate in the normal pre-release compatibility testing program that all the other developers seem to have successfully gone through with flying colors?

  12. Having the exact same "no device" issue. I've only had this thing for a couple of weeks, and since I (fortunately it seems) bought it as a sound source for my POD HD500, I hadn't taken much time to play with the Amplifi sounds. Now that I have, I'd say the default patches (since I can't access anything else) and the iOS app (since it won't transfer patch settings to the Amplifi) can only be described as garbage.

     

    There are other full range solutions I could have used for my POD HD. I gave the Amplifi the nod due to it's stand alone capabilities. Capabilities that don't appear to exist.

  13. I had the same problem. It turned out it was caused by a need to update the Line 6 Monkey software. And I have NEVER in 4 years been able to update Line 6 Monkey without incident. You'll need to download it directly, instead of hoping that the ever-wonky Monkey software will be able to update itself. It'll probably throw out erroneous reasons why it can't do that, so here is the direct link.

     

    Free Download

×
×
  • Create New...