1. Plug in the AC cord and connect the included USB cable to a USB 2 or USB 3 port on the computer
2. Download and install the latest USB driver from Here
3. When the installer completes, reboot the computer when prompted

1. There is no driver for macOS, just connect the USB cable and you are ready to go.

1. Install appropriate driver for the operating system
2. Connect a word clock cable from the worcdclock out of unit #1 to the wordclock in of unit #2. Alternatively, if you use a master clock, you can connect wordclock cables to the inputs of both units
3. With Thunderbolt, use NControl or the front panel controls to set Sync Source for unit #2 to "Word clock" (or both units to Word clock if using a master clock). For USB, disconnect the USB cable and set the clocks as described above with the front panel controls. Reconnect USB when finished.
4. Open Audio Midi setup from Applications > Utilities
5. Click the "+" in the bottom left corner and select "Create aggregate device"
6. Select Aurora #1 first, and then Aurora #2. De-Select "drift" from Aurora #2
7. Rename the aggregate device if you wish
8. In your DAW, select the aggregate device as your audio device

Check and make sure you have the latest version of Big Sur.

Click on the Apple icon, then select System Preferences

Select Software Update

Allow the system to update to the latest version

After the operating system is completely up-to-date, please follow these step by step instructions to check the installation of the driver on macOS 11 Big Sur.

By default, NControl will try and communicate with the Aurora(n) over USB or Thunderbolt. To get NControl to find the Aurora(n) on a Dante network, you must first have Dante Controller installed on the same computer that you want to run NControl. Dante Controller is software from Audinate and is available from here: https://www.audinate.com/products/software/dante-controller

Once you have Dante Controller installed, you should be able to see the LT-DANTE card from within Dante Controller:

Next, enable Dante as the only connection type from within NControl by selecting Menu > Connection > Dante (make sure you uncheck USB and Thunderbolt):

You may need to relaunch NControl after making this selection.

One Windows, the Firewall Manager may popup a notification when you launch NControl:

Make sure you check "Allow access". Again, you will need to relaunch NControl to allow this setting to become active.

Now you should see that NControl is connected to your Aurora(n) through Dante as indicated by the "Dante: Connected" label on the connection panel.

1. With 24 or 32 channels Aurora(n)'s, the I/O will appear in the correct order in the I/O setup
2. If an LM-DIG is installed, the Aurora(n) will appear as follows:
   • With 8 channels of analog I/O, it will appear as a single HD I/O with 8 analog and 8 digital. Digital I/O channels 9-16 will not be available.
   • With 16 channels of analog I/O, it will appear as two HD I/Os, each of which have 8 analog and 8 digital channels. HD I/O #1 will carry channels 1-8 of analog an digital, HD I/O #2 will carry channels 9-16 of analog and digital.
   • With 24 channels of analog I/O, it will appear as two HD I/Os, with 16 analog channels each. Channels 9-16 of the second instance of the HD I/O will carry digital channels 1-8. Digital channels 9-16 will not be available
3. Performance at 192khz has been improved
4. You will no longer change sync source in the ProTools hardware setup. Desired Sync Source will be established from the Clock Settings page on the Aurora(n). If using the Aurora(n) on internal clock, then the default settings in ProTools will be fine. If using the Aurora(n) on an external clock source (wordclock or digital in), we suggest setting the clock source for the unit in the ProTools hardware setup page to "wordclock" at the project sample rate.
5. If using an external clock source, and you wish to create or open a project at a different sample rate, we recommend the following steps
   • Close the current session
   • Open the ProTools Hardware Setup
   • Change the sample rate on your external clock source to the rate of the project you intend to open or create
   • Set the sample rate on the hardware setup page for the Aurora hardware to match the external sample rate
   • Close the hardware setup page
   • Open or create a new project at the new sample rate
6. Firmware 15 should remedy AAE errors on launch, as well as noise blasts when ProTools is closed

The Aurora(n)-TB3 and Hilo-TB3 both use Thunderbolt 3 as the interface to your computer.  Both Thunderbolt 3 and 4 use a USB-C connector on each end of the cable, however not every USB-C cable is capable of supporting Thunderbolt.

We have tested Thunderbolt cables from Belkin, Cable Matters and StarTech and all of them work fine with both the Aurora(n)-TB3 and Hilo-TB3.

Passive Cables

Passive cables have no internal repeater, so they can be 0.8 meters maximum.  As such they are much less expensive than active cables.

Belkin: 0.5 meter Thunderbolt 3 cable

Belkin: 0.8 meter Thunderbolt 3 cable

Cable Matters: 0.8 meter Thunderbolt 3 cable

Cable Matters: 0.8 meter Thunderbolt 4 cable

Active Cables

