Please ensure Javascript is enabled for purposes of website accessibility Jump to content

rd2rk

Members
  • Posts

    7,947
  • Joined

  • Last visited

  • Days Won

    426

rd2rk last won the day on February 7

rd2rk had the most liked content!

7 Followers

Profile Information

  • Location
    Colorado, USA
  • Registered Products
    4

Recent Profile Visitors

12,436 profile views

rd2rk's Achievements

Grand Master

Grand Master (14/14)

  • Dedicated Rare
  • One Year In
  • One Month Later
  • Week One Done
  • Reacting Well Rare

Recent Badges

3.5k

Reputation

10

Community Answers

  1. Contact support. If it's being caused by the "known issue" they'll take care of it regardless of warranty status.
  2. 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.
  3. 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.
  4. 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,
  5. 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.
  6. 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.
  7. 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?
  8. 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.
  9. IF NO THEN download and install the Catalyst ASIO driver. Line6 Catalyst Driver 2_5 v2.0.0.0
  10. Do you perchance have the XLR and 1/4" outs set differently in GLOBAL SETTINGS>INS/OUTS?
  11. 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.
  12. 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?
  13. 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.
  14. 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...
×
×
  • Create New...