rd2rk

This is a user-to-user support forum. Nobody from L6 hangs out here. Based on posts I've seen over on The Gear Page Digital and Modeling Gear forum (where L6 people DO hang out), they're not saying much about it (as is the L6 Way where future plans are concerned), Helix Native will likely stay Helix-centric. If a new Native-like plugin is created, it will likely be Stadium-centric. As of now, that's all anybody thinks they know. Sign up on TGP or follow in the various Facebook and other social media platforms if you want to keep up with the latest Stadium news/speculations.

You're getting the DI recording, you just can't SEE the waveform in Logic. Correct? IDK, as I'm a PC guy. I tested in Reaper, Ableton, Cubase, Studio 1, Cakewalk Sonar and Protools. The only problem I encountered was in ProTools, which simply would not accept signal from USB7 or 8. Not surprised, I HATE ProTools!!! Anyhow, this sounds like a Logic problem. Contact support (Apple?) and see if they can figure it out.

AFAIK, Helix models the effect of the Speaker Impedance Curve (SIC - google it) in the Power Amp section of the model, as that is where it occurs ITRW. There's also an interaction between the Pre and Power amp section modeled that obviously wouldn't occur between your digital pre and a separate analog power section. At least that's my take on it.

Why did you ask for advice if you won't even try the obvious next step???

In case no one replies - Backup your existing presets to your computer. Do the Factory reset. SAVE to your computer whatever originals you want to have access to. Restore your backed up presets. Import whatever originals you want.

That may well be the case. The internet is confused about your CPU's W11 compatibility. I got 2 different answers from Google's AI depending upon the wording of my question. My main music system is an 11th gen i7 and came with Win 11 preinstalled, but it does not have a camera or microphone. I tested OBS on an ancient i5 Win10 laptop with no issues. Good Luck!

Contact support. If it's being caused by the "known issue" they'll take care of it regardless of warranty status.

No, not in MIDI 1.0, which is the current implementation in most HW, SW and controllers. While it is technically possible in MIDI 2.0, it requires both the controller and the HW/SW being controlled to implement the new 2.0 spec in a compatible way. Just as it took many years for the one-way communication in MIDI 1.0 to be widely implemented, it will take many more years for 2.0's 2-way capabilities to be widely implemented.

I found it in that subheading, and mine is the same as yours, so that is not the problem. Check the Catalyst listing in Sound, video and game controllers. I asked some posts back, what processor are you running, but don't see where you answered. Could be that your processor, if not Intel, is not properly compatible. If it is Intel, try updating all of your Intel and other Motherboard drivers. I'm really just throwing spitballs at the wall to see if anything sticks. Since you're using free SW you probably won't get much support from the publisher but that might be your best bet at this point.

What is the Device Manager Path? Device Manager>Sound, video and game controllers>Catalyst 100-112 I don't have a listing for Digital Audio Interface,

Go to the source. Open a support ticket and explain the problem and the results of your trip to the repair center. If you live in the US they'll probably have you send it to them. If not, they'll know what to do.

A couple of things. First, this is a user-to-user support forum. Nobody from L6 hangs out here. Second, the Helix line is approaching EOL. There will be no further MAJOR updates, just bug fixes and maybe a new effect or two. This is per L6 by way of the forums they are active on, such as The Gear Page and Facebook. Third, the LT is the budget model. The full-fat Helix with scribble-strips solves those problems. Lastly, the new flagship line, STADIUM, is on the shelves. IDK if it solves your problem but it's a major step up from Helix and certainly worth looking into. Any new "features" requested by users in the various online forums (other than this one) are likely to be implemented there.

Have you performed all of the recommended optimization steps? Do that. If it doesn't fix the problem, then I don't know what to tell you. Contact Microsoft?

Overheating? If your Helix is on a carpet, put it on a hard surface. I use a 12"W x 24"L shelf, but any hard surface that gets it off the carpet will do. Ask the Service Center if they opened it up and blew out the dust.

IF NO THEN download and install the Catalyst ASIO driver. Line6 Catalyst Driver 2_5 v2.0.0.0

Do you perchance have the XLR and 1/4" outs set differently in GLOBAL SETTINGS>INS/OUTS?

Are you using it on a carpet? IF YES THEN put it on a hard surface. I use a shelf. If that doesn't work, as @silverhead said or, if there's no service center nearby, contact support. If it turns out to be a known issue they'll sometimes take care of you even out of warranty.

Reaper works fine in Win11. Start by following my advice about optimization. That might solve all of your problems, or at least uncover something. Out of curiosity, what processor are you running?

I've had mine for 10 yrs and never noticed that, so I just tested it. I don't hear it. Nor was there a difference when I had a Powercab switching from Multi to Digital. Not that it should matter, but what is the specific signal chain - post Helix devices - that you are using? My XLRs go to a Scarlett interface and studio monitors, my 1/4" to the Power Amp In of my Catalyst.

Check to see that you have the correct Catalyst ASIO driver installed. IF YES THEN: Step 1 - Go into device manager and check the Power Management settings for all of the USB Controllers. Turn OFF "Allow the computer to turn off this device to save power". Step 2 - Go to this article and follow ALL of the instructions. Don't be thinking "blah blah yadda yadda". Just do it. Windows 11 PC Optimization for Recording | Sweetwater If you're still having problems, then: Go to the Korg website and download the most recent version of the Korg Drive Tools: Downloads | KORG USB-MIDI Driver | KORG (USA) Run the Uninstall tool. It will show all of the MIDI Port assignments. Delete all duplicates and be sure that the drivers you need are loaded under port 10. If your computer has installed the 25H2 update from Microsoft, then you MAY need to roll back to 24H2. Yes, Microsoft screwed up again, and rolling back is their recommendation until they fix the problem. If after rolling back, the drivers are still loaded above port 10, uninstall the Root Hubs (Device Manager), disconnect all your USB devices and RESTART the computer. If you lose your mouse/keyboard and have to manually power cycle, use RESTART after Windows boots. Run the Korg Uninstall tool and reconnect your USB devices starting with the most critical. You'll see which port they're assigned to as you reconnect them. This process should fix the problem. If not...

Here ya go!

I'll have a look and see if that can be done with OBS. I'm assuming you use Windows?

Why OBS? What, EXACTLY, are you trying to accomplish?

When weirdness happens on digital gear, perform a factory reset. Don't forget to back up your presets first!

I recently sold my PC212+. My reasoning had nothing to do with how it sounds. It sounds GREAT. At high volumes. I live in an apartment. On an upper floor. The PC212+ is big, and weighs 48 lbs. NBD when I was 25, but that was a long time ago. I rarely play out anymore, just the occasional jam with friends. My upper floor apartment is 100 yards from the parking lot. My Catalyst100 sounds better at the volumes that I can play at, is totally sufficient volume-wise for jams and small gigs and is MUCH easier to carry. G.A.S. for other stuff. I found someone who had G.A.S. for a PC212+ and has a sound-proofed studio. Good gear should be played!