Jump to content

Sentox

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sentox

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    2

Recent Profile Visitors

138 profile views
  1. This is something I discovered during my update as well. Copying from another thread:
  2. Definitely not unique to you. I had tried everything in this thread to no avail. As soon as I let the WinUSB drivers install, the updater could see my Helix Rack again. Without the "WinUSB" drivers, there's a random device that appears to the computer as "Msg Pipe" but doesn't have a driver. With these drivers installed, that same device shows up as "Helix Rack" and the updater can see the unit. Edit: Interestingly, looking at the drivers that are installed when "WinUSB" is selected, the INF includes entries for basically every piece of Helix hardware. The architectural changes in 2.80 are clear since the Helix Drivers actually installs two packages simultaneously now, 1.92 (which works for any Helix unit pre 2.8) and 1.93 (which obviously applies to 2.80). To Windows a 2.80 Helix is a completely different piece of hardware than any earlier version. It also enumerates an extra device as mentioned above that the WinUSB drivers apply to. Not sure if this is for sending keyboard inputs to the PC, or perhaps a new way for L6 software to talk to the Helix, but it's clearly necessary for the update to complete. The installer is a tiny bit misleading (imho) in that it can lead you to believe you don't need the WinUSB driver if you have a rack/floor/etc.
  3. Excuse my ignorance, but how are you guys running Spotify/YouTube/et al at the same time as a VST host with ASIO in Windows?
  4. Additionally, due to licensing restrictions the normally available releases of Audacity do not have ASIO support. You either have to dig around online or compile one yourself, so it's possible the OP does not have the option to use ASIO.
×
×
  • Create New...