godoq Posted June 4, 2017 Share Posted June 4, 2017 Please check attached Logic Pro X screen shots. It shows better roundtrip latency when Helix Mac Driver NOT installed (using Helix as USB class compliant mode) Yes I know that with Helix Mac driver, i can change sampling rate and control system volume in OS. But Is it ok to understand that Helix Mac Driver still not well implemented for recording performance as an audio interface? * Without Helix Mac Driver (Class Compliant) Device Name : HELIX Audio Roundtrip : 7.9ms Output : 3.4ms Buffer size : 64 * With Helix Mac Driver (1.0.4) Device Name : Line 6 Helix Roundtrip : 16.9ms Output : 9.4 ms Buffer size : 64 EDIT : data fixed :) Quote Link to comment Share on other sites More sharing options...
bradlake Posted June 4, 2017 Share Posted June 4, 2017 Think you got things backward..... Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted June 4, 2017 Share Posted June 4, 2017 Mac driver should not be necessary to use anyway. Quote Link to comment Share on other sites More sharing options...
steevo1977 Posted June 4, 2017 Share Posted June 4, 2017 Class compliant driver only allows 2in 2out does it not? (might be off on that of course) The Helix driver allows 8in 8out and midi functions. Quote Link to comment Share on other sites More sharing options...
godoq Posted June 6, 2017 Author Share Posted June 6, 2017 Class compliant driver only allows 2in 2out does it not? (might be off on that of course) The Helix driver allows 8in 8out and midi functions. Even without Helix Mac Driver 1.0.4 (in Class compliant mode), I can use all 8 I/O (incl. re-amp) as well as MIDI functions via command center. I think one of important feature of Helix Mac driver is solution for USB audio problems in some OS X versions. Quote Link to comment Share on other sites More sharing options...
tommasoferrarese Posted June 7, 2017 Share Posted June 7, 2017 You get all the functionality even without the driver. And, as you already discovered, better performance. The only (minor) drawback is that sample rate is stuck at 48kHz Quote Link to comment Share on other sites More sharing options...
mdmayfield Posted June 8, 2017 Share Posted June 8, 2017 Device-specific drivers are *not* always better than Class Compliant drivers. It's very possible that, for Mac system versions that *do* work properly with the Helix, the Class Compliant drivers really do have better performance and lower latency. The Helix Mac driver was only created because some specific versions of OSX / macOS didn't interact properly with the Helix. If those versions of OSX didn't have this incompatibility problem, Line 6 would never have even created a Mac driver, because the Helix is a Class Compliant device and is intended to work with the built-in CC drivers. I haven't kept up with the latest macOS versions, but I believe that these issues were resolved on the Apple side in recent macOS updates, so Helix should now work well in Class Compliant mode. Apple has a much larger driver development team than Line 6 and would have had the resources to put many more person-hours into testing and refining the CC drivers than Line 6 would have for the device-specific driver. If your version of macOS is not showing any major problems with them, I would suggest using the Class Compliant drivers. 2 Quote Link to comment Share on other sites More sharing options...
ibisibi Posted September 2, 2017 Share Posted September 2, 2017 As a newbie here running El Capitan 10.11.6, do I need the Mac Driver or is my OS playing nicely with my Helix in Class Compliant mode. In other words, at which OS update did Apple fix things? Anyone know for sure? Thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.