rd2rk

I can't really define the difference. It's just better for guitar. The FRFR112 was then relegated to bass amp duties when I got a PC112+, which then got traded for a PC212+. I'm finally really happy with my sound.

If everything is set correctly there should be no noise. If, despite everything being connected correctly, there's still noise (DEFINE noise), there's a small possibility that you have a bad board. When I first got mine, back in 2016, I had this problem. Support had me return it to them for repair. Round trip <1 week. I've had no problems since. With just the Helix and 18i20 connected (NO DAW) CALL support and let them listen to the noise.

SimonGugala - If you're convinced that your problem with HXFX is a bug that needs to be "fixed", you should contact support. This thread was started by someone with the HXS, and while the problems may seem related, trying to troubleshoot both boxes in one thread is becoming confusing for all involved. AlchemyStrat - As I mentioned, I do not hear what you are hearing. A line in signal is just that, whether it's coming from the LINE OUT of your loadbox or from the FX Send of my amp makes no difference. You'll always hear it when the IR mix is at 0%, but should not hear it as a distinctly separate sound at 100%. Did you try replacing the IR with a reverb at 100% to see if you still hear the direct sound (would point to a problem with the IR block mix function)? Did you try my suggestion about raising the IR signal vs the direct signal to see if that helps? We're remote troubleshooting here, and things like that can give us hints as to what might be happening. Also, did you try Schmalle's suggestion about the Aux/Return setting? Also might help if you attach a copy of the preset that you're using so we can more accurately attempt to duplicate the problem.

From the manual page 33 "Impulse Response Settings" MIX Blends the IR signal with the dry signal passed through the IR block. When set to 0%, the path bypasses the IR completely. When set to 100%, the entire path is fed through the IR, and no dry signal is heard. So, yes, at 0% you WILL hear the DRY signal. BUT, at 100%, how are you isolating the DRY signal? Because, AFAIK, this is the way that all of the MIX settings work on ALL of the FX. If I put a rad reverb in there at 100%, I don't hear ANY dry signal. With a subtle effect such as an IR, at 100% there's no way I can tell if there's any dry signal still mixed with the sound. Try this. Even with the IR at it's default -18db, the level difference between mix at 0% and 100% was pretty big. Try upping the IR Level to 0db (unity) and compensating for the overall output level increase by lowering the Output Block level (so as not to overload the AI Inputs). Are you still hearing it?

This is where you go if you're serious about suggestions for changes and improvements: https://line6.ideascale.com/a/index Before posting a new idea, please search to see if it's already been proposed. If 100 people vote on the same idea presented 20 different ways, it looks like only 5 people care about it! Also, post your ideas one at a time. I for one NEVER vote for multiple combined suggestions.

It would still need to be done on every preset, and be a waste of a block and a split.

I wonder how long it will take for the improvements in MIDI 2.0 (such as two way communications) to be considered important enough to enough non MIDI geeks to be widely enough implemented to matter....did I use enough enough in that sentence?

$13.99 AmazonSmile: Monoprice 3ft Premier Series XLR Male to 1/4inch TRS Male 16AWG Cable (Gold Plated): Musical Instruments I'll vouch for the quality of and warranty on Monoprice cables. Even if you get two for stereo, still cheaper than a stereo DI Box.

To answer your other question, if you need the 2i2 for a second instrument or mic, you can use the same connection as you use for the M60/FOH. Otherwise, there's no need to use the 2i2, as your HXS is a fully functional Audio Interface. It also has the advantage of allowing you to record a DI track simultaneously with your HXS processed track for later re-amping with NATIVE or your amp sim/effects of choice.

