Sentox

On 8/15/2019 at 6:06 AM, DunedinDragon said:

Well, one thing I did discover (which is not a bug by the way) is that the Helix PC device driver for 2.8 and 2.81 which is downloaded/installed as part of the HX Edit 2.80 install, is functionally different from the Helix device driver in 2.7 and 2.71.  This may have been pointed out in one of the documents and I just missed it.  But what it means is that a Helix loaded with 2.8 or 2.81 will not connect to the PC for sound or for HX Edit unless you've done the install of HX Edit 2.8 and it's driver.  In fact according to the Control Panel, the older Helix device driver will not start if you plug in a Helix loaded with 2.8 or 2.81.  I discovered this when I took my Helix Floor unit from my studio setup which I had upgraded to 2.81 and plugged it into my laptop which is normally connected to my Helix floor unit I use for live performances and is still on 2.70.

This may account for a number of problems people are having with HX Edit working with 2.81.  In spite of what they say, they may not have run the HX Edit install for 2.8 so they don't have the correct driver.

This is something I discovered during my update as well. Copying from another thread:

Quote

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.

On 7/29/2019 at 1:32 PM, TheHYPO said:

My solution may be unique to me, or it may have been a coincidence

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.

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?

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.