Jump to content

OmegaSlayer

Members
  • Posts

    63
  • Joined

  • Last visited

Profile Information

  • Registered Products
    2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

OmegaSlayer's Achievements

Enthusiast

Enthusiast (6/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

16

Reputation

  1. Yeah, you're right, it's a lead guitar tone, snapshot 1 was the rhythm associated with that lead tone, but it's really of no use, so I should always active snaphot 2 after entering the preset
  2. I need to move snapshots. Or better I need to "erase" snapshot 1 and substitute it with currently is snapshot 2. Is there a way that I didn't manage to figure out using PodGo Edit? Thanks
  3. Unfortunately you will have to wait quite a good bit. Going through all my presets is painstakingly long and I must find the actual time to do it
  4. I have mainly brought every patch to the same volume, by ear, not with a DAW (but I think I'll have to resort to that), and every patch is well above +5 db. PodGo knob is between 9 and 11 o'clock and the Headrush is at 2 I think. Honestly I feel like I did everything wrong...will have to take a day and set up everything again with a DAW
  5. I was wondering what you guys think yelds the best results sound wise. Do you prefer to crank the PodGo volume up and turn down the volume of the amp/pa, or do you prefer the opposite, turning PodGo volume up and amp/pa down? Unfortunately I can never crank up the volume high enough to perceive well the difference, but what I hear is enough to say that there's quite the difference and that PodGo volume down kills stuff like reverb and delay much more than turning the pa volume down (I use an Headrush 108).
  6. Geez, more intensive than the Horizon drive...
  7. I've noticed there's some Legacy stuff that is not in the Pod Go...I think the Legendary Drive or Prince Of Tones for example Does anyone know the reason?
  8. 6 months Development limbo? Development hell? Development pregnancy?
  9. Kind of funny that he replies on the gear page but not here
  10. Line6 dealing with v1.40 bugs
  11. It's like someone that should start a diet :D
  12. "And even this week, the update will be released next week"
  13. As the process derives from the ticket I filed here on support, Line6 knows who my tech is I hadn't realized until I went to the lab (which lately changed address and name) but I have known him for 29 years, and I don't want to put him in troubles My unit hasn't been replaced, it had the same scratches and it wasn't restored to default, my presets are all there I repeat myself, 7 minutes clocked, I phoned my girlfriend when I left the lab, then after 7 minutes I got his call to go take the device back That's how I know it has been 7 minutes, from the phone calls tab 7 minutes for me is: unscrew the device > unsolder part > solder back the part > reassemble the device > try the device The problem is not "impedance" as a whole...but part of it And yes, L6 should come forward with the acknowledgment of the problem as it seems so very easyto solve @voxman55 "Line 6 should be upfront with its customers and shouldn't have anything to hide. " "Circuitboard copyrights" was the reply I was given
  14. Techs are under non disclosure agreement I suggest that IF someone gets to know the issue, they keep for themselves because they put at risk the exclusivity service of the techs Capisc'...
  15. Filed a ticket on Sunday Got an OK from Line6 Monday, late afternoon Contacted the local repair service immediately Got a reply this morning (Tuesday) Brought the device in in the afternoon, walked away with the problem solved, 7 minutes later ...wish I could say more...
×
×
  • Create New...