jmcecil

Hopefully legit! Christmas in Sept/Octish

I just put my desire in with my sales rep. I'm sure they can't enter it until the official date.

I pre-ordered the XL within minutes of the announcement .. I'm sure I'll get it in like March cuz I don't know anyone :P

I've had the Helix Floor for nearly the entire 10 years (9+) .. Stadium XL already on pre-order! I still play on the Helix every day. It's one of the best price to usage technology items I've ever purchased. If we get 10 quality years out of Stadium, it's money well spent.

Couldn't use the site, but HX Edit downloaded the updates ok. Almost through with the firmware install. Can't wait to try the new IR's.

I don't know if you are in this situation or not. But I have been unable to load HX Edit or Native since version 1.7x. All I would get is a partially framed screen and then poof. I've had a ticket open for however long that is. A LONG TIME. We've gone back and forth with log files and system reports etc.. Basically on each release I would update my ticket with NOPE still doesn't work. After I did that for 1.9.1 I got a reply from support that said they may have figured it out, and possibly in the next release. And sure enough I can now use Native at version 1.9.2 I don't know if it was some C library compatibility issue or video driver etc.. But, it now works. You might want to give it a go. There isn't much of an install trick. You click the installer and tell it where to put the plugin. That should be a place your DAW scans for plugins. It shows up in your DAW as an insert effect.

I can finally use HX Edit and HX Native. It hasn't worked on my computer since 1.7x. Support told me they might have figured it out in this release and YES!!!!! I'm back in business on my main computer.

Updated to 2.81 and still can't use HX Edit. As soon as it detects the Floor unit it crashes. If I turn the unit off and just simply try and use a menu in HX Edit, it crashes.

Updated to 1.81 and still doesn't work. I'm on the latest NVIDIA drivers for my card. Also, if I install the old 1.7 version it works. There's something f'd up with the entire 1.8/2.8 software. I can't use HX Edit 2.8/2.81 either.

Tried in Reaper and Cubase 10. I get the frame, but no gui.

The install completely screwed up my Lynx Aurora configuration and hijacked my system and set the Helix to the default audio interface. I had to re-install my Lynx drivers to get it working normal again. HX Edit still doesn't work. I've passed back some basic info to support that they asked for. We'll see where it goes.

I have this same issue on Windows 10 and have opened a support ticket. I suggest you do so. It's possible one of the basic suggestions will help you, but it seems there are potentially bigger fish here.

I have no problem with suggestions. But still no go - different ports, different cable (although it's been running for a couple years now just fine and 2.71 worked fine) - I downloaded HX Edit 2.80 installer 3 separate times - I did an uninstall and deleted the actually driver from Device Manager the 2nd two times - The update to 2.8 using the updater worked fine - Updater is not running - I'm not disconnecting my peripherals ... if that's what's breaking things then Line 6 needs to fix their driver. My peripherals include quite a number of keyboards, sequencers, drum machines, FX etc... But again, it's never been a problem before. - Just another complaint .. having the damn driver take over the default audio interface every time I plug in the Helix is a Pain in the lollipop. My audio interfaces all had their names changed by the installation. I had to re-install my Lynx Aurora interface drivers to get it back after the Helix install. Again, I've installed Helix updates for ages without issues like this.

Running as admin didn't help. I've redownloaded 3 times.

Windows 10. My update went fine and the Helix Floor seems to be working fine. But if I try to launch HX Edit, HX Edit just crashes out as soon as it changes from No device found to Helix Floor .. then poof. I tried deleting the existing driver and re-installing. But the same thing happens.