dragonfet

I don't have a solution, but if you have the time, could you check if 1. the FX returns are dead as well 2. if you get dry sound via USB (reamp input) when using the Helix as an audio interface ? It might help to narrow down similar issues in the future.

The impedance circuit is an actual analog load circuit located in the input amplifier section of the guitar input. It simulates an actual pedal input by adding a load to the input, which usually rolls off the high frequencies and makes the signal slightly less strong. This has no effect if there's any buffer inbetween the pickups and the Helix, including a wireless transmitter. Same goes for any FX pedal that isn't set to true bypass. I don't have such a list sadly, but I agree it would be useful. One type of effect that should have an influence are old fuzz pedals. Many had a bipolar transistor input with a low impedance, putting a lot of load onto the pickups, but making the such less harsh in the process.

This has been confirmed by Line 6, the responding person also narrowed it down to Drive 1 being set to 8-10 and Bass to 10, so he suspects it has to do with the Bass control.

I have just filed a bug report for a feedback loop in the Voltage Queen preamp block. I'm posting it on here too if someone wants to confirm it and to avoid duplicate reports. Steps to reproduce: 1. Insert a Voltage Queen preamp block. 2. Set all controls except for Drive 2 and Hum to 10. Drive 2 can be set to any value, Hum should be turned off, otherwise the effect might be masked. 3. There should be a low frequency (around 13 Hz + harmonics) resonance audible. 4. With Drive 1 set inbetween 7.4 and 9.5, the Sag value seems to change the frequency of the resonance a little. Other controls will influence the timbre and may cause the resonance to die off, e.g. when setting Bass to 0. Device is a Helix Floor, Firmware is current 2.70 .

Which firmware version are you using? I will try to reproduce this.

You did not. You may have tried to start one with an aggressive initial attitude, from then on you continue to flame against individual users, you respond selectively to those posts that offer the easiest way for you to heat his thread up even more, you throw in terms like "fascism" and "millenial snowflake" to send this entire conversation even further away from your proclaimed topic. You may have started a conversation, but not with an opinion.

Embedded programmer and software test engineer here. Since you seem to prefer voicing your opinion in a very direct way, I'll do so too: This crap is becoming tiring. You seem to have zero insight into software development, yet you come here and know exactly what the developers at Line 6 are doing wrong because... Yes, why actually? As an attempt of explanation: Resources are limited. The main resource in this case is the time a team of developers has in total. This time can be spent on concepts, architecture design, implementation design, implementation itself, testing, debugging, maintaining and many other tasks. Developing for a real time embedded system like the Helix isn't like clicking on a few icons in an Android App Maker to build the 16931st whoopee cushion soundboard for the Play Store. These projects eat a ton of time in every stage from concept over implementation to maintenance. Almost everything has to be optimized because any code that is inefficient would result in an audible delay, every bit of wrong code would distort the sound in various ways. This is one aspect. The other is what amsdenj mentioned: Technical debt. It's a term for tasks and unsolved problems that have accumulated over the development of a component or a product, basically a To-Do-List. This list has to be tackled someday if you want to keep your product in the market. If you look at the changelog for the 2.7 update, it's a lot of those minor annoyances that may be major ones in the wrong setting, like polarity/phase issues and amps that become quiet. The third aspect is that we are not talking about a single device here. Helix is a platform with by now a whole set of different hardware devices and a software plug-in. "Platform" doesn't equal "I write a line of code and it works everywhere". It once again may have to be optimized and it has to be tested. And no, testing isn't plugging in a guitar, checking if there's sound and if so, ship it. If that was the case, we wouldn't have to fix bugs at all. Look around in the forum. For over one year there have been complaints about the tuner, including lengthy posts, heated discussions, YouTube side-by-side comparisons with other tuners, people testing it with different instruments and what not. I play bass and have had very few issues with the tuner, but it seems to be a problem for many users. What did Line 6 do here? They addressed a complaint. Isn't that what you wanted? No, you're one of those people that not only buy a product and then somehow feel entitled to get something they want, you also have the impudence of putting yourself above a department full of most likely very experienced software engineers, programmers and projects leads saying "They're all idiots because they can't do more.". I recommend you get yourself a SHARC evaluation board, a matching C++ IDE and start writing your own DSP accelerated real time sound processing pipeline. Then you can use all your insight to add amp models, fix bugs, walk and chew bubble gum every day.

Hmm. To me the offered preamp stages of the two Cali models and the Ampeg (though I rarely use that, I don't like the Ampeg sound in general) are pretty sufficient, and there's still the Aguilar and others available. I don't use the Darkglass because it sounds too harsh for me, instead I either use a guitar pedal like the Deranged Master or a blend of a guitar amp and a bass amp. Without wanting to offend anyone: I'd rather check if there isn't a way to get the sound you desire with the amps and FX that are already available. You can always add an EQ inbetween stages and do a lot of tone bending, you have the IR block that can also be used in various places. I know the desire to have more different models available, but often enough the flexibility offered by the existing ones is actually sufficient. And I'd rather have Line6 focus on a few good models than to add mediocre ones on every update.

This is interesting. I'll have to check if I'm using the input pad, I think I do (passive humbucker bass). Electrically, there should be a bit of noise added if impedance stays the same and you're turning the (amp) gain up higher, but maybe the Helix has a high enough signal to noise ratio that it doesn't matter in practice.

Not sure if this existed in pre-2.60 versions too: 1. Select a preset with an amp block 2. Open Global Settings 3. Select any category (e.g. Ins/Outs) 4. While touching a footswitch, press Page Left or Page Right. Result: While the "Global Settings" Screen is still being displayed, the rotary knobs change to amp controls instead of the settings. I'll open a ticket for that. [EDIT] While it was perfectly reproducible a moment ago, I can't seem to stimulate this condition anymore. It seems to be a more complex connection of events or a sporadic bug.

Helix Floor bass user here. Your scenarios definitely work, and I can add something else: Depending on what you want to do with it, the Helix works great for bass. Most of the guitar amps and cabs obviously won't work well with a bass, but there is still a broad and usable selection of bass amps, bass cabs and FX. And you can of course load your own IRs. I can strongly recommend the Helix for that.

I'd like to nitpick here: Why the PSU? If anything, I'd call a switching mode power supply digital because of its hard switching characteristic and PWM controlled action. As for the OPs question: No, there is no analog part involved in the Helix' effects. I'd be reluctant to specifically mention the input/output circuitry: Of course it has to be analog. There's also no such thing as "digital impedance" (aside from just using a cheap high-cut filter), so that part must be analog as well. Though it's of course a noteworthy feature to have it switchable in the Helix.

I agree on the thread topic. As for the new effects: I personally have everything in the Helix that I want by now. I tried out all the amps, speakers and FX, I tested a few free IRs and I found the models and combinations that work for me. If I have to make a new preset/sound, I know where to start and which workflows to use. While I don't doubt there could be some new models in the coming update(s) that will immediately make their way into my patches and become absolutely essential, I don't miss anything at the moment, and I suspect a few other users might have similar thoughts.

On 12/4/2015 at 10:30 AM, jaminjimlp said: here is a bunch I found and some I made with rewirerz mix2 prog from free ones I found. I think the best one I made is the "GHK.wav" the other good one is the kp-cab-ir.wav someone made with a kemper that was posted on TGP enjoy friends: https://www.dropbox.com/sh/m19ymuuus8qid7d/AACLHcDWpEUZsUF54GLom6Xua?dl=0 This is a very old quite and I can't create a backlink, so I'm just copy-pasting it. It is still active and I actually found my favourite bass cab IR in there (a Mesa one). It contains some duplicates, some IRs vary greatly in volume and - as usual - there's some very good and some very bad ones. But if you have the time, you can look through there and maybe find something that suits your needs, I haven't checked for JBL. As for the "quality" discussion: like zooey said, there is no technical difference in the IR files themselves. What I could imagine may have been meant by the "by today's standards" is that IR recording techniques have progressed. Maybe different tools and/or acoustic setups are now used that yield "better" results, whatever the definition of "better" might be. I strongly recommend not to simply pass on "old" IRs though as they might have just the sound you're looking for. Think of an IRs real-world counterpart: For some reason, some people still prefer a very old and totally outdated Fender Bassman over something shiny and modern...

This sounds non-ideal to me. I can't find a datasheet right now, but I'm sure the Helix can output more than 0 dBu on it's XLR outputs as I've driven a Behringer DCX 2496 with it, which runs at +22 dBu = 0 dbFS. So turning your Helix all the way up could easily drive the XLRs (and 1/4" 's) towards levels that may increase distortion on the output amplifiers. I agree with the first part and partly disagree with the second. I also reserve the physical volume knob for the 1/4" outs so I can adjust my stage monitor while feeding feeding a constant signal to the FOH. I would not set it to Mic level unless required though as that makes the Helix attentuate the signal, send it over a possibly very long XLR cable, then have the mixer's preamp amplify it again. If possible, it's much better to output line level and either use the mixer's input Pad (usually -20 dB) or, if the mixer only has a 1/4" line input, use a passive DI box in reverse where you "convert" from XLR to 1/4". Of course that last option may not be convienent when you have time pressure, so it's easier to set the Helix to Mic out as Dunedin said and just go with it.