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

ben_craven

Members
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Registered Products
    5

ben_craven's Achievements

Rookie

Rookie (2/14)

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

Recent Badges

5

Reputation

  1. I am hopeful. If the Pod Go had been advertised more accurately as "the input impedance is 300k" and "you will need to add corrective EQ to make your passive guitar sound consistent", I probably wouldn't have bought it in the first place.
  2. A factory reset made no difference in my case. It's just the standard, easy, first troubleshooting step support teams recommend to customers.
  3. I have no further updates. I am disappointed that a $1000 AUD unit has such a glaring design problem, which has been generally dismissed by reps as something only "power users" should worry about. The digital algorithms and modeling are absolutely terrific. Unfortunately the critical input circuitry does not do them justice. Mine is still under warranty so I might contact the local Yamaha service centre and see what options are available.
  4. I notice this topic has spawned a similar thread on The Gear Page, so it doesn't appear limited to a few units:
  5. Hi everyone. I received the following comment in my support ticket. I think it's an acknowledgement that Line 6 has not dismissed the issue completely, so that's positive news: "I was recently informed that our team is already aware of this issue, and our quality team will be investigating it further if there should be any improvements to Pod Go firmware or hardware." For a bit more background, I also tested the input impedance with the signal connected as the unit was switched on, but I didn't see any difference so didn't bother including it in the video. The guitar input pad was off for the test, and the placement of effects at the beginning of the chain didn't seem to make a difference either.
  6. Line 6 support told me I was subjectively hearing the 1M input impedance incorrectly. I went and calculated the input impedance at 360k. This explains everything, so I still believe this is a genuine issue, at least in MY Pod Go:
  7. The input impedance seems to be completely messed up to me. I made a video showing the difference when using a buffer. Sorry about the clickbait video thumbnail: That a buffer can make that much of a difference to the top end suggests to me that issue is in the hardware.
×
×
  • Create New...