stevenew

Sorted! I don't ever remember the main Volume control working on the digital output as well as the analog but it had reset to controlling the multi out and as I always keep it on zero when not using the analog outs, there was no volume on the digital out! So I reset the volume control assign to only control the XLR & 1/4" and now I have digital out:-)

For ages now I have been using the SPDIF on my Helix Floor to connect to my audio interface, it has worked fine. Since updating my Helix Floor to 2.91 I have lost output on SPDIf and AES. I have tried numerous things checked the cables, the audio interface but nothing. I have also checked the AES out, nothing on that either. Also if I try to restore a backup it freezes at 36% the Helix display goes blank, I have to reboot the Helix, it rebuilds the presets and seems to work but still with no SPDIF or AES. It seems to me that the 2.90/91 update has not worked correctly. I have tried reinstalling 2.91 but it seems the same. Should I try a factory reset, but I might not be able to restore my backup? Edit: I just did a factory reset and my backup restored OK but still no SPDIF or AES output:-( Can I roll back to 2.82? Thanks for any help.

Latency using a Aggregate Audio Device of Helix Floor and MOTU 624 on my 4.1 (flashed to 5.1) Mac Pro 2 x 3.46 GHz 6-Core Intel Xeon, Mojave 10.14.2 As I use a lot of VI and sample libraries 44.1k & 48K are really the only sample rates that are practical. Do I just add the In & Out to get a total RTL? Cubase 10 & 9.5 Aggregate Audio Device of Helix Floor (Line 6 Driver) and MOTU 624 44.1K 64 = In 7.438 Out 9.433 = 16.871 44.1K 128 = In 8.889 Out 10.884 = 19.773 44.1K 256 = In 11.791 Out 13.787 = 25.578 48K 64 = In 7.333 Out 9.333 = 16.666 48K 128 = In 8.667 Out 10.667 = 19.334 48K 256 = In 11.333 Out 13.333 = 24.666 88.2K 64 = In 9.705 Out 8.707 = 18.412 88.2K 128 = In 10.431 Out 9.433 = 19.864 88.2K 256 = In 11.882 Out 10.884 = 22.766 96K 64 = In 9.667 Out 8.667 = 18.334 96K 128 = In 10.333 Out. 9.333 = 19.666 96K 256 = In 11.667 Out 10.667 = 22.334 Helix Only with Line 6 driver 44.1K 64 = In 7.438 Out 9.433 = 16.871 44.1K 128 = In 8.889 Out 10.884 = 19.773 44.1K 256 = In 11.791 Out 13.787 = 25.578 Aggregate Audio Device of Helix Floor (class compliant) and MOTU 624 48K 64 = In 4.583 Out 3.354 = 7.937 48K 128 = In 5.917 Out 4.688 = 10.605 48K 256 = In 8.583 Out 7.354 = 15.937 Helix Only with class compliant MacOS driver 48K 64 = In 4.583 Out 3.354 = 7.937 48K 128 = In 5.917 Out 4.688 = 10.605 48K 256 = In 8.583 Out 7.354 = 15.937 MOTU 624 Only 44.1K 64 = In 1.995 Out 1.995 = 3.99 44.1K 128 = In 3.447 Out 3.447 = 6.894 44.1K 256 = In 6.349 Out 6.349 = 12.698 48K 64 = In 1.833 Out 1.833 = 3.666 48K 128 = In 3.167 Out 3.167 = 6.334 48K 256 = In 5.833. Out 5.833 = 11.666 Using the same Cubase project, the aggregate device at 48K using the Helix on class compliant gives a much better latency but the CPU hit is much higher than using aggregate device at 48K using the Helix Line 6 driver with the same buffer size… Using the MOTU on its own with the same sample rates and buffer sizes not only is the latency way lower the CPU hit is considerably lower. I am seriously thinking of getting a converter so I can take the Helix SPDif coax out to the SPDif optical in on the MOTU and run at 44.1K 64 or 128 buffer. Super low latency and minimal CPU hit. Hope this is useful

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.

Ooops I just realised the Helix is not loaded on that screen shot, not sure what has happened, I will have to check.

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.

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.

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?

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?