Belkin: 2 meter Thunderbolt 3 cable

Cable Matters: 2 meter Thunderbolt 3 cable

Cable Matters: 2 meter Thunderbolt 4 cable

StarTech: 2 meter Thunderbolt 3 cable

Please note that there is really no difference between a Thunderbolt 3 and Thunderbolt 4 cable, as long as they both support 40Gbps.

Optical Cables

If a cable longer than 2 meters is required, optical is the only option.

Cable Matters: 10 meter Thunderbolt 3 optical cable

Corning: 5 meter Thunderbolt 3 optical cable

Corning: 10 meter Thunderbolt 3 optical cable

Corning: 15 meter Thunderbolt 3 optical cable

Corning: 25 meter Thunderbolt 3 optical cable

Corning: 50 meter Thunderbolt 3 optical cable

Please be aware that optical cables are more fragile than copper wires, so they should not be bent or curved around tight corners, and should generally be treated much more carefully. Optical cables cannot provide power delivery to downstream devices.

Thunderbolt 1 or 2 connections

If your computer only supports Thunderbolt 1 or Thunderbolt 2, you can still use the Aurora(n)-TB3 or Hilo-TB3, you just need to purchase a Thunderbolt 2 to Thunderbolt 3 adapter cable.  We have tested the Apple adapter cable and it is the only one we can recommend:

Apple Thunderbolt 2 to Thunderbolt 3 adapter

Connect this adapter cable directly to the Aurora(n)-TB3 or Hilo-TB3 and use a Thunderbolt 2 cable to connect to the computer.

1. Insure that the Cable connected to the appropriate analog output port is the Lynx CBL-AOUT85 or adheres to the Tascam DA-88 Analog I/O pin configuration.
2. Make sure that the cable connected to your monitoring equipment is plugged into ANALOG OUT 1-8
3. Make sure that in the Aurora(n) display Function > Routing has the correct source set for TO ANALOG OUT.
4. Verify that your monitoring equipment is turned on and the levels are turned up to a safe listening level.

• First off, since you will be disabling a security feature of Windows, after completing these steps take care to only install drivers that you trust to avoid potential corruption of your OS.
• We will be using a "test signing mode" in Windows to get past the driver signing enforcement. Start by right-clicking the Start button, and selecting "Command Prompt (Admin)".
• Paste the following command into the Command Prompt window and press Enter:
  

  bcdedit /set testsigning on

• Restart your computer to enter test mode. After re-boot you will see a "Test Mode" watermark in the bottom-right corner of the screen. In this state you can successfully install the Lynx Drivers.
• To leave test mode (which will disable the ability to use the Lynx driver), open a Command Prompt (Admin) window again and run the following command:
  

  bcdedit /set testsigning off 

1. Buffer size is too small for the sample rate and number of channels selected.
• To resolve this, increase the buffer size.


2. Power management is causing the processor to go to sleep, which takes quite a bit of time to wake up, causing the interrupt to be responded to too slowly.
   • To resolve this, in the BIOS of the computer:
   • Turn off Intel SpeedStep (sometimes labeled EIST).
   • Turn off C-States: C1E; C3 and C6.
   • Turn off Intel Trusted Execution Technology.
   
   
   • In Control Panel, set your Windows Power Options to High Performance.

1. Is the Aurora(n) set to the same Sync Source and Sample Rate as it was the last time ProTools was open?
2. If the Aurora(n) is set to 192KHz, try changing it to a lower sample rate before launching ProTools.
3. Sometimes Audio Midi Setup can "hijack" the Avid card, and prevent proper loading of ProTools. Try removing these two files, empty trash, and reboot:
   

   Library/LaunchAgents/AvidAudioServer.plist2

   and
   

   Library/LaunchDaemons/com.avid.AvidAudioServiceHelper.plist

1. Disconnect power from Aurora(n).
   
2. Remove six screws from top cover.
   
3. Remove top cover.
   
4. Locate SW1 nearest the headphones board at the front left of the PROC board. The factory default posting has PROM 2: ON and PROM 1: OFF as shown below:
   
5. Change SW1 position 4 to OFF and SW1 position 3 to ON. This will enable the Aurora(n) to start on PROM 1 instead of PROM 2.
6. Temporarily replace the top cover so there is no chance of coming in contact with any powered electronics.
7. Reconnect the AC power to the Aurora(n).
8. Power up the Aurora(n) and program PROM 2 firmware using the "Firmware Update" option on the Function Menu following the instructions in Section 8 of the Aurora(n) User Manual.
9. Once the firmware on PROM 2 is successfully programed: disconnect power from Aurora(n); remove the top cover; change SW1 back to PROM 2: ON and PROM 1: OFF to have the Aurora(n) start on PROM 2.
10. Install top cover by attaching with 6 screws removed in step 2, above.
11. Connect to AC power.
12. Verify the Aurora(n) starts on PROM 2.

1. Disconnect power from Aurora(n).
   
2. Remove six screws from top cover.
   
3. Remove top cover.
   
4. Locate SW1 nearest on the LT-TB board in shown highlighted in the image above. The factory default position has PROM 2: ON and PROM 1: OFF as shown below:
   
5. Change SW1 position 4 to OFF and SW1 position 3 to ON. This will enable the LT-TB to start on PROM 1 instead of PROM 2.
6. Temporarily replace the top cover so there is no chance of coming in contact with any powered electronics.
7. Reconnect the AC power to the Aurora(n).
8. Power up the Aurora(n) and program the LT-TB PROM 2 firmware using the "LynxFirmware" update application.
9. Once the firmware on PROM 2 is successfully programed: disconnect power from Aurora(n); remove the top cover; change SW1 back to PROM 2: ON and PROM 1: OFF to have the LT-TB start on PROM 2.
10. Install top cover by attaching with 6 screws removed in step 2, above.
11. Connect to AC power.
12. Verify the LT-TB starts on PROM 2.

Check and make sure you have the latest version of Big Sur.

Click on the Apple icon, then select System Preferences

Select Software Update

Allow the system to update to the latest version

After the operating system is completely up-to-date, please follow these step by step instructions to check the installation of the driver on macOS 11 Big Sur.

First, check and see that the Thunderbolt device is being seen by the operating system.

Launch System Information (Applications > Utilities > System Information)

Click on the Thunderbolt/USB4 under Hardware:

You should see LT-TB or LT-TB3 listed under Thunderbolt/USB4. If not, check your cabling and that the device is powered up. If the cabling is correct and the device is powered up, on the LT-TB check that LED D30 is flashing; on the LT-TB3 check that LED D1 on the wrap-around board is flashing.

Next, check under PCI to see if the LT-TB or LT-TB3 shows up as a PCI device:

On this sample screen, you can see the LT-TB is showing up as pci1621,14 and the driver is not installed. It is assumed that you have already tried to install the driver, so you need to check the Kext_policy database to see if the driver is being blocked from loading.

Launch Terminal (Applications > Utilities > Terminal)

Here is the line you can cut-and-paste into Terminal:

sudo "/usr/bin/sqlite3" "/var/db/SystemPolicyConfiguration/KextPolicy" "SELECT * FROM kext_policy;"


As a short-cut, please see the attached "kextpolicy.zip" file attached to the bottom of this page. Simply open the zip file which will extract the script file "kextpolicy", then double-click on the kextpolicy script.

And here is an example of a sample of what you might see:

Each of the five fields are:

The flags field can be:

If your Macintosh is:

* Not loading the driver

* Flags ? 0

* Not showing the Allow button in Security & Privacy

You will need to delete the driver's entry from the database and reinstall the driver.

Normally, the kext_policy database is locked in read-only mode. To modify the database the Mac will need to be rebooted into recovery mode.

Booting into Recovery Mode:

Intel: Restart the Macintosh. Hold down the "COMMAND ?" and the "R" key until the boot chimes play.

Apple Silicon M1: With the Macintosh off, hold down the power key and continuing to hold down the power key until the recovery environment starts.

Once recovery Mode has loaded, click Utilities, and select Terminal.

In Terminal, type (where Macintosh HD is the name of your boot volume):

"/Volumes/Macintosh HD/usr/bin/sqlite3" "/Volumes/Macintosh HD/var/db/SystemPolicyConfiguration/KextPolicy"

Once sqlite is running type the items in bold (being careful to type EXACTLY what is shown):

sqlite> DELETE from kext_policy where Bundle_ID = 'com.lynxstudio.driver';

sqlite> .quit

Then from the terminal prompt, type:

% exit

Restart the Macintosh.

Run the "Uninstall Lynx Driver" application to remove the current installation of the driver.

Restart the Macintosh.

Install the driver.

Make sure to click "Open Security Preferences" after the driver has installed.

Next click "Allow"

Restart the Macintosh once again.

Double-check that the driver is now showing as installed in System Information:

• Remove the driver from Start > All Programs > Lynx Studio Technology > Uninstall Lynx Driver (or C > Program Files > Lynx Studio Technology V2Uninstall or V3Uninstall)
• Reboot when prompted
• Run the driver installer, but do not continue once the DIFXAPI_ ERROR message comes up
• Go to device manager
• Right Click the Lynx Device under Sound, Video and Game Controllers and choose "Update Driver"
• Point the installer to C:Program FilesLynx Studio TechnologyV2Driver or V3Driver for the driver files