phil_m

I never said it wasn't possible. I'm just saying there's reasons for it being the way it is. I think they want to be careful about pursuing a feature that makes one group of people happy if it has the potential to cause problems for another group of users. It seems like they're saying that stuff that adds latency to preset switching is a non-starter right now. It doesn't mean it won't ever be done, necessarily. They would just need to come up with another way to do it.

I was pretty much repeating what DI said here: https://www.thegearpage.net/board/index.php?posts/24636213/

Tracking the input impedance of every block along with the on/off state of each block is quite a bit more data to deal with. The thing with all these little subroutines is they add up and end up making the gap when switching presets longer. Right now the input impedance can be tied to a snapshot controlller, so it's pretty simple for people to set it how they want it.

I forgot the lowest input Z setting as I'm not in front of my Helix right now, but the highest setting is 1 Mohm.

The Spider V effects cadre is essentially taken from POD Farm, and there was never a ducking delay added to PF...

It's really not that uncommon for there to be a little bit of drift or for the BPM display to not match exactly when you're syncing with MID clock. There are limitations in how precise MIDI clock can be. What do you mean by " most of the time the tempo is correct but not in sync"? What's not in sync?

Press those two switches together again to change their function. They can be set as bank up/down, preset up/down, or snapshot up/down. Just make sure you're just pressing them once and not holding them down. Holding them down toggles between preset and snapshot modes.

Have you installed the latest firmware in your amp?

As stated above, it's called Spider V Remote. It should show up in the software link as long as you select one of the Spider V models in the left pull down menu.

The way the Auto setting on the Input Z works is that it changes the input impedance based on the first block in your chain. The input impedance will be set to match that block whether it's on or bypassed. If you want the lower impedance to only be that when the fuzz pedal is on, you could set the impedance to be tied to a controller, either that same footswitch or a snapshot controller, and have the impedance be lowered only when the fuzz in on.

As of yesterday, there is a PC/Mac editor available for download here: http://line6.com/software/ As for the iOS and Android app, it's called "Spider Remote". With an iPad or iPhone, you'd find it in the App Store. On an Android device, you'd download it from Google Play.

I believe the Spider V's XLR outs behave the same way as the XLR outs on the Helix. If only the left side is used, the stereo signal will sum to mono.

There are all sorts of Variax transplants out there, but like cruisinon2 said, Line 6 doesn't sell the Variax guts independently, and I highly doubt they ever will. You just have to buy another Variax and rip the electronics out to put them into your guitar. It kind of goes without saying, but doing this sort of thing isn't something Line 6 supports. What I mean by that is that if anything goes wrong with the Variax electronics, there will be no sort of warranty coverage.

Relevant to this thread - Spider Remote for PC/Mac now available: http://line6.com/support/topic/29307-control-your-spider-v-amp-with-spider-v-remote-version-100/?do=findComment&comment=226551

All the previous versions are available still. You just have to check the box that says "Archived" to see the older ones.

Just throwing my 2 cents about the G70 here... I mentioned in an earlier post that I was using the G75. Well a few months ago, I decided to switch to the G70 since I could mount it on my board with my Helix. I've been using the G70 all summer for my various gigs, and I've not had any issues with it whatsoever. I've not had it cut out once. Depending on the specific gig, I use three transmitters and three scenes on the G70. It has been great.

The Headrush doesn't have the ability to save or export loops either, as far as I can tell, so I guess I'm a little puzzled how it could be all that helpful as a recording tool in that regard. It just has a longer looping time. It does have the concept of layers of loops, but it's still not really a multi-track looper. The loopers on these devices aren't really meant to compete with full-blown looper pedals, but you can still do cool stuff with them. The device I've most often seen used for live looping is still the good ol' DL4, and that is way more limited than the Helix's looper.

Perhaps the noise gate is on in the input block... If you select the input block, you'll be able to see if it's on.

I wouldn't expect any upgrades to the looper as far as additional looping time and multi-track looping being added... Those are all a matter of the available memory and type of memory being used. Digital Igloo, the product manager, has basically said that the Helix architecture doesn't support that sort of advanced looping stuff. Now things like quantizing and tempo syncing, that might be possible...

You should turn CC32 to off, as the BigSky doesn't respond to it. That could be messing with its ability to receive the PC message.

You can use the 2.11 editor with the 2.12 firmware. The 2.12 firmware was a patch for 2.11, so there was no 2.12 version of the editor.

The Opti Trem block has Windex-like qualities... It can fix everything!

In your earlier post, you mentioned that you have the output block set to +5dB... You have the ability to set that up to +20dB, so it seems like there should be plenty of volume on tap between that and gain blocks. One other thing, is you mentioned the master volume in the amp block. That does affect the volume, but it also affects the saturation. The channel volume is the overall output for the amp block, so if you need a little bit more from the amp, you can add it there.

All of the modulation blocks have a level parameter, so I suppose it's possible to get some amount of boost with an output block (although, I believe it's limited only +6dB for those blocks). The level control on those blocks is really there for the purpose of getting the level of signal with the effect on to match what's there with it off. It's not going to do anything to help the situation described here.