rd2rk

You've got it! After you try the DIR presets you can delete those, too. Most users do.

My bad!

Which reset procedure did you follow? If you're not sure, just try it again - reboot holding FS 9+10. It can't hurt to be sure, and your alternative is to contact support, 'cause what's happening is definitely not normal. In fact, it's a glitch I've never even seen before, and I've had my Helix and been active here for 6 years!

Presets have 8 snapshots numbered 1-8. When you open HX Edit on a new preset Snapshot 1 always appears in that spot. Any snapshot can be edited and assigned to control multiple parameters, and blocks' status (bypassed or not) is saved per snapshot. However, the snapshot that loads with the preset is the one that is active when the preset is saved. If the active snapshot when the preset is saved is other than Snapshot 1, that is the snapshot that will appear when that preset is next loaded in HX Edit. IOW - if Snapshot 2 is active when the preset is saved, the next time the preset is loaded, Snapshot 2 will be the active snapshot and will appear in that space in HX Edit.

There's this thing called the "Pan Law". Pan law - Wikipedia By lowering the Path A level at the Mix Block you even it out. Try the attached modded DIRT preset. SVT-4 Dirt Mod.hlx

Attach a copy of the preset (.hlx). You attached a .php file.

When crazy stuff starts happening, do a Factory Reset. Don't forget to make a backup first.

TL;DR - L6 Link works fine UNLESS you try to get too fancy with changing Modes WITHIN PRESETS (MIDI use case), and if you encounter the no audio problem with the PC112+ it's simply a matter of the order of activation. The Whole Story (AFAIK) - The L6 Link cables do not carry MIDI. The Link protocol is intended to replace MIDI. Unfortunately, there are bugs which L6 refuses to address. This is why I mentioned that I didn't know how using a 112 with a 212 would work out. You're kind of in uncharted territory there, since it's an uncommon combination. In the case of my PC212+ the main problem I found was inconsistency in controlling the HF Driver. It's supposed to be OFF when using Speaker Emulations and ON when using FRFR and USER IRs (USER IRs are stored on the PC212 vs cabs/IRs that are part of the Helix preset). In some scenarios when switching between FRFR and Speaker Emulations the HF Driver would not turn ON/OFF as expected. Part of the reason L6 has not addressed the issue is that this behavior is extremely random, and random bugs are very difficult to track down. However, when using MIDI to change between the modes there are no such problems, which points to L6 Link as the culprit. For this reason I use L6 Link as the audio transmission method (and for simple speaker/IR changes) and MIDI when changing MODES (WITHIN A PRESET). Since most of the misbehavior seems to occur when changing MODES (WITHIN A PRESET - for instance, using a snapshot to switch between FRFR and a Speaker Emulation) adhering to the KISS (Keep It Simple Stupid) philosophy OR using MIDI eliminates the problem. IOW - unless you insist on pushing the envelope WITHIN PRESETS, L6 Link works fine for most purposes. There's some other problem when using two PC212+ at once as relates to changing Speaker Emulations in a coordinated fashion between PCs, but since I only have the one PC212+ I've never experienced this. Again, this seems to be a problem that occurs when making changes WITHIN A PRESET. Another reason I'm not sure how combining the two different PCs will work out, so KISS. The only problem I recall with the PC112+ is that the PCs need to be turned on in a specific order, else the second PC doesn't properly receive audio over L6 Link. A non-issue once you have the order down. I want to reiterate in case it's not clear. L6 Link works fine UNLESS you try to get too fancy with changing Modes WITHIN PRESETS, and if you encounter the no audio problem with the PC112+ it's simply a matter of the order of activation.

The main point of using the digital cables is to enable per preset control from Helix. If you're not using L6 Link end-to-end you might as well just use standard mic cables. In that case (and with the QC) it makes sense to run stereo to the PC212, but L/Mono Out from the 212 to the 112.

The usual method is to use two AES/EBU cables - one to the first PC and the other to link them. IDK exactly how this will work with a 112/212 configuration, most I've heard of use two of a kind.

Yes, scabs can be quite the problem!

This is sounding like something that's been reported before. Try contacting support and emphasizing that last bit about the zero volume setting.

If they still haven't figured it out 3-1/2 years later... Oh, sorry, first post - WARNING! Beware of Zombie threads! :-) Welcome to the Community!

Spitballing here. IDK how far back your issue goes or how you create your presets, but one thing I've found is that when using dual cabs (or multiple amps/cabs in a stereo preset), different amp, speaker and mic combinations can cause imbalances in the stereo signal. Also panning. Maybe unrelated, but something else to look into?

If you have a FS set to send a CommandCenter function (vs simple bypass or parameter change) it will do that if you have Global Settings>Footswitches>Stomp Select set to TOUCH or TOUCH AND PRESS and you're playing barefoot or in thin socks.

If you read the .pdf I sent and you're still lost, I don't know what to tell you. It's the best amp mic'ing primer that I know of.

Start here. It was written for the old versions, but it's all about mics. People who excel at mic'ing amps spend a lifetime learning how. Mostly thru experimentation. Sorry, there's no magic "Do this for great tone every time!". FWIW - the most commonly used formula is an SM57, Cone Edge 1" off the grill, plus an R121 back about 3-4 inches. This is approximately Mix 01 in the York Audio packs, which many people swear by. EDIT: Don't blow off the newer Helix cabs. They are just IRs and provide the same flexibility as the Redwirez without needing to load a new IR for every change, just not as many cab options (yet). I don't know about the new Redwirez version, but the original had just about every mic position and cab possible. So many that it was overwhelming and is at least in part responsible for making the aftermarket of "sounds like (heavy dark thick thin etc)" IR creators possible. DialingInYourTone.pdf

That's not what I meant. Doesn't the QC have an Output Block Level parameter (I just looked at the manual - it does)? Turn it down there and save the preset.

Works fine. What seems to be the problem?

The clip LED indicates that the signal at the PC input is too hot. That means, conversely, that the signal at the output of the QC is too hot. Turn down the signal from the QC at the QC's output. Keep in mind that a distorted tone is a compressed tone. A clean tone has more dynamic range and will be easier to clip with changes in picking dynamics, so the "keep the clip LED in the yellow/amber" rule might need to be viewed more as "just when picking hard".

The FX Loop impedance is 1M regardless of its location in the chain. Try this. Run the SEND directly to the RETURN, no FX in the loop. Assign a FS to bypass the Loop Block. Play. The signal should be the same with the Loop Block active as it is when bypassed. One at a time, try the devices in the loop. Unless I'm mistaken, all of the named devices are stereo. Be sure that you're using the MONO connectors.

That's not the preset in your screenshot, but nothing about it jumps out at me as being a problem. What are the actual external FX that you're putting in the loop?

If you're using "stomp" type FX (vs pro-grade rack FX) they expect an Instrument level input, so make sure you have the Send/Return set to Instrument. If that doesn't fix it then attach the preset itself, a snapshot does nothing for me.

… When I was back there in Seminary School There was a person there Who put forth the proposition That you can petition the Lord with prayer Petition the Lord with prayer? You cannot petition the Lord with prayer! - Rt. Rev. Jim Morrison

Thanks. I didn't know that.