chasingMango

Based on what everyone else has said, using 1/4" out may be a solution. If your stage doesn't have a jack for 1/4", perhaps purchase a DI box and run your 1/4" out into that, then connect the DI box to FOH via XLR. I agree with @DunedinDragon, don't go change your whole rig, you're likely to run into new problems. Also, did you read about being connected via USB possibly causing the issue with the XLR out? Are you connected via USB @barmando?

Bump?

Has anyone else done this?

I own a PC212+. Page 7 of the user manual says: "NOTE: XLR Outputs are not affected by 48V phantom power." Anyone know the difference in architecture between the PC112+/212+, and Helix, which says: "IMPORTANT! Never connect the Helix device's XLR outputs to a device whose XLR inputs have 48V phantom power enabled!" I was about to purchase a 2-channel Line Isolator for my PC212+ plugging into FOH mixers until I realized it lacked the same warning as the Helix. Would the Line Isolator have no affect whatsoever, or would there still be some benefit?

Do you though? The only source of contention in this conversation has been you brother :)

Obviously there is an explanation for why there is a hum - what is the explanation for why this problem could not be avoided through a better/different design? It doesn't exist on the cheaper transmitter/receiver I tried.

I believe people who say they are plagued with issues, I however have never had problems with my G10S playing small church events. Not sure what the discrepancy is. One small annoying thing however is that I have to use an extension on the receiver in my acoustic guitar and my electric guitar with active humbuckers, in order to eliminate a quite noticeable and annoying hum. Fortunately the hum goes away with the extension, but it kind of defeats the ultra portability of the unit. I don't get the same hum when using my friend's much cheaper wireless product on the same guitars. Weird.

Oh, the question was answered thoroughly right away. And no names have been mentioned... I think that's as much as you could ask for!

I have only used the helix with FRFR speakers, so I'm not personally familiar with using it with a traditional amp... but wouldn't you want to use the amp's pre-amp? I wonder if you would like the tone more if you did what I said above, turning off amp modeling on the stomp? With an additional two cables you could try it.

P.S. I am not sure but I think you might be skipping your pre-amp, if nothing is going into your amp's input jack. Try plugging your guitar into the amp input, then run a cable form the fx send to your peddleboard, then another cable from your peddleboard to your fx return.

Not sure that you want to "stick everything in FX return"... the question is which effects do you want on the dry guitar signal before any amplification, and which effects do you want on the amplified signal? This article lays it out pretty well https://www.dawsons.co.uk/blog/how-to-use-an-effects-loop-on-your-amp

What do you mean by "right"? What are you trying to accomplish? Does it sound good?

I'll be that guy and say that the price increase made me appreciate my already-purchased Helix that much more :)

If you are able to make your presets into a single preset and utilize snapshots to change tones... then if you make a change in one snapshot, switch to another, then back to the original, the change will still be there. All changes will go away if you switch presets without saving, but they will remain when switching between snapshots within the current preset.

What @Kilrahi said... just get Native, you could get it later in life but then you'll wonder why you didn't get it sooner, just like the Helix :) I'm assuming you might not have another audio interface to plug direct into your PC... FWIW I have the FocusRight 2i4, it works great and I get ~6ms latency in Cubase+Native on my W10 laptop with decent buffer settings.

Check out Kali Audio https://www.kaliaudio.com/lone-pine-studio-monitors

What do you mean? You can't already place the reverb after the IR block?

Not sure if I stated my case clearly... in dozens of performances, I only had one cutout issue that lasted only a moment. Of course, the tech could be improved... but at the price point, what's available now has done me well.

Gotcha... then I would guess it probably depends on your exact IEM and how you want to use them. If it has its own volume control, then connect to a regular output set to unity, then control volume from your IEM. If you want to control the volume from helix, then connect to phones and program the big knob to control it. Not sure the cables matter if you are not using mono anyway.

I don't understand your use case - are you monitoring yourself only, or dialing in other instruments in the band as well?

Hm... one can hope for 2.9.

Not an ideal solution because requires extra gear but maybe there is some kind of tap tempo midi controller that could send tempo to the helix? I agree that it should average out during however many taps from the last X seconds... thought it already did this. I don't use tap tempo (yet). I guess it only measures between the last two taps?

FWIW it works great for me. I have experienced cutout issues one time in dozens of live performances, it went away after a moment. I'd say if you want an affordable/easy wireless solution now, its a good option. Something better may take years to come out, by that time you can sell your G10S and recoup some money to put toward the new thing. It seems that L6 gear has pretty good resale value.

It does not... one is the left channel, one is the right channel. If you swap the cables between L/R input, the L/R output will swap accordingly. Only matters if you expect certain sounds to be panned left or right.

Ditto this... Helix Native is only 100 bucks, and frequently discounted below that. Well worth the convenience. Otherwise I believe the device you are looking for is called a Studio Monitor Controller. An inexpensive one with only two stereo inputs is about the same price as Native... for your use case, just get Native. P.S. Just realized that it was @CoredusK answering his/her own question... but for others' reference... that is the hardware solution to the problem! Have fun with Native @CoredusK!