Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Registered Products

Recent Profile Visitors

379 profile views

wahwahferrar's Achievements


Apprentice (3/14)

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

Recent Badges



  1. Hi,. If I hit record, then 'once' the loop will play once, and left bottom screen says 'overdub OUT', however, it does record overdubs. If I then hit 'once' again, the screens all display the same, but no overdubbing occurs (as expected). This a problem for me as I wish to record a loop, then press 'once' and immediately start playing over the top, with out overdubbing. I believe this is a bug - overdubbing should only occur when the leftmost screen says 'overdub IN' Thanks
  2. Hi I’m wondering if the non plus model powercab will be able to receive firmware updates? I can’t see any USB connector on it but there must be a way?
  3. So make it configurable as to whether or not to apply it to the line6 link. I own Helix and a L2 and in that situation I have no way off eq'ing for a room globally. I'd have to go analog and patch in an outboard eq. Seems dumb to me.
  4. Just download Line6 Monkey and you can update the variax from there.
  5. Oh cool - just realised you cam now edit string volumes per patch, not just globally. I don't think you could do that before? Really like the update. The natural body idea is something I had been wanting. Cheers Line6 :)
  6. Anybody else noticed this? I've listened pretty hard and it seems to me that the B and E strings are lower in output than the other strings on the Fender models. It's easiest to notice on the 'quack' strat settings (pos. 2 and 4). Seems fine on other models, including the acoustics.
  7. Yeah, theres no way to get distortion from the power amp and then have pristine clean reverbs etc after that, with or without an attenuator. Unless you take the line out from your attenuator, run that through you're verb and delays, then send that to another power amp - not overly practical.
  8. I'm sure it would be a whole lot simpler and less computationally intensive than, say, modelling a tube amplifier - absolutely trivial in comparison. And there's no reason why an OO language is required.
  9. Thanks for your posts guys. The that surprised me most was that, before the 2.0 update, I was using the DT probably without realising there was a cab sim on. I'm pretty experienced using modelling live (traditionally amplitube into an acoustic image and my THD cab) and when things sound a bit funny, the first thing I do is make sure the cab sim is off. Switch the cab sim off and everything comes right. I've got a pod HD500 and always just made sure the can sim was off if I was using a guitar cabinet. I'd read that they were 'live' models if not if studio/direct mode but was not convinced. I think I've changed my mind a bit, 'cause the DT has always sounded REALLY good, and I've had 'live' cab sims on without realising it! BTW, I don't use the pod with the DT using the line6 connect. I've always wanted to be able to call up different patches with the amp settings not changing. On a gig, I want to be able to change the amp eq and have it 'stick' when I change patches to use different effects chains. Having the pod with only effects running and using the preamp sims on the DT is the perfect setup for me. I have some experience as a software developer and have always thought patch systems on things like the pod could be made a lot better by allowing a hierarchy of patches. So, for example, I could have a 'parent' patch that has , say, an amp setup with maybe some reverb and eq. I could then apply a 'child' patch that has maybe some chorus or a drive pedal. Then I could change the child patch, but retain the amp settings and reverb from the parent patch. This is actually a pretty common way of dealing with settings in software. The active settings are calculated from a hierarchical structure with certain rules for overriding or combining settings further up the hierarchy applied. That's the way I'd do it.
  10. So, I just realised the default voicings on my DT50 have cab sims. Can anybody tell me what they actually do. Someone who actually knows, not just speculation - I can guess as well as anybody. I run it through a THD 2x12, and using the cab sims doesn't sound rubbish like I would expect. I can switch them off via midi with the new firmware to compare. So, they are clearly not full cab sims - more like what the pod does when it's not in 'studio/direct' mode. Are they just some eq (that's what it sounds like), or are they more than that? Does the dt50 phase them out as the amp gets louder? It seems a bit silly to have a cabinet sim going when you're driving a real cab to speaker break-up. Cheers
  11. Yeah, I just discovered that about my DT50. Seems a bit weird to me. You're going into a cabinet, so why the cabinet models?
  12. Really, for live use? Not much reason IMO. I like my DT50 head but normally use my Fender Hot Rod (pod to FX return). Sounds great. DT 50 doesn't sound better, just different, then different again if you change class a/ab etc. If I didn't use a pod, then I'd say differently. My DT-50 is great to use with just a guitar and maybe a boost/drive pedal.
  13. A little confused. When you use L6Link, it sets the POD output mode to 'combo power amp' and the L2 to electric guitar mode, which seems to imply that's the Line6 recommended way of using them together. Doesn't that defeat the point of a full range flat response system? The speaker is coloring the sound and the POD is expecting that coloration so is altering its output to suit. Also, if you're using the L2 as backline and sending output to the soundman from the pod you'll want to have the pod in 'studio' output mode. Problem is them you'll want the L2 in FRFR mode, meaning you can't take advantage of the groovy virtual tilt back thing. If you put in keyboard mode (for example) what you'll be hearing will be colored and different from what the soundman gets, no?
  • Create New...