How are you monitoring the Helix output? Using two different monitors, one being MIDIOX, both my Helix and HXS are sending the correct octave. However, there's this to consider: There is one, nagging discrepancy that has crept up between various models of MIDI devices and software programs, and that concerns the octave numbers for note names. If your MIDI software/device considers octave 0 as being the lowest octave of the MIDI note range (which it ideally should), then middle C's note name is C5. The lowest note name is then C0 (note number 0), and the highest possible note name is G10 (note number 127). Some software/devices instead consider the third octave of the MIDI note range (ie, 2 octaves below middle C) as octave 0. (They do this because they may be designed to better conform to a keyboard controller that has a more limited range; one which perhaps doesn't have the two lowest octaves of keys which a 128 key controller would theoretically have. So they pretend that the third octave is octave 0, because the first two octaves are physically "missing" on the keyboard). In that case, the first 2 octaves (that are physically missing) are referred to as -2 and -1. So, middle C's note name is C3, the lowest note name is C-2, and the highest note name is G8. This discrepancy is purely in the way that the software/device displays the note name to you. SOURCE: MIDI Note Numbers and Names (teragonaudio.com)

You are correct. On Helix it's "First Enabled". On the HXS it's "Enabled". Oops.

Since 1M is what plugging straight into an amp gives, unless you've got some reason to want something else - "authentic" tone from certain old fuzzes - 1M gets the proper high frequency response from most humbuckers. Glad you worked it out!

In Global Settings>Preferences set Auto In-Z to FIRST (HXS) or FIRST ENABLED (HELIX). In your Presets, in the INPUT BLOCK, leave IN-Z set to AUTO. This allows Helix to set the Input Impedance (which loads your pickups) to the impedance that the first active effect or amp expects to see. If you're using pedals between your guitar and the Helix, your pickups will be loaded (affects high frequencies) at whatever those pedals' impedances are. If you're using wireless, your pickups are always loaded at 1M. If you need a lengthy and pseudo scientific explanation of what all of this means, there's a huge long thread over on TGP in the Digital and Modeling Forum started by @Tito83 where it's all explained over and over in painful detail. Suffice it to say that L6 included the settings I described above in v3.0 largely as a result of that thread, and credited @Tito83 in the release notes.

Not describing the type of cables you're using, from which HXS Outputs to which VS inputs.

I'll throw in that the same website where you get the UNO2 chip also sells the UNO 1.0.4 chip and it's GUI editor. This chip falls between the very limited stock chip with Mtnsys/Ed Dixon GUI editor and the fully programmable UNO2 with actual code editor.

Simplest method: Connect both guitars to the Inputs. Roll off the volume on the inactive guitar. Done.

Any Value between 0-63 is OFF, 64-127 is ON. Though the LT Manual SAYS 0-127, if it toggles between 0-64, that will work. I just tested it using HXS and NATIVE, works fine.

Long title for a frustrating subject. I've posted at length on this, as have others. Until today I was SURE that using L6 Link, the Powercab was NOT properly turning ON/OFF the HF Driver (HF Trim) when changing Speaker/IR Modes. This was partially based on visual feedback from both Powercab Edit and the actual screen on the Powercab. Partially it was based on not trusting my ears. Today I tried a different approach to the problem. Using a stripped down signal chain, I created two nearly identical presets. Both have a Crunch amp, a stock cab and an IR (Allure). These are switched via snapshot. A third snapshot turns both cab and IR off and loads an equivalent speaker emulation. All are V30 models. Attached are the presets. In Mode Test1, the L6 Link is doing all the work. In Mode Test2 I'm using MIDI to MAKE SURE that the HF Driver (HF Trim) is turning ON/OFF when it's supposed to. In Mode Test1, neither Powercab Edit nor the physical display on Powercab reflect the HF Driver (HF Trim) being turned off. In Mode Test2 they both reflect the change. To me, at 10 PM after messing with this off and on all day, they sound identical. I may be suffering auditory burnout. I may be losing my mind. I hope someone will take the time to try this comparison, and let me know what you think. NOTE: you'll need a MIDI cable to do this. NOTE2: In your reply, please say if you tested with PC112 or PC212. I have the PC212. Thanks to all who choose to take part. Mode Test1.hlx Mode Test2.hlx

HF Trim - Page 18 of the PC Manual, third item down. It controls the Output Level of the HF Driver. In PC Edit you'll find it on the SYSTEM Tab, right below the Input 1/2 Gain controls. It doesn't SEEM to affect the Clip light (doesn't add enough gain?), which is part of the reason I wonder why the FRFR and Speaker levels DO affect the Clip light. I think it's a bug, and the PC's internal level settings should NOT affect the clip light. But, again, it could be an engineering thing, and until somebody technical at L6 checks in, we're all just guessing. As for Jason's video, since the Input 1/2 Gain controls only affect the analog inputs (as far as I can tell), and he says at the beginning that he's using L6 Link, I don't know why he would even mention those. I don't have time to re-watch the whole thing to find that spot, but if he says then that he's using XLR, he's contradicting himself. Maybe he used different methods in different parts of the video? Anyhow, the XLRs are how I bring in a VST, and using a VST or an HXS or anything that doesn't have L6 Link, the Input 1/2 Gain controls are the ONLY way (EDIT: except for the FRFR/Speaker Level) to set the clip indicator (isn't Input Gain what an Input Clip indicator monitors?), so I have no clue what he's talking about.

Well, there is an Input Trim Control, it's on the System Tab in PC Edit, and in the System settings on the Powercab itself (press and hold the HOME button). It can be controlled via MIDI PC#5, and the settings go from OFF (PC#5 Value 0) to +12db (Value 127) with 113 being 0db - not 100 per the PC Manual. My problem with the implementation is that it's about the only Global PC setting you can't access on Helix itself from the GLOBAL Tab on the Powercab dialog.

Yes. It makes NO sense to me that there would be any other way to affect an INPUT clip indicator other than the OUTPUT level of the device that's feeding it. The SPEAKER level and IR level in the Powercab are OUTPUT levels within the Powercab. Makes no sense at all, and I think it's a bug. But, as you say, that's a L6 engineering problem, and they're not talking about the Powercab AT ALL - not here, not over on TGP - no feedback from L6 at all where Powercab is concerned. Scary.

Couple things I didn't mention. At the split block, Pan the signal LEFT/A100. That prevents guitar from mixing with the synth. At the Path B Output Block, if you're using RETURN L/MONO, Pan the Output Full Left. That puts 100% of the signal onto USB 3. Vice versa if you're using RETURN R.

Plug the synth in to the Return(s). Put the Return Blocks on Path B. Pull down the Mixer Block to separate the Outputs. Use USB 3/4 to bring it into Ableton.

I have a two button switch (Moskey). I set the Ring (FS5) and Tip FS4 to Normal Polarity and they send NOTE ON before (On Press) NOTE OFF (On Release)..

Over on TGP there's a thread in the Digital and Modeling forum about the XL. In it, DI explained that the only reason that the XL exists is to satisfy the common complaint of "not enough footswitches", and that it wouldn't have happened at all if it hadn't been a cheap fix to that specific problem. It was not intended as a "New and Improved" Stomp except for more footswitches. FEAR NOT! They still love you!