rd2rk

In Ableton, on the track strip there's a section called MONITOR with 3 settings - IN, AUTO and OFF. If you have that set to ON or AUTO while recording you'll hear the incoming signal. If you're Direct Monitoring at the same time it will be delayed by the latency amount and at higher latencies can sound like an echo. If the sound that you're recording also has delay/reverb it might not be obvious. When DIRECT MONITORING set that to OFF. Playback will work as expected.

Partially correct. "Copy/Paste All" is fine if all you want is for every FS to do the same thing in every snapshot. Refer to the last fix I sent. Is that the case? No. If you're in SS2, what is the point of having a FS wasted by being assigned to SS2? In each snapshot I assigned the FS for THAT snapshot to go back to your general rhythm snapshot. That may not be exactly what YOU want it to do, but the point of every fix I sent was to teach you how to use CommandCenter, and there's more to it than copy/paste. Incorrect. In Helix Edit CommandCenter, just right click on any FS and you'll see the copy/paste all options.

As long as you are not PLAYING through a plugin, latency is not an issue even with the Helix drivers. Simply RECORDING the Helix over USB, while MONITORING direct (Helix to speakers) is the proper use of Helix and you don't need anything else. Once you have a recorded track, any latency involved in recording additional tracks while monitoring the previously recorded track (still DIRECT MONITORING Helix) is compensated for within your DAW. Again, you don't need anything else. Save your money for more guitars!

SPDIF won't help unless you have the Helix Floor or Rack model, as the LT does not have SPDIF. You'd need to do some research for a PCI soundcard, I've been using laptops for years. TBH, your biggest impediment to ultra-low latency is probably your computer. Why is low latency important? Are you planning on playing through amp-sims, as opposed to direct monitoring through the LT while recording?

Buy a better interface. Helix as interface is perfectly fine for recording while direct monitoring and for re-amping into Native or other amp sim. It is NOT designed for best latency when PLAYING through Native or monitoring live with ITB processing. My Floor and HXS both get 12.6ms RT latency at 48k/64spls. That's the best they can do. My 2nd gen Scarlett 18i20 gets 7.6ms at the same settings. With that interface I also cut 2-3ms because I can use SPDIF. Your LT (and most AIs) doesn't have SPDIF, so figure 7.6 + 2-3 for the AD/DA conversion at the AI + 2-3ms Helix throughput. Net gain nada. Also consider that I'm using a 7th gen i7 with 16gb. With your 12th gen i5 you MAY be able to use a lower sample rate (16/32) to get lower latency, but 64 is the best my old 16gb i7 will do without glitches. Also consider that my Scarlett is not the lowest latency AI you can buy, nor the most expensive. A 12th gen i9 would do much better, maybe as low as 4ms. Maybe less with a VERY expensive AI. How much money you got?

That's why I wanted the actual preset. See the BOLDED parts above. Using the FX Loop works but is unnecessary as you're only using the SEND half of the Loop. A more "elegant" solution is to use a SEND L with the DRY THRU set to -120db. Your method works, I just would do it differently. NBD. The Output muting is just unnecessary. When the FX Loop is enabled, there's no signal passing THRU the FX Loop to the second half of the signal chain and the return signal from the DAW is going straight to the Main Outs, bypassing everything after the FX Loop. When the FX Loop is disabled, no signal is being sent TO the DAW, therefore there's no signal returning FROM the DAW and no need to MUTE the DAW Output. If you also want to record the FX Loop Bypassed signal, just create another track with USB 1/2 as inputs. Be sure to turn OFF the Track Monitor Switch to prevent an echo. Small things, but you did ask for comments... Try the attached mod to your preset. Sorry if I was a bit testy about posting the preset. My brain works best when looking at both an explanation and a practical implementation. I try to be helpful with everyone who posts here. You'd be surprised at how many people want me to re-write the manual and create complex custom solutions for them, but if I ask them to post an example of the preset they're working with they act like it's a CIA National security need to know thing. AARGH! Merry Christmas! LOOP Mod.hlx

Thanks for posting your preset. Very helpful.

It depends on the mixer. There's usually a switch or a pot on the mixer channel that sets the incoming level and an LED that indicates overload. MIC level is lower than LINE level. Start with MIC level at the PC's XLR (DIRECT) Out and set the mixer's switch/pot accordingly. Remember that the level being sent to the XLR Out is relative to the level that's hitting the PC's Input, NOT the setting of the PC's Volume knob. Generally accepted practice is to have the PC's Input LED in the yellow/amber when your modeler's preset is at maximum (all ODs and Boosts ON) and digging in. If you're setting the PC's XLR out to MIC and the mixer's channel is overloading despite setting its pad switch/knob at its lowest setting, then you have to turn down the PC's Input 1/2 Gain (I leave them linked so I only need to turn one down). This way if you've got your presets properly level matched you don't need to mess with the preset levels.

Have you actually tried this? I have many better ways to interface, so I hadn't bothered since I got my PC212, 2+ yrs ago). At that time I was not impressed. The latency was awful. Just for kicks I DL'd and installed the latest ASIO Drivers (v1.97 - 12/1/22). 7th gen i7 16gb Win10 laptop. Powercab's ASIO driver comes up in Reaper as 48k/64spls (could be because that's my defaults with other interfaces) which results in 16.4ms RT latency. That's fine for recording, which is the primary purpose of using the PC as ASIO interface, but not exactly "low latency". My usual interface is a 2nd gen Scarlett 18i20 which gives 7.6ms RT at those settings. Even Helix is better at 12.6ms RT. Attempting to open the PC's ASIO Configuration panel from Reaper causes a hang and eventual crash if you don't select OK or Cancel from the otherwise blank panel. I repeated the experiment with Cakewalk, same results all around. Conclusion: If all you want to do is record while direct monitoring thru Powercab with a backing track or EZDrummer, it works. I would not want to process the guitar signal with plugins before returning to the PC as the latency at 16.4ms is abysmal. Helix is not much better at 12.6ms RT, which is why I use the Scarlett which itself is not the fastest AI out there, but at 7.6ms works for me.

Download them to a directory on your computer. Click on the "guitars" icon in the upper left corner. Select LOAD PRESET and navigate to the location where you saved the downloaded preset. Select the desired preset and click OPEN. Again, click the guitars icon. Select SAVE current preset to Catalyst. Select the desired location (Bank/Channel) and click SAVE.

When you did the update, did you follow the directions including pre-update backup, post-update factory reset and finally restoring you backup including Global settings?

I just re-read your post and some things don't make sense. Please attach your preset so I can see what you're doing. Thanks.

A couple things. If you use a stereo send (SEND L/R) you can keep an end-to-end stereo signal for use with dual amps or stereo processors. Set the DRY THRU parameter of the SEND Block to -120db. That prevents the dry signal from going directly to the MAIN 1/2 OUTS and being mixed with the return from the plugin. ADVANCED VERSION: Set the Input Block to USB 5/6. Plug your guitar into L/MONO Return. Split the Path with a RETURN L Block followed by whatever FX you want BEFORE the plugin on Path B, then pull down the MERGE/MIX Block to completely split the paths. Set the Split to A/B with the signal panned full LEFT (Path A). Add whatever FX you want AFTER the plugin to Path A. Your signal path will be Guitar into RETURN L>Path B FX to USB 3/4>Plugin (I use this configuration with ToneX)>USB 5/6 from plugin to Path A Input and FX>Main Outs 1/2. Your plugin (or Standalone if not using a DAW) should have its Input set to USB 3 (or 3/4 if using stereo FX before the plugin) and its Outputs set to USB 5/6. NOTE: you lose the auto impedance function, but that only matters if you ABSOLUTELY MUST use FX that require the lower impedance settings for AUTHENTIC tone (mostly older fuzzes). Demo preset attached. ToneX.hlx

Use a breakout/insert cable such as this: AmazonSmile: Hosa STP-204 1/4" TRS to Dual 1/4" TS Insert Cable, 4 Meters : Electronics OUT 1 = TIP OUT 2 = RING Global Settings>Preferences>EXP/FS TIP = EXP1; EXP/FS RING = FS5 Global Settings>Footswitches>FS5 Function = ToggleEXP I find that when adding the wah/vol blocks, adding them both at once before saving the preset works most consistently, but that could just be one of those "I've always done it that way, so..." thing.

If you look at the bottom of the screenshot he's using you can see that he's on v2.91. Changes were made around v3.0 IIRC. You're not the first to be tricked about something by referring to one of his old videos. As @themetallikidsaid, you can choose a color for a snapshot, just not in CommandCenter. The NAME on the Scribble Strip will always be the name of the Snapshot or Preset.

As a powercab owner I'm getting used to this crap. I opened a support ticket on this. Probably never hear back, but WTH.

Nobody from L6 hangs out here. Post your idea here Line 6 Ideas - by IdeaScale | Popular AFTER you've done a search and voted for the other 27 requests for that (there's a proper name for it, not on the tip of my tongue) and similar features.

Sometimes, sometimes not. Whatever sounds best. ALWAYS!

If you're going to reference a video, provide a link. A timeline reference is also helpful. The color/naming options are available for everything EXCEPT HX Snapshot, HX Preset and HX Looper.

What do you mean by "swap over"? You want to move SS1 from FS1 to FS3 and SS3 from FS3 to FS1? Touch (don't press) both switches and push the "OK" knob. Done. Repeat as needed until the switches are arranged as desired. I can make any changes I want in a preset, because I know how it works. The whole point of that last fix preset was to show that you can make not just one, but MANY changes without breaking CommandCenter. You want me to write a tutorial on how to use CommandCenter to do anything in any situation? Why do you think that L6 hasn't done that? Because they're lazy? No. Because there's lots of possible interactions, and NO WAY to guess what any given user might want to do in any specific situation. You asked for certain things. I gave you demo presets showing how those things are done. Study the presets I've made for you. When you press a FS to go from one SS to another, what are the settings in those snapshots? How do they interact? I've explained that you can use a FS or IC for a certain FUNCTION that has certain PARAMETERS, and that you can change the PARAMETERS between snapshots but not the basic FUNCTION. A FS can't switch from the SNAPSHOT FUNCTION to the PRESET FUNCTION between snapshots. If you change the FUNCTION of a FS or IC in one snapshot it changes the FUNCTION of that FS/IC in ALL snapshots. But you CAN have different PARAMETERS assigned to that FUNCTION in different snapshots. If you assign a FUNCTION to a FS/IC with a specific PARAMETER other than the default, that FS/IC will have the DEFAULT PARAMETER assigned in all other snapshots. That's why if you assign a FS to go to a SPECIFIC snapshot, when that snapshot opens the scribble strip for that FS will say SNAPSHOT^. SNAPSHOT is the FUNCTION assigned to the FS across ALL snapshots, ^ means "NEXT" which is the DEFAULT PARAMETER of that FUNCTION in THAT snapshot. You can then change the PARAMETER in the second snapshot, but not the FUNCTION. Also, don't forget, if you have "SNAPSHOT EDITS" (Global Settings>Preferences) set to DISCARD, that is EXACTLY what will happen to your edits when you press that FS and go to the assigned snapshot! Set SNAPSHOT EDITS to RECALL! Then, just to be sure, when the edit works as expected, SAVE THE PRESET ANYWAY! Before I go any further, understand that all those caps in my explanation are not YELLING, they're EMPHASIS on the terms you need to understand and pay attention to if you want to understand this stuff. HOMEWORK ASSIGNMENT - start with a NEW PRESET. In SS1 assign FS1 to SNAPSHOT2. SAVE the Preset as TEST1. Change to the next Preset, then change back. Snapshot 1 was SAVEd as the DEFAULT snapshot so that's the snapshot that loads when you load the preset. FS1 Scribble Strip says SNAPSHOT2. Press FS1. Now you're in Snapshot2. FS1 Scribble Strip says SNAPSHOT^. Now, in SS2 change the PARAMETER of the Snapshot FUNCTION assigned to FS1 from NEXT to SNAPSHOT1. SAVE the preset, go to the next preset then back. You SAVEd the preset with SS2 as the default, so SS2 is loaded and FS1 Scribble Strip says SNAPSHOT1. Press FS1. Now you're in SS1 and the FS1 Scribble Strip says SNAPSHOT2. Now change the FUNCTION assigned to FS1 from SNAPSHOT to anything else. What is the assigned FUNCTION in each snapshot? What do the Scribble Strips say? Now imagine that your INTENTION was for FS1 in SS1 to do whatever, but you wanted FS1 in SS2 to still switch to SS1. IT DIDN'T WORK! COMMAND CENTER MUST BE FAULTY! WHY DIDN'T HELIX TELL ME THERE WAS AN ERROR? It did. Right there on the Scribble strip. It didn't say ERROR because there's no way Helix could know that it wasn't your INTENT. Whatever FUNCTION is displayed on the Scribble Strip in any given snapshot is the FUNCTION assigned to that FS in EVERY snapshot. Only the PARAMETERS can be changed between snapshots. This may be part of L6's reasoning behind not allowing custom naming of the Scribble Strips for CommandCenter assignments? Displaying the FUNCTION acts as a VERY low level "WARNING! DO YOU REALLY WANT TO DO THIS?" Lastly, it is possible to corrupt a CommandCenter configuration. Nobody knows HOW or WHY, and since it's nearly impossible to do it intentionally and consistently, there's no way for L6 support to figure out what's happening. Sucks, but it is what it is. Computers. Programmed by silly humans. If we don't tell them EXACTLY what to do, there's no telling WHAT they'll do. Enter Skynet. Exit silly humans. I hope the above helps with your understanding of CommandCenter, and also why there's no "Idiot's Guide". All of that explaining only covers ONE aspect of using CommandCenter for a SPECIFIC purpose.

I've tried this before. Did you post this elsewhere? Anyhow, even using a Spectrum Analyzer and multiple EQs, I could get close, but the GR5 amps/cabs have their own sound and I couldn't find a way in Helix to duplicate it exactly. I just happen to also like that GR5 preset so I spent 3 or 4 hours on this (slow day, bored), but I admit that tone matching is not my forte. Maybe someone else can do better.

"I swapped over one of the snaps to a different snap just to test the theory" A configuration is exactly that, and you can't just take a piece from here, stick it over there and expect the system to go on functioning as designed. A liver is NOT a spleen. I'm going to be honest here. While there's always the possibility that there's a problem with your Helix, it seems more likely that you still have not fully grasped how CommandCenter works, and your attempts at custom design are doomed to failure until you do. Your best bet is to just go back to using the basic, default functions as they were designed by L6. Play your guitar and maybe keep a copy of this preset as a "project", or experimental learning tool. Revisit it when you're feeling uninspired on guitar. Eventually you may experience an "AHA!" moment and it will all fall into place for you. Good Luck!

Since you're the only user I've seen reporting this, here or elsewhere, it can't be a widespread problem. Back up your LT and do a full factory reset. If it persists, re-install the FW. If it STILL persists, contact support.

So, you don't want any Helix FX (OD,Dist,Mods) in front of the GM's preamp, you want to send the unadulterated GM Pre thru A,B,C Helix FX, then into an IR and on to FOH, like this: Guitar>GM Input>GM Pre Out>Helix Input>A,B,C FX>Helix Send>GM Return>GM Power amp>GM speaker > Helix cab/IR>Helix Output>FOH IOW, the GM's pre into an IR and out to FOH? I can't imagine that would sound good. Why not (if you really think an IR on Helix will sound THAT MUCH better than the Red Box): Guitar>Helix Guitar In>X,Y,Z FX>Helix Send1>GM Input>GM Send>Helix Return1>X,Y,Z FX>Helix Send2>GM Return>GM Power Amp>GM Speaker V >Red Box OFF>Red Box Out to Helix Return2>IR>HX Out to FOH If it was me, I'd be thinking really hard why I'd want to complicate my life vs just using the Red Box Out to FOH. I find it hard to believe that H&K would have gone to all of the trouble and expense of licensing and building in the Red Box if it really sucked that bad. As to MIDI, yes, anything the GM needs MIDI for can come from Helix. You use Instant Commands (up to 8) in CommandCenter which load at Preset Load (from the default Snapshot) and again (with required changes) when each Snapshot loads.

You have the basics, just need a drum program. Since you've not yet committed a lot of time to Reaper (what I use mostly, with EZDrummer) or Ableton (what I use when I feel like loopy elektronika), may I suggest Cakewalk by Bandlab? FREE and comes with a drum program and some other instruments. Easy to use, too. Once you have a drum program, MIDI drum tracks are all over the place, just Google it.