stevenew Posted December 21, 2018 Share Posted December 21, 2018 I am trying to use my Helix as a aggregate audio device with a MOTU 624 on macOS Mojave 10.14.2, even with the latest Helix Mac driver I can only get it to work on 48K I cannot get it to work on 44.1k. I am using Cubase 9.5.41 and Digital Perfomer 9.52. Even if I try using the Helix on its own as my Mac audio device, when I go into Audio Midi setup the only Sample rate available is 48K. Has anyone succeeded in using the Helix over USB on macOS at 44.1k? Quote Link to comment Share on other sites More sharing options...
zolko60 Posted December 21, 2018 Share Posted December 21, 2018 Helix native frequency is 48kHz. You can however download driver with higer latency to use other sampling rates. BTW It is described in the Owner's Manual page 58 (HxLT) Quote Link to comment Share on other sites More sharing options...
stevenew Posted December 22, 2018 Author Share Posted December 22, 2018 I have downloaded and installed the latest 1.0.5 macOS Helix driver but can only get it to work on 48K, if I set the aggregate Helix/MOTU sample rate to 44.1K in macOS Audio Midi setup and then launch Cubase, cubase gives an error message that the driver for Helix/MOTU is missing. If I set the sample rate to 48K in macOS Audio Midi setup Cubase launches OK and all works fine, if I try to change the sample rate to 44.1K in the Cubase project I get no sound. If I choose the aggregate device of the Helix and MOTU 624 and set the sample rate 48K everything works as it should, if I then try to change the sample rate within the Cubase project to 44.1K all the Helix in/out disappear and only the MOTU ones remain. If I just choose the Helix audio device I only have the option in macOS Audio/Midi setup for 48K. I get similar problems in Digital Performer. Again it will only work at 48K. I wonder if despite installing the Helix 1.0.5 driver twice, for some reason it is not using the driver but still running as class compliant? Quote Link to comment Share on other sites More sharing options...
stevenew Posted December 22, 2018 Author Share Posted December 22, 2018 Problem solved: Security settings in Mojave were stopping the Helix driver loading: System Preferences/Security & Privacy/General, once I authorised this to load and rebooted the different Sample Rates were now available in macOS Audio/Midi Setup, 44.1K selected, launch Cubase and everything seems to be working as I expected. I can now load the Helix/MOTU aggregate device as 44.1K, 48K or 88.2K or 96K. 1 Quote Link to comment Share on other sites More sharing options...
zolko60 Posted December 22, 2018 Share Posted December 22, 2018 So aggregating on OSX is only possible for the same sampling rates. Am I right? Can you share the results of reported latencies (RTL) and what buffers are usable for your machine in the linked thread? Quote Link to comment Share on other sites More sharing options...
stevenew Posted December 22, 2018 Author Share Posted December 22, 2018 Yes aggregating has to be at the same sampling rate, there is not really the option to do otherwise. I also clock from the MOTU and switch off Drift correction, this seems to result in less pops clicks. I can certainly post the input and output latencies I get with Cubase in your linked thread. On my ageing 4.1 (flashed to5.1) Mac Pro only 44.1K and 48K are of any real practical use. If I was just recording audio then 96K would work but as I work with a lot of VI and sample libraries the CPU hit is too much. Quote Link to comment Share on other sites More sharing options...
stevenew Posted December 22, 2018 Author Share Posted December 22, 2018 Ooops I just realised the Helix is not loaded on that screen shot, not sure what has happened, I will have to check. Quote Link to comment Share on other sites More sharing options...
stevenew Posted December 22, 2018 Author Share Posted December 22, 2018 Sorry wrong that was the screenshot! Here is the correct one showing the aggregate device of the MOTU and Helix using the Line 6 Drivers. The other thing to note that the latency for any sample rate is much higher using the Helix and MOTU as opposed to the MOTU on its own. 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.