phil_m

It is odd... All of my global settings seem to be fine on my Rack after all the various betas for this release. I haven’t done a reset in quite awhile. I wonder if it’s related to people not doing a reset with the prior update?

Please try doing a factory reset and Restore from Backup! That seems to clear up most of the weird issues people have. There are a few bugs known bugs - the tap tempo thing, the volume knob, and a few others - and those will be dealt with in a hotfix very soon. But don’t just assume because something is different that it’s a bug that’s affecting the whole line. Sometimes it’s a global setting that has been changed, and sometimes it’s just something that the reset will fix.

Sorry to be the bearer of bad news, but it's not going to happen. In short, if it were possible, they would have done it out of the gate. It all has to do with the DSP requirements of each block. Things like the volume, wah, EQ and FX loop blocks use very little DSP. But they take up space, so they make the overall chain longer. So in a way, it's kind of trick, in the sense that it's giving you a lot of blocks - kind of like Chipotle giving you a lot of rice in your burrito. Rice is cheap, so they'll give you more. These utility blocks are "cheap" from a DSP perspective, so you can have four of them...

I'm sure some of your global settings changed. Just do a Restore from Backup (File>Restore from Backup) in HX Edit to get them back to what they were prior to the update.

ASIO4ALL is most likely the issue. Why are you using it and not the Line 6 drivers?

What are you using for an interface?

I would try doing a factory reset (hold down FS9 & FS10 while powering up) and then restoring from backup before you try rolling back the firmware.

You don't have anything to worry about. The USB cable involved in the recall was an accessory that was sold separately.

I'm glad things seem to have gotten sorted, but it seems to me that if the same computer bricked multiple pieces of hardware, than it's most likely there's some sort of issue with that particular computer, not all the different pieces of hardware...

The tap tempo thing will be address with a hot fix, probably within the next few days. As far as saving a block, what exactly do you mean? There isn't a way to save settings for individual blocks.

You just need to set your Global Settings back to what they were. Or just Restore from Backup. The settings relating to the EXP/EXT FS jack were changed with the updated.

Did you update HX Edit?

How are you getting audio from the Helix to the Audient? The BNC connector is simply Wordclock.

I would think that it might be possible for them to to add that in the future, since there’s separate tip and ring circuits coming out of the jack, but as it stands now, you can only choose between having it support a single expression pedal (without a switch) or two footswitches. There’s no option for one expression pedal and one footswitch, which is what you would need for the SP1-L6H.

Not really much you can do for that. The looper on the HD500X doesn’t have any external sync capability, so, yeah, trying to sync it with an external drum track like that, it will eventually get off sync.

There isn’t a 64-bit version of Monkey.

Hmmm... Well, last time I got my transmitter down to the point it was flashing red, which was like last weekend, it stayed that way for over 20 minutes. I didn't actually let it die, so I just recharged it at that point. It really does seem to me that people are seeing very disparate behavior from their batteries.

You could use the Floor as a MIDI controller for the Rack, but it would not give you nearly the same functionality as the Helix Control with the Rack. It would also be a relatively painful and tedious process programming the Floor to control the Rack, depending on how detailed of control you want. With the Control, everything is much more automatic. One way to think about is that the Helix Rack and Control are designed to give you the same sort of hardware control as the Floor (minus the on-board pedal, of course), but just broken out into two physical pieces. The Control is an extension of the Rack in that sense.

What I’m still not clear on is whether people are going from the actual behavior of the transmitter or just the indicators on the receiver. In my experience, the indicators on the receiver are not very accurate. Even when my receiver is flashing red, the LED on the transmitter stays green for a good while.

The original Spider V series can essentially be converted to an mkii with the 2.0 update. The only hardware differences with the mkii series are aesthetic. So you just need to install the update, and you’ll be able to do what you want - no hardware modification necessary.

Have you updated to the 2.0 firmware? If you use the Classic speaker mode rather than the Full Range mode, the tweeters will be disabled.

Try a different cable and/or USB port.

The receiver seems to start blinking red well before the transmitter. I've hardly ever looked at the receiver while using my G10S because at home it's in a rack shelf. But I have noticed a few times, that the bars started going down earlier than I expected. It still seemed, though, that I was getting close to the six hours with the transmitter. So I don't know - something seems off as far as the battery life indication on the receiver goes.

When you say the receive tells you it needs charged, what do you mean? It’s blinking red? If the transmitter isn’t blinking red, I’d go by that.

The battery performance isn’t based on the age of the battery. It’s based on the number of charge/discharge cycles. I believe the batteries are rated for 80% of their life at 300 cycles, so most people shouldn’t be seeing such a huge reduction in life after a year, even with the new update. Even at 80%, and the reduced capacity with the update, battery life should be over 4.5 hours with a full charge. https://www.thegearpage.net/board/index.php?threads/line-6-g10-release-date.1692051/page-15#post-22175031 This is is why I keep saying people should open up a support ticket if they’re seeing extremely reduced capacity with the update.