ASIO Buffer Size	Payload Size 44.1kHz & 48kHz	Payload Size 88.2kHz & 96kHz	Payload Size 176.4kHz & 192kHz
32 & 64	2	4	8
128 & 256	4	8	16
512 & 1024	8	16	32
2048 & 4096	16	32	32
8192	32	32	32

• 5.1 support for WaveRT (6-channel interleaved)
• Smaller transfer sizes to reduce latency to under 1ms round-trip (96kHz, 32 sample buffer)

• AES16e: 14.0
• LT-TB: 6.0
• E44/E22: 2.0

• Tabs for each adapter installed instead of a separate floating window.
• Adapter; Record and Play pane may be displayed
• Same look and feel for both Windows and OS X.
• Saves scenes in a standard XML file which are no longer version or OS specific.
• For the AES16e+Aurora combo, new Aurora menu items appear within the Settings menu.This replaces Aurora Remote Control which is no longer needed for the AES16e+Aurora combo.
• New method for controlling the monitor sources.
• Inputs and Outputs change name based on what is connected.For the AES16e by itself, I/O will be labeled as Digital In and Digital Out.For the AES16e+Aurora combo, I/O will be labeled as Analog In and Analog Out.
• LS-ADAT fully supported with "ADAT Clock Source" selection in Settings Menu and LStream clock lockout for when the ADAT Clock Source is set to Slave.
• For the Aurora-TB and AES16e+Aurora combo, the Adapter Settings dialog now flashes the front panel of the Aurora when each device is selected.This allows easy identification when selecting the order of the adapters.

1. To avoid physical hardware dropouts.
2. To avoid the extra buffer(s) of latency introduced if hardware dropouts occurred.
3. 3) To give the CPU the most time possible to render the playback audio into the buffers (which minimizes audio glitches) before that audio is actually played.

1. The AES16e requires Build 6 Firmware to function properly with a buffer size of 32.
2. In mixed card systems (some AES16e and AES16 cards together in the same computer, for instance) the latency reported will not match the "other" audio card. Specifically if you have an AES16e as card #1 and an AES16 as card #2 the latency reported will be for the AES16e, so manual latency compensation will be required for the AES16 channels. This is no different than using a LynxTWO and AES16 in the same system since those cards have different latency.
3. Cakewalk SONAR 7 issues an ASIOStop / ASIOStart command before each playback.For the AES16e this causes the very first buffer to be played out-of-sequence.The next release version of SONAR will no longer issue ASIOStop / ASIOStart which will solve the issue.

1. It allows manual changing of the Current Clock Source by selecting a new Preferred Clock Source even if devices are active on the card.If you do manually change the Preferred Clock Source while this switch is ON and devices are active, an audible glitch will occur.
2. If the Preferred Clock Source has become invalid and the driver has switched the Current Clock Source back to Internal, it allows the driver to change the Current Clock Source back to the Preferred Clock Source immediately when the Preferred Clock Source becomes valid.Normally when this switch is OFF the driver will not change the Current Clock Source back to the Preferred Clock Source until all devices become inactive.

• MIDI control of output volumes. Each of the sixteen outputs are assigned in order to a single MIDI channel. The Volume controller (7) now effects the main output for that channel. This allows automated control of the main output volumes.
• MIDI control to start the LTC Transmitter. Once the MIDI Output driver sees a complete MTC message, the LTC Transmitter will have its position set to match, and begin generating timecode.
• LTC Receive to MIDI Timecode conversion.

• 5.1 support for WaveRT (6-channel interleaved)
• Smaller transfer sizes to reduce latency to under 1ms round-trip (96kHz, 32 sample buffer)
• DMAV2PLUS is supported with the following firmware:
  AES16e: 14.0
  LT-TB: 6.0
  E44/E22: 2.0

• Tabs for each adapter installed instead of a separate floating window.
• Adapter; Record and Play pane may be displayed
• Same look and feel for both Windows and OS X.
• Saves scenes in a standard XML file which are no longer version or OS specific.
• For the AES16e+Aurora combo, new Aurora menu items appear within the Settings menu. This replaces Aurora Remote Control which is no longer needed for the AES16e+Aurora combo.
• New method for controlling the monitor sources.
• Inputs and Outputs change name based on what is connected. For the AES16e by itself, I/O will be labeled as Digital In and Digital Out. For the AES16e+Aurora combo, I/O will be labeled as Analog In and Analog Out.
• LS-ADAT fully supported with "ADAT Clock Source" selection in Settings Menu and LStream clock lockout for when the ADAT Clock Source is set to Slave.
• For the Aurora-TB and AES16e+Aurora combo, the Adapter Settings dialog now flashes the front panel of the Aurora when each device is selected. This allows easy identification when selecting the order of the adapters.

1. To avoid physical hardware dropouts.
3. To avoid the extra buffer(s) of latency introduced if hardware dropouts occurred.
5. To give the CPU the most time possible to renderthe playback audio into the buffers (which minimizes audio glitches) before that audio is actually played.

1. The AES16e requires Build 6 Firmware to function properly with a buffer size of 32.
3. In mixed card systems (some AES16e and AES16 cards together in the same computer, for instance) the latency reported will not match the "other" audio card. Specifically if you have an AES16e as card #1 and an AES16 as card #2 the latency reported will be for the AES16e, so manual latency compensation will be required for the AES16 channels. This is no different than using a LynxTWO and AES16 in the same system since those cards have different latency.
5. Cakewalk SONAR 7 issues an ASIOStop / ASIOStart command before each playback. For the AES16e this causes the very first buffer to be played out-of-sequence. The next release version of SONAR will no longer issue ASIOStop / ASIOStart which will solve the issue.

1. It allows manual changing of the Current Clock Source by selecting a new Preferred Clock Source even if devices are active on the card. If you do manually change the Preferred Clock Source while this switch is ON and devices are active, an audible glitch will occur.
2. If the Preferred Clock Source has become invalid and the driver has switched the Current Clock Source back to Internal, it allows the driver to change the Current Clock Source back to the Preferred Clock Source immediately when the Preferred Clock Source becomes valid. Normally when thisswitch is OFF the driver will not change the Current Clock Source back to the Preferred Clock Source until all devices become inactive.

• MIDI control of output volumes. Each of the sixteen outputs are assigned in order to a single MIDI channel. The Volume controller (7) now effects the main output for that channel. This allows automated control of the main output volumes.
• MIDI control to start the LTC Transmitter. Once the MIDI Output driver sees a complete MTC message, the LTC Transmitter will have its position set to match, and begin generating timecode.
  
• LTC Receive to MIDI Timecode conversion.