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

Potential bugs using as interface with Win 10


njglover
 Share

Recommended Posts

This morning I thought I'd try using the Helix as an interface and record a quick riff to compare it to my actual amp just to see how it stacks up, but when I first went to play back my old recording it sounded nuts, almost like it was bitcrushed. So I played with my buffer settings and tried to check various other settings, here are some things I discovered:

-No matter what I set the sample rate to on the Helix, Windows only gives me the option of 16/44.1 or 16/96. It also doesn't matter than in the driver panel I have it set to 24-bit, Windows still reads it as 16 (I assume the driver the Helix application installs is the correct ASIO driver, anyway).

  - On a related note, does the sample rate set on the Helix impact the sound coming out of the Helix itself? I'm fine leaving it at 44.1 as long as what's coming out of the actual unit isn't lower quality as a result.

-Studio One reads it, correctly, as 24-bit, as set in the driver settings, but does not allow me to change the sample rate.

-Finally, after much frustration, I found that changing the bit depth in the Helix control panel to something else and then back to 24 got everything working correctly.

 

So basically, nothing is communicating with each other. Helix says one thing, Windows says another, and the DAW says yet another thing. If it helps, I am running Windows 10 Pro 64-bit, it's an ASRock motherboard, and I was plugged into one of the front USB 3.0 ports. Using Studio One 3.

Link to comment
Share on other sites

Haven't tried your steps into a USB 3.0 port myself, but I run Helix into one of my USB 2.0 ports since it's 2.0 itself and have had no issues into Pro Tools, Sonar, FL Studio, or Amplitube 4. All audio applications report correct Helix options per the Helix ASIO panel in their respective settings screens.

 

I am on Windows 10 64 bit Pro on an Alienware X51R2.

 

The USB 2.0 vs 3.0 port was a lesson learned from my Eleven Rack.

  • Upvote 1
Link to comment
Share on other sites

Haven't tried your steps into a USB 3.0 port myself, but I run Helix into one of my USB 2.0 ports since it's 2.0 itself and have had no issues into Pro Tools, Sonar, FL Studio, or Amplitube 4. All audio applications report correct Helix options per the Helix ASIO panel in their respective settings screens.

 

I am on Windows 10 64 bit Pro on an Alienware X51R2.

 

The USB 2.0 vs 3.0 port was a lesson learned from my Eleven Rack.

Good to know, I plan upgrading to Win 10 after I get the Helix.  Waiting cause Eleven Rack doesn't support Win 10.  And I have an Eleven rack atm. 

 

Avid even advises not to plug the 11R into a USB 3.0 connection. They say strictly USB 2.0.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...