silverhead

(... I added the bolding above for emphasis ....) Unfortunately I think Line 6 and other manufacturers may not be where you hope they are. What if Apple went ahead and did what the bold text says you don't want them to do?

Line 6 developed mobile apps and a Bluetooth/wifi capability in their Amplifi/Firehawk series of products several years ago. They are still available new and there’s now a used market for them. If mobility and Bluetooth are critical features for you then consider those products. Of course, they are iOS and Android apps; Linux is not supported. I guess you’re used to that. It’s highly unlikely that a Bluetooth capability will be added to the Helix products. However I expect there’s already a suggestion for that on Ideascale. Vote it up or add it.

You’ll get more useful results if you describe the type of music you like to play. A blues lover will give you a very different answer than a metal lover. After your Helix arrives you can also get a good idea of the amps you like by browsing the factory presets.

Downloading and installing the HX Edit v2.92 installation package is the first step of the firmware update process. Did you do that? Install all components of the HX Edit package and then run the HX Edit program. It will guide you through the firmware installation procedure.

I thought her name was Karen.

I think the point is that it’s Apple’s problem, whether the OS itself or their servers. Neither Line 6 nor other affected manufacturers can fix it.

I think the best presets can be purchased from Helix Marketplace. They all have samples you can listen to before purchasing.

I think Line 6 and all the other companies are and were ready for Big Sur, except that it seems Big Sur is broken. It’s up to Apple to fix it and Line 6 can’t say when that will be.

As I understand the situation Line 6 is aware of and investigating the incompatibility issue. However I haven’t yet heard exactly what the issue is, and who is responsible for a fix. I seem to recall that the release of iOS 13 also caused compatibility issues with some Line 6 (and other manufacturers’) products. In that case it was Apple who caused the problem and they eventually fixed it in the iOS 13.4 release. Until we hear exactly what the problem is and who’s responsible for providing a fix I think we should avoid pointing fingers. This is the current status report from Line 6. We have discovered a compatibility issue between the “StageScape Remote” application and iOS 14. We are investigating the cause of this issue, and at this time we recommend not updating your iOS device to iOS 14 if you are using StageScape Remote with your StageScape M20d mixer. To prevent iOS devices from automatically updating, please click “Settings -> General -> Software Update -> Customize Automatic Updates” and de-select “Download iOS Updates”. Thank you! The Line 6 Support Team

Yes, you are misunderstanding. When you turn off the POD Go FX Loop you bypass the loop but the rest of the signal chain is active. That means the signal no longer goes from the POD Go FX Send to the front of your amp, and the FX Receive on the POD Go no longer receives the signal from your amp’s FX Send. However, the signal continues through your POD Go and passes through the remaining FX blocks in your signal path. So the FX you place after the POD Go FX Loop are active and are passed through the POD Go outputs to your amp’s FX Receive, and then are heard through the amp’s speaker. The typical use for 4CM is allow you to construct presets that use either a POD Go preamp model or your physical amp’s preamp section - not both. When you want to use a POD Go preamp model you turn the FX Loop off and make sure the Preamp block in your preset is active. Since you are using your physical amp’s cab/speaker you don’t want to use the full amp model (which includes the cab section) in your POD Go preset. When you want to use your physical amp’s preamp you turn the POD Go FX Loop on and you bypass the amp/preamp block in your preset. In the latter case you are essentially using the POD Go only as an FX (not amp) processor, with the flexibility of placing your FX blocks before or after the amp. But in all cases all FX blocks in your POD Go preset are active unless you bypass them.

Don’t know if you like manuals but you can learn a lot about the POD Go in advance by reading the manual.

What parameter are you talking about starting at 0.0? In general you should start your patch levelling process with the quieter, clean patches. Set the main volume knob of the POD Go at nearly maximum, say 80% or so. Work on a few clean patches and get their levels balanced using the amp Channel volume and the preset Output block level, both of which do not affect tone. You can also use the EQ block; leave all tone settings neutral and just use the Level setting to provide volume adjustment without affecting tone. Avoid adjusting amp parameters like Drive and Master to balance preset volume levels; these parameters affect tone.

