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

Leaderboard

Popular Content

Showing content with the highest reputation on 05/17/2022 in all areas

  1. While researching Pod Go issues before the purchase, I discovered multiple reports on difference in sound with same presets compared to Helix. Apparently this is known issue, and many solve it with placing additional pedals before guitar input. Here is the main thread: pod-go-impedance-problem Here is the video highlighting the difference in sounds: Just wondering, is there any official response to this issue? Is it confirmed/negated by line6 anyhow, anywhere?
    1 point
  2. Re the video: Helix has a variable input impedance selector. Pod Go has a fixed impedance of 1M Ohm. If he had Helix set to 'Auto' I'd be interested in a comparison using the other impedance setting in Helix. For those less familiar, placing a buffered unit in front of Pod Go will deliver the same highs. A buffered unit might be eg any Boss stomp pedal - the pedal has to be powered but not stomped 'on' to benefit from the buffer. The other buffered device could be something like the Line 6 G10 Relay wireless system that is a buffered device. I use the G10 Relay, so do not have this issue, and is why similarly the Pod Go Wireless doesn't have this issue ie it's an issue ONLY when using cables. However, it is also very much down to the make, length & type of guitar cable you are using because different cables have different impedance, that can make a big difference to your tone. I tested my Pod Go with a good quality Vox coiled cable and my Piranha cables and the tonal difference with both as compared to via the G10T or placing my Boss CS3 pedal in front of Pod Go, was negligible and nothing like the variation in this video, which is quite extreme. Now, whilst there has been a lot of posts on forums/boards/youtube vids on this issue, you need to appreciate that putting a buffered unit in front of ANY MFX unit will brighten tone and not until you hear the difference do you think anything is 'wrong'. now, although Helix offers an impedance selector, a 1M Ohm input impedance is standard in mid-range MFX. Even the brand new Boss GX100 is 1M Ohm, whereas it's big brother the GT1000 is 2M Ohm. So this is not a 'fault' with Pod Go, but an additional option in Helix that is 3 x the price. I have a Vox Tonelab SE, LE and ST - and the same tone brightening occurs when using a buffered device in front of these. I also have a BBE Sonic Stomp Maximiser, and this makes tone sound brighter/clearer too. The same issue applies when using a guitar amp if you plug direct into an amp and then compare with a buffered device in front of it. So, whilst there is a tonal difference, it's because of the more sophisticated impedance options in Helix, rather than an issue with Pod Go Impedance. And here's a further thought. Many of the more expensive wireless devices allow you to change the settings to replicate guitar cable impedance. Why? Because a lot of players don't like the brighter tone, and want it to sound similar to their cabled sound. This whole thing has just got a bit out of proportion. But whilst it's possible Line 6 might be able to do something in v1.40 firmware, I suspect only a physical mod would 'solve' the issue for those seriously troubled by it - but you never know. However, having said all this I still would have hoped that Line 6 would have said something to at least confirm Pod Go impedance definitely is 1M Ohm. The fact they haven't even done so does potentially raise a big question mark and could give some credence to (reportedly) 'techs' who say they have tested Pod Go and found the input impedance to be only a third to a half of 1M Ohm. If that is proved to be the case then it might suggest Line 6 may have cut corners to save a few pennies. The problem is that if Line 6 refuses to comment, customers and potential customers are left to speculate, and that's not a good thing. So Line 6, if you are looking in - please confirm what the Pod Go input impedance is.
    1 point
  3. I had a quick look at your history and you don’t seem to have much success using this stuff. You didn’t say what piece of hardware was having the problem loading the IR. I know you have a Helix floor because you had issues trying to figure out how to put it into 10 foot switch mode when using Command Centre. From the Helix 3.0 Owner’s Manual - Rev F - English - Page 38 ”IR File Reference Once an IR block is configured to utilize an IR index slot that includes an imported IR (.wav or .hir) file, and the preset then saved, the preset creates a “reference signature” to the imported IR from its file name. Likewise, if you save your IR block as a Favorite (see "Adding a Block to Favorites" on page 17) or set the IR block’s current settings as the User Model Defaults (see "Saving a Model’s User Default Settings" on page 18), the IR bock also creates a reference to the specific IR file within your IR library. Therefore, if you re-order IRs within the IR library list, your preset (or IR Favorite or User Model Default block) will still intelligently reference the originally associated IR file, even if it now resides in a different IR Library index location. This also makes it easy to share your presets with friends since they can then insert the same IR file in any slot within their Helix IR library, and the preset will find it. Please also refer to the HX Edit Pilot’s Guide for additional info regarding the use of IRs.” link: https://line6.com/data/6/0a020a3f041b611d61cac763b/application/pdf/Helix 3.0 Owner's Manual - Rev F - English .pdf And here is the Pilot’s Guide https://line6.com/data/6/0a020a3f1049f61fd3077f0eca/application/pdf/HX Edit 3.15 Pilot's Guide - English .pdf Have fun trying to “krack” the protection - I really don’t think you should have mentioned that in here. Hope this helps/makes sense.
    1 point
  4. only one thing for me really.. the valve driver has anyone ever used it and been happy with it? i tried it a few times and it just seems to make everything sound harsh and bad
    1 point
  5. The official response is no response. There's been nothing official here, and the two Line 6 contributors active on The Gear Page have refused to comment.
    0 points
  6. I have also measured the input impedance and found it to be around 205K at 1KHz. Someone posted a clip of the the Pod Go's schematic on one of the facebook Go groups showing a 1nF cap to ground in the input section, which would explain the low impedance and tone suck. The person also showed pics of the board showing where the offending cap was (C126 if memory serves). Unfortunately, the post was deleted shortly after it was posted. Of course, it could have been a fake, but it looked legit to me. Two people on the gear page have opened support tickets because of this issue, The first person says Line 6 "repaired" their unit but they have no way of measuring the input impedance, so they don't know what line 6 did. The other person was told to pound sand. This can't be fixed with a firmware update. My fear is that Line 6 will band-aid a fix in the form of adding a hidden compensating curve in the output EQ to digitally boost the attenuated high frequencies. I really wish Line 6 would address this issue.
    0 points
  7. -1 points
This leaderboard is set to Indiana - Indianapolis/GMT-04:00
×
×
  • Create New...