phil_m

The little external VDI interface just passes data. It doesn't pass power or audio. So, no.

The reason I'm asking about whether you're going from the indicator on the receiver versus the actual transmitter indicator, btw, is that I noticed today that on my receiver, it was down to one last red LED (not blinking yet), but I was still able to play for another 1.25 hours. Even then, my transmitter LED hadn't started blinking red. So perhaps the indicators are just out of sync?

Are you going just by the bars on the receiver, or has your transmitter actually started blinking red as well?

Not trying to make anyone feel dumb. I'm just saying that there's no way to gauge the actual numbers with this sort of issue based on a super-small sample size that is people who post on these forums. If you bought your unit in November 2019, it is still under warranty, and you should be eligible for a replacement. I have to G10S systems and one of the original G10 systems. I haven't extensively tested them all yet, but the one, I charged at the beginning of the week, and I've been using it all week in the evenings, and I haven't had to recharge it yet. So at least for me, I'm not seeing the same sort of battery life reduction others are seeing. If there's a problem, Line 6 will get to the bottom of it, but they need people to cooperate with them to do it.

You're basing your 90% number on what exactly? A few posts here? There have been over 144,000 G10 transmitters since it was originally introduced. I imagine what might be happening is that some of these units were probably getting close to the end of their battery life, and there probably was some internal tolerance changed as far as monitoring the output voltage goes, so they're just registering as being low faster than they were before. I don't know. If there's a genuine issue with the firmware, I imagine it will get fixed eventually. Again, this is another reason why opening a support ticket is important. It's the only way to get real data to Line 6.

I'm sorry, but I'm not following what you're wanting to do. Can you provide a little more detail? If you want to change parameter values on a snapshot per snapshot basis, those values need to be assigned to the snapshot controller, just like on the hardware.

You have to plug the transmitter into the Spider's input for 15 seconds or so the transmitter can be set to the correct channel.

You could use the line out from that to connect to the Powercab, but be aware that the PS1 is just an attenuator, not a reactive load. So you still have to have an actual speaker load connected to its speaker output to prevent your amp from being damaged.

Are you re-syncing the transmitter with the amp?

Is your Global EQ on?

I know pretty much all of them are working from home right now. Whether or not they'll be able to release the update during this time, I don't know. I imagine it's probably not a big deal from a feasibility standpoint, but things like QA/QC might be harder now.

The answer is the same for anyone experiencing this issue. Open a support ticket.

Yes, this is the expected behavior of the capacitive touch feature on the footswitches. You can turn the Touch feature off in Global Settings>Footswitches if you want.

What do you mean by the one that comes with it is too small? Do you mean the cable isn't long enough? The HD300 power supply should work with the HX Effects. They should be the same thing. Although, the HD300 power supply may be an earlier version of the DC-3G, hence the lower rating. Even at 2A, it should be fine for the HX Effects.

It probably won't work with the looper. I know when I messed with this before, the looper always caused things to lock up because the looper sends CC commands for the various looper commands. They may have changed that, but I'm not sure.

https://www.disasterareaamps.com/shop/midi-baby

It's in the manual:

It's normal. It's related to the amp modeling. You can hear similar sounds in close-mic'ed amps and in other modelers. You can try adjusting the Bias parameter in the amp model to minimize it somewhat.

It will be fine. That's really not even that cold. I played an outdoor gig at a holiday festival here in Minneapolis with my HX Effects board where is was like 20F, and everything worked fine. Really, electronics generally much prefer the cold to the heat.

Not without creating another instance as I mentioned above, no. I mean, there's no real drawback for creating another instance. The CPU load depends almost completely on what you have active in that instance. So whether you have the reverb block in one instance versus another doesn't make much of a difference.

Not quite sure I understand what you're wanting to do, but it sounds like you're making it too complicated. Just set up another track with it's own instance of Native and put the reverb block in that instance then create a send in your DAW to that track. Set the mix level for the reverb in Native to 100 and then you can control overall reverb mix in the track with the fader in the DAW. This is essentially how I would handle reverb for vocals or drums or whatever in a DAW.

There should not be poor battery life with the new firmware. I have not experienced that with my G10S. If you are, open up a support ticket so Line 6 can help you out. I believe the transmitters that are going back to retailers are the ones that the stop was placed on, just with the updated firmware applied.

Do you mean a 3-pole, dual throw switch (3PDT) switch? One thing is that the switch needs to be momentary.

Do you have the outputs on the Stomp set to line level under Global Settings>Ins/Outs?

I'm pretty confident in saying that there will be some polyphonic stuff coming in 3.0 just because that's what several Line 6 guys have been saying publicly for awhile now (notably, Igor Stolarsky, who's does a lot of the coding for the Helix). So, yeah, the pitch shifting stuff should be coming. As far as polyphonic tuning, I've never quite understood the appeal. Yeah, I get that it tells you which strings are out of tune, but you can still only tune one at a time. And a lot of time if I'm tuning a few strings, I'll just check them all quickly anyways. Does having a polyphonic tuner actually save time?