phil_m

I wouldn't say I'm being defensive... I don't work fro Line 6. I have nothing to do with the programming side of things. All I'm saying is that some of the ideas being put forth don't really make sense to me because that's not really how the product works. It's very hard to design a system that has some of fail-safe protection at every step along the way simply because people are really good at coming up with unexpected ways to find new problems. My day job is a lighting designer/engineer. The most complex things I do in my normal work are designing lighting control systems. And I'll just say that if you think the Line 6 software isn't user friendly enough, then never try doing anything with a lighting control system. But from the customer side of things, it's just hard to predict what people will do. This isn't meant to blame anyone, but if I have one word of practical advice for people, it would be this. Please don't update Helix during the middle of a thunderstorm... I've been slightly surprised/amused by a few reports from people who lost power when updating their Helix because they were doing during an electrical storm... :-)

Well, if you don't have the drivers installed, Updater won't even see the Helix. As far as HX Edit, technically, it's not required to install the update... It's just that - the editor.

I don't understand what you mean by this in this context... What prerequisites?

Conceptually, the steps for doing the update aren't really all the complex. I think DI's instructions are very detailed simply because he's trying to cover all the bases. They are so long and wordy because he's outlining every single step along the way - like to the point of telling people how to sign into Line 6 Updater. The fact of the matter is that once you go through the process once, it's a pretty simple thing. In my mind, I fundamentally see it as the following: 1. Create backup using the currently installed version of HX Edit. 2. Download and install new version of HX Edit. 3. Run Line 6 Updater and install update. For most updates, you can actually stop there. Now this update was different because it affected the Global Settings, so you might want to restore from backup to get those back. Also, if having the new factory presets is important, it requires another step.

That's the case in scenario A and B. The L6 Link output is simply another option for the output block on the Helix. It will send out the signal from whatever you have in the signal path ahead of it. So if you have a cab model in the signal path, that signal with the cab modeling applied will be sent to the DT. Meaning you'd be running an emulated cab into a real cab. And that's probably not what you want to do. If you want to run both a direct signal from the Helix and run the signal from the L6 Link in the DT amp, you'd need to so something like shown below. The one wrinkle is I'm using a Preamp block instead of a full amp block in this tone, so the direct tone from the Helix wouldn't have any power amp modeling...

There is a bug with the parameter values for the Powercab tab not updating correctly in HX Edit, but the snapshot changes should still be working. You should see them changing on the Helix itself.

The TB516G is the only transmitter that's compatible with the G70 and G75 systems. Each receiver can support up to 16 transmitters.

Your first two points are correct, but the Helix’s XLR outs won’t include cab and mic modeling unless you set up a split path and add a cab block. You can always use the DT’s XLR out if you want a direct out with cab and mic modeling.

This update resets your Global Settings, so unless you restored from a backup, those will be back at the default settings. It sounds like you had Preset Mode set to be one of the Snapshot/Preset split modes. Go to Global Settings>Footswitches>Preset Mode Switches and select the view you would like.

There were no firmware updates for the Spider II, and there's not even a way to hook it up to computer to update it.

I'm not exactly sure what you're saying here, but if your IRs aren't showing up in HX Edit, it's almost certain that you're running an older version of HX Edit. Note that the number on the bottom of the HX Edit screen displays the version number of the firmware on the attached device, not the HX Edit version number. There is a one step back up process. In HX Edit, you simply go to File>Create Backup, and that will create a backup file that contains all your Presets, IRs, and Global Settings.

The Spider V doesn't have Bluetooth capability. In order to use it with an iOS or Android device you need to use a USB cable.

The reason being DI thinks it's dumb... Lol... ;-)

The input for Helix Native should be representative of what's coming from your guitar. Generally, though, if the signal from your guitar is exceeded -12dB, you want to use the input pad. The Native manual says you should aim for between -36dB and -12dB for the input.

Based on what DI said here, I don't think it's going to happen... It doesn't really take any more setup or tweaking than using a cab or IR block in a Helix preset. You just have to think of the Powercab settings as part of your preset. Yes, it will take time to set up 50 presets, but once you do it once, it will be a lot easier to deal with in the future.

But what I'm saying is if you're clipping the input, you're clipping it for both the wet and dry... The same A/D converter feeds both the wet and dry inputs. The input pad, or the line level setting, is the control you speak of. The whole purpose of the dry track (for the most part) is for re-amping. And you don't want to change the level of the dry signal you use for re-amping because you want to maintain the gain staging of the original performance.

Well, as long as you're not clipping, you're good, but that is coming pretty close. The thing is, if you're clipping the DI signal, it also mean the signal feeding your wet tracks is also clipping. It means you probably need to set the input to line level. Given that you're using a seven string, I would imagine that your low B (or whatever you have it tuned to) is probably driving this.

Do you have the parameter set to the snapshot controller? Are there brackets around it? It most certainly works.

No, you don't need to change presets on the Powercab. Everything that's stored in a Powercab preset is now part of the Helix preset. It does mean that if you've already built Powercab presets that you were recalling with MIDI, you'll have to rebuild them in the Helix output block. But in the end it makes everything a lot more flexible and easy to use. With the L6 Link functionally added in 2.8, the Powercab is simply like an extension of the Helix. Other than adjusting it's master volume knob, you don't need to adjust anything on it or edit on it at all.

What was wrong with your first unit? I’ve been using my original G10 for over three years.

You can change all the Powercab settings in the output block per snapshot. It’s just that there’s a bug that the text doesn’t always update in HX Edit. You just have to assign them to the snapshot controller, just like any other parameter you want to change per snapshot. It definitely works, though.

Setting the 1/4” inputs to Line on the Stomp is functionally the same as enabling the input pad on the Helix. And, yes, the Stomp does have variable input impedance.

You have to have the time or rate parameters for the effect(s) you want tied to tap tempo assigned to a note value. Simply push the knob in for that parameter and the value will change from ms or Hz to a note value. The note value relates to the tempo you tap in. If you want the delay time to equal the time you tap in, set it to 1/4.

Yes, my understanding is that it works in Snapshot Mode currently, but not in the Preset Mode views that show snapshots (which is what the 8 Snapshots setting is). In any case, it's a known bug.

A little more detail please... In what way aren’t you able to use them? The update resets the Global Settings, so unless you restored from backup, things like how you have Preset Mode view set up could be different.