Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


qwerty42 last won the day on May 16

qwerty42 had the most liked content!

Community Reputation

68 Neutral

About qwerty42

  • Rank

Profile Information

  • Registered Products
  1. Correct. This is a confusing statement. You're saying with the TubeScreamer on (NOT bypassed), your 'tone and impedance should not change' if you remove it. Input impedance is a property of a circuit. The TubeScreamer has its own input impedance. Your amp has its own input impedance. It affects the tone of your guitar because of how it interacts with your pickups, and every device you plug into has its own input impedance that doesn't necessarily match anything else. The rest of your statement is just further confusing the original poster's problem. We're not talking about real pedals. We're talking about behavior of Helix under 2 very specific conditions, which should give identical tone. Re-read my post just above yours where I distilled it back down to exactly his issue. The more I address what you're saying, the more confused it's going to get again.
  2. FWIW, I tried exactly this and can't hear any difference in the treble freqs. I made two identical presets, one with a fuzz bypassed and one with the fuzz deleted completely. I set the input impedance to 1M on both. If you're still having this issue, can you share a preset that you're sure shows it? To bring this back on topic with the original problem, what the original poster described in this diagram above should *not* sound any different. Scenario 1 should be no different in tone than Scenario 2, if the input impedance is indeed manually set to a fixed value. Duplicating the above on my Helix as a test, I hear no difference. If the OP is still hearing a difference, their problem isn't solved, and more troubleshooting is needed.
  3. No it's not, because it's still being misunderstood how it works and what is actually happening.
  4. You're misunderstanding. Each model in Helix has an input impedance value included with it. Whether the block is bypassed or active, that input impedance still applies, and it is actually switching an analog circuit inside Helix at the instrument input. I'm going to explain with an example to make it clearer: The '70s Chorus' pedal has a 22kOhm input impedance. This is a built-in property of the model. You have the signal input's path Input Impedance set to 'Auto'. You put the 70s Chorus as the first block in your path, after the input. The input impedance (set by the switchable circuit inside Helix) will now be 22kOhm, because of the 70s Chorus pedal and the 'Auto' setting It doesn't matter if the pedal is active or bypassed. As long as it's there and the Auto option is selected, it will have the same input impedance with the corresponding load on the guitar's pickups in the circuit. If you delete the pedal with 'Auto' still chosen, then the next block in the path will set the new input impedance. If it's an amp, it'll probably be a much higher input impedance. If you override the input impedance value instead of using 'Auto', the override value applies no matter what. It no longer matters which models are in your chain. Lastly, just to really make this clear, the input impedance is a switchable circuit on the instrument input of Helix. The lower the chosen value, the lower the impedance in circuit with the pickups, which creates a low-pass filter that chops off treble. You can set this value to whatever you want to hear the difference. If you're still confused, this has been discussed endlessly on this forum -- you can search and there are LOTS of old posts that explain it ad nauseam. This is the point I'm making: that statement is not correct. There are no modeled bypass characteristics except the impedance (Z), and it absolutely matters what the setting of it is. With 'Auto', it gets assigned by the first pedal in the path, regardless of bypass state. With a fixed value, it ignores anything in the path and just sets it to whatever you choose. If you have anything that proves otherwise, please share it, because nothing any of the Line 6 staff have ever said that I've seen disagrees with what I've just stated.
  5. He has two setups. One is guitar ->pedal ->amp. The other is guitar ->pedal ->Helix. What difference would a buffer in the pedal make? The pickups of the guitar are loaded the same in both cases. Are you implying the input of the Helix doesn't like a buffer before it? To the OP: When you say you max'd the input impedance, you set it to 1MOhm, correct? If what you're hearing is loss of treble, then 1MOhm should give your best chance of keeping it. How long is your cable run between the Paisley and Helix vs. your pedal setup? Long cables can filter high frequencies too. Try to match the physical setup as close as possible. Is the input pad turned on in the Helix? That can change the sound and dynamic response a bit. I think you'd want it set to OFF but try it both ways, see if it helps. If the output of that pedal is a lot greater than the pickups alone, maybe it's a level issue. Try putting it into an effects return jack instead of the guitar input, and use the return as the input of your Helix path. Then go into your Global Settings and change that return to line level instead of instrument. I think this is unlikely to be the problem, but worth a try.
  6. FWIW, Helix's input dynamic range is 123dB***. So if you're looking to match that, the Clarett is closer. Honestly the Helix is a great ASIO input device, it just has pretty poor latency (higher than most modern interfaces). ***for the instrument input. Not sure if it's different for the various other inputs.
  7. One little clarification -- if you use a Dual Cab block, it is in stereo, with one cab panned hard left and the other hard right. You only get this dual option if your cab block is separate from the Amp block. Otherwise, yes, single cab blocks collapse everything to mono at their output.
  8. Are you certain of this? If so, what's the source? I've never read this anywhere before -- everything I've seen previously said bypassed vs. not bypassed retains the same input impedance values and only turns the model on or off.
  9. I'm kinda confused by what you're implying... the input impedance is an analog circuit inside the Stomp/Helix, which changes the actual impedance at the input jack. In other words, it's changing the way the pickups are loaded. The lower the input impedance, the more treble gets cut. That's not a buffer phenomenon, that's simply what happens with a low impedance input in circuit with the pickups--it creates a low-pass filter. On 'Auto', the input impedance is set to the value of your first block (it's baked into the model--it won't tell you anywhere what it actually is). For fuzzes, 'Auto' sets it to a pretty low impedance, because the real pedals also have low input impedances. That's where the treble loss comes from; that's what makes a fuzz sound the way it does. If you override the input impedance to 1MOhm, you've now changed the fuzz model itself because fuzz pedals in real-life don't have high input impedances. Thus you end up passing way more treble frequencies into the fuzz. It doesn't have anything to do with a buffer vs. no buffer in the Helix/Stomp, but this same thing is essentially what happens if you put a buffer before a fuzz in the real world. TL;DR: you're not hearing a switchable buffer; you're just hearing the difference between a low-impedance and high-impedance input on the same fuzz pedal. Real fuzzes have low input impedance which filters treble.
  10. FWIW, I tried exactly this and can't hear any difference in the treble freqs. I made two identical presets, one with a fuzz bypassed and one with the fuzz deleted completely. I set the input impedance to 1M on both. If you're still having this issue, can you share a preset that you're sure shows it?
  11. I'm only guessing here, so could be totally wrong, but... possibly because those are loopback tests, and without those things connected they can't be successful. EDIT - you posted at exact same time as me, ha! Which cable is plugged in? And is it actually connected to anything on the other side? Are you having an issue you're trying to solve?
  12. It seems very solid to me. There were a handful of bugs in 2.90 and 2.91, but 2.92 seems to have fixed all of the notable ones. One thing though -- I was one of the people who had the new output meters and compression meters get laggy, after the Helix was powered on for a while (hours). This continued even after updating to 2.92. It was fixed by making a backup, doing a factory reset, and then restoring the backup. I don't know if it matters, but when I restored the backup I did not restore globals, because resetting them is apparently what fixes it. I figured if there was some corrupted value in there, I wouldn't want to restore it, so I just reset all my global options manually. Probably not necessary, but just including that detail for thoroughness.
  13. FWIW I get very (very) faint audio in my headphones too (Sennheiser HD600) with the headphone volume knob at 0. Can’t remember if it’s only in one side, will have to double check that, but I don’t think this in itself is a problem. Depending on the headphones you’re using it could be louder or quieter. At levels above min, the balance in L/R seems equal to my ears. I’ll try to remember later tonight to listen more closely and report back if it’s only the right channel. Anyway, glad yours seems to be solved. If it’s just a software glitch that can be fixed with a reset or update, that’s a great thing for others.
  14. I agree, either a double line or a different colored segment, something like that would be nice. I think a lot of new users probably don't even realize when their path is stereo or mono, which is unfortunate because it makes a big difference for recording.
  15. It's a feature, not a big. Those are the new signal present / clip indicators. Green = signal; red = clipping. If you select the output block, or any compressor block, you'll also see new signal meters and gain reduction meters.
  • Create New...