I suggest that, since you already have it, you try using the POD HD in the FX Loop of the POD Go. It may very well satisfy you and not ‘muddy the tone’. If you’re not satisfied you can explore other options.

The one who dies with the most toys WINS!

It sounds like you are using two different physical pedals to control the two VOL blocks. You could optimize your current setup by assigning both VOL blocks to the same physical pedal and configuring their Min/Max values oppositely. When one is at 100% the other is at 0%. That way you achieve a blend of the two inputs, with the pedal at heel position being 100% one input and at toe position being 100% the other. The blend can provide an interesting option that you might want to explore. Or, you could try assigning the Variax Vol knob in the Input block of each path to the Snapshot controller and set it at 10 or 0 as the snapshot requires. Another method might be to assign the Output block (or use Gain blocks?) Level parameter in each path to the snapshot controller. Assign the Level to minus or plus whatever dB as required in each snapshot to suppress the desired path outputs. There may be other methods too. These are just the ones that come immediately to mind.

By default when you connect an external expression pedal (EXP 2) it is assigned to the VOL block. You can remove this assignment, or simply turn the VOL block off (bypass it). See manual pg 29.

No. The POD XT has no wireless or Bluetooth capability, and there is no built in media reader/writer (USB memory stick, SD card, etc.) so there is no data transfer method that does not require a computer.

I understand there will be a series of lawsuits to prevent the release. Dead people designed it and no one was allowed to review it.

Follow the instructions. Start by installing the latest HX Edit package. It includes the compatible drivers and Line 6 Updater program. After installation, run HX Edit. You can update the firmware from there.

I use the POD Go or my Helix Rack interchangeably as the interface; my older non-Line 6 interface device is collecting dust. I find I don’t need to switch interfaces in my Windows 10 system. When the POD Go or Helix is powered on it automatically becomes the computer’s input and output device as well as being recognized as the audio interface by any recording program. When neither is powered on the computer’s internal audio system is used. I leave both devices connected via USB to my computer and also to my studio speakers (using different speaker inputs). I power on the one I want to use for any session; no switching or setup of cables. There is a small and generally unnoticeable improvement in quality using the POD Go or Helix via USB because the signal remains digital throughout, avoiding a D/A and subsequent A/D conversion required to pass through a separate interface.

You’re right - a software/hardware mismatch. The Helix VDI communication is not compatible with older Variax guitars. It may work to some degree but it is not supported. You should use the analog (1/4”) from the guitar to the Helix Guitar input. However I think the original Variax Workbench software (not Workbench HD) should work with your Variax Acoustic 700, allowing you to store alternate tunings in the guitar. You won’t be able to control anything via Helix but you will get the alternate tuning when you manually select an alternate-tuned model in the Variax.

I also own a StageScape mixer and a set of StageSource speakers. They form a wonderfully integrated and great sounding system. If you can pick up a set of used ones that are in good working order at a great price you will be doing yourself a favour. But I agree (and I have no inside information here) that Line 6 is no longer pursuing their own brand of mixer/speaker products. Since Line 6 was bought out by Yamaha it seems that Yamaha is incorporating some StageScape/Source IP and technologies into their own Yamaha brand of similar products.

Refer back to my previous post in this thread. Helix does not officially support any Variax guitars prior to the JTV series. In particular the Variax 500 is not supported and not guaranteed to work in any way with Helix. Having said that, in that post I described some limited success in my experience with a Variax 300. I have not re-tested any of this with more current versions of Helix firmware. The situation may have changed by now and may change at any future time. You should assume that the Variax 500 will not interact in any way with Helix. Any successful interaction cannot be predicted and would be a bonus.

When you purchase a Marketplace product it is immediately associated with your Line 6 account. But you need to visit your account’s Marketplace area to download it. Have you done this? To get to your account page click on the Support tab at the top of this page. Then scroll down on the Support page and click on Account Services. Then click on Helix Marketplace in the left hand column. Your purchase should appear there and you can download it. Then import the presets and IRs (if any) into POD Go Edit.

You’ll need to open a support ticket to get more info and a possible repair/recovery.