silverhead

I agree. Line 6 seems to have dropped that consideration as of the POD HD series. I previously owned a POD X3 Live which was a dual input/tone device. While it didn’t have the dedicated vocal FX you mention it DID have a very handy feature called Lock Tone 2. You could set up a vocal tone in Tone 2 of one preset, activate the lock feature, and then navigate among many presets with different guitar processing using Tone 1. No need to duplicate your vocal tone in all presets; it remained steady. I still miss that feature.

Both options undergo A/D conversion. Helix does it at/in the Input block and passes the converted digital signal direct to the assigned USB dry output channel. Your other device does it at/in the hi-z instrument input block. After that I think everything is the same. So your specific question is: what is the relative quality of those two converters? Personally I have never had an issue with the Helix converters. I can’t speak to your other device. Personally I don’t think it would make an audible difference but I don’t have your ears. I have been using my Helix Rack as my audio interface for more than 10 years and I love it. I think the ability to transfer Helix presets between the Helix device and Helix Native is a huge advantage when wanting to reproduce your studio sound on stage, or vice versa.

Yes, you can set the Input block of the bottom path (Path 2A) to multi or guitar. But this is unnecessary in your case because….. The paths are completely independent; nothing from the top path (Path 1) is ‘picked up’ unless … You direct the Output of Path 1 to the Input of Path 2A. This removes the need to duplicate blocks and effectively creates a single signal path spanning both Path 1 and Path 2. When using multiple amps I tend to assign the Output of Path 1 to Path 2A so that all FX in Path 1 are carried through to Path 2. I place one amp/cab in Path 1 and the other in Path 2. There is sufficient DSP for both amps/cabs and lots left over in each Path for FX processing. You can arrange to have the sound from either amp/cab individually, or a blend of the two. I assign an expression pedal to the Channel Volume parameter with inverted Min/Max settings to control the blend ratio; toe position is 100% one amp and heel position is 100% the other; exact middle position is 50% each; intermediate positions provide one amp more than the other. You can use Snapshots to control different on/off states as well as different parameter settings for both amps/cabs, as well as all FX blocks. There is a tremendous amount of flexibility in preset creation. Experiment with options until your head spins, then take a break and go back at it again later. Repeat for a couple of years, by which time you’ll be ready for Helix Stadium!

Which Helix model do you have? With the Helix Floor, Rack, or LT you have dual DSP processors which provide two independent processing paths. Use both paths and place one amp/cab in Path 1 and the other in Path 2. The HX Stomp only has one DSP processor, and half the processing power. Although it supports parallel paths, that’s different from two independent paths. There will be DSP constraints on the Stomp for what you want to do.

A ‘REAL modelization’ is an oxymoron. By definition a cab model is not a real cab. All Line 6 models, including the new cab engine and models in Helix are captured from real physical amps/cabs/FX pedals. They represent the current state of the art which will never be identical to the physical thing. But the current state of the art is very good, such that many models can’t be distinguished from the real thing in blind tests. Whether the cab models in Helix Stadium, based on the new Aguora modeling technology, sound ‘real’ to you will be determined by your perception of the sound. Nobody can answer your question except you when the time comes. Certainly not now.

I don’t see it as a PowerCab thing. The same is true for Variax users like me; no VDI. I think it makes good business sense to ask the small minority of PowerCab and Variax users to pay for the additional features rather than include them, meaning everybody else subsidizes us.

Make sure you have assigned the parameters to the Snapshots controller.

This might refer to the new cab engine that was introduced in a firmware update some time ago. It was more than reloading presets. You need to change the cab model in the preset, selecting one of the new cabs to replace the previous cab. The firmware update process itself includes rebuilding all presets so that they conform to any new structures or features introduced in the new firmware. This is an automatic ‘reload’ if you want to call it that. I’m not aware of any other changes or improvements that are available by a manual reload of any presets.

Over the years I have seen many threads here about ASIO4ALL failures with Helix devices. It is a non-compliant pseudo-ASIO driver that attempts and usually fails to do things that are unsupported by the ASIO protocol, most notably trying to use different audio input and output devices. I advise against using it.

No, not if you use Helix and the Line 6 ASIO driver as your audio interface device. It’s a restriction of the ASIO protocol. I believe Helix on Mac uses the Mac’s native Core Audio, not ASIO.

Help with what, exactly? What you describe is the normal and recommended setup. Your Helix becomes the computer’s audio device. The ASIO protocol demands that the same device be used for audio input and output. How would you like it to work?

Well, Helix is not a one stop shop. It’s onboard looper is not a fully functional looper either. Who says they’re not considering it? At the top of this page you’ll see a banner about Ideascale retirement. Read that to learn how to submit a feature request.

Let your own ears be your guide. There’s no right or wrong answer. You certainly won’t do any harm to the equipment by connecting things differently and experimenting. What sounds best to you?

All I’m saying is that your symptoms “seem” to indicate a potential power supply issue. If you’re certain that your supply is working fine then the issue must be something also. I have no other suggestions.

In general yes, a buffer before a fuzz pedal can affect the dynamics. But maybe there’s something else going on…. The original manufacturing of the POD Go had a flaw regarding input impedance. This could affect things as well unless you have a Pod Go that has either been repaired (free lifetime warranty) or was manufactured after that flaw was fixed. Contact Line 6 Support if you’re not sure about your specific POD Go.

Those symptoms can indicate a power supply issue. Are you using the power adapter that came with the unit? If not, try testing the HX FX alone with its original power supply. If no joy open a support ticket.

Thanks for the update. Very interesting. I suspect there's some sort of driver conflict on your music laptop. In my experience the most likely suspect is the non-ASIO-compliant ASIO4ALL driver which seems to be the Audacity default. If you want to test this uninstall ASIO4ALL and reboot your computer.

Yes you can get an HX Stomp patch onto Helix. I’m not sure that it can be done directly using HX Edit. Perhaps it can, but you can certainly use a trial version of Helix Native to either create a Helix-compatible patch or at least to inspect and manually recreate it.

Another procedural consideration….. Frankly I’m not sure whether this matters at all but it’s the way I would do it anyway. You haven’t mentioned whether you have any other Line 6 products with installed software. If so I would recommend you also uninstall/reinstall their associated programs and drivers. Uninstall in reverse order of installation time; begin with the POD Go stuff and then proceed backwards in time. When reinstalling, do the reverse; start with the oldest stuff and finish with the POD Go.

That’s a good idea. Make sure you restart your computer after uninstalling. If that doesn’t work then it’s a good idea to phone Line 6 Support and ask for specific procedures to completely uninstall Line 6 stuff manually. Then start fresh. I commend your patience and perseverance. This will eventually get resolved!

Yes, the POD GO Edit download package includes the POD Go Edit program itself as well as the required drivers. But they are separate things. What you download is an installation package. When you run the installer you have an option to deselect certain components such as a driver. It’s not wise to do so, but the program and the driver are two different things. I expect that’s what he is referring to. This doesn’t address your issue. You seem to have all required components installed. At this point I suggest you open a support ticket.

Download and install the original Workbench software, not Workbench HD. This is the pre-JTV Variax editor. It allows you to adjust individual string volume levels. Unless you have a VDI-equipped Line 6 guitar processor (X3 Live, XT Live, some POD HD/Helix devices) you will also need the Variax Workbench hardware interface device. If you don’t already have one you may find them scarce and surprisingly costly.

Not necessary in my experience. If something fails the first time you should do this on the next attempt.

That’s correct. The proper driver is part of the POD Go Edit download package. After downloading, run he installer and select to install all components. I don’t think Reaper provides usb drivers because they apply to hardware devices. A windows system will provide generic usb drivers for its hardware but an audio interface device like the POD Go typically provides its own unique driver. I believe a purely software product like Reaper uses the host hardware drivers. Try downloading and installing POD Go Edit again.

That depends on whether or not you use Helix presets to change the Variax model (or any other Variax settings) in your 600 as you select different presets. There is a Global vs. Per Preset option for Variax controls. If you don’t need/want to change Variax models using presets you can use one preset to set the Variax Volume level to 10 and then set the Variax contro parameter to Global. Any future changes to the Variax controls that are stored in different presets will be ignored as you switch presets until you change that parameter back to Preset control.