Download the latest drivers, firmware, and software for your USB 2.0 4-Port Hub.This is HP’s official website that will help automatically detect and download the correct drivers free of cost for your HP Computing and Printing products for Windows and Mac operating system. SIO (Smart-IO) USB to UART/Serial/Printer PL2303 Windows Driver Download. MultiMix USB 2.0 - Firmware Update for Windows v1.10 Download; MultiMix USB 2.0 - Macintosh Driver 3.3.3 OS X EL CAPITAN ONLY This update adds compatibility with OS X 10.11 and should not be used for earlier versions. Download; MultiMix USB 2.0 Macintosh Driver v3.2.0 This update adds compatibility with Mac OS X 10.10 Yosemite and 10.9.
USB to Gigabit Ethernet adapters are especially useful for adding faster wired network capability to otherwise WiFi-only machines like the Macbook Air.
Jul 24, 2015 A MacBook to run Disk Utility in OS X. How to create USB installer for Mac OS X Step 1: Download installer of OS X Yosemite, Mavericks, Mountain Lion, and Lion We are still able to download Yosemite from Apple store: Go to Mac Apple Store use your Apple ID and login Find and download OS X.
You can buy Apple’s branded 10/100 USB adapter — but price-wise, it will cost more than some gigabit adapters (like our Plugable USB Gigabit adapter). A gigabit adapter is also a nice upgrade for machines that only have a 10/100 ethernet port, but are connecting to a gigabit-capable network.
Because there’s often confusion about the rated speeds and actual throughput, especially when running 1000Mbps Ethernet over USB 2.0’s 480Mbps bus, we did some testing to establish a base line.
Usb 2.0 Ethernet Adapter Driver Mac Os X
We installed the latest ASIX AX88178 Mac drivers for the Plugable Gigabit Adapter (currently v6.3.0). We used the open source network testing tool iperf running on a Mac Mini Server running 10.7.3 and a MacBook running 10.6.8. If you’d like to duplicate our tests, here’s a nice pre-compiled GUI version available here: JPerf-2.0.2.dmg. In order to isolate the adapters as completely as possible, we connected directly between two ethernet ports, set the address manually and ran iperf as both server and client in each direction. Remember that in order to get gigabit speeds, your entire network (including any routers in-between) need to be gigabit capable.
|USB-to-Gigabit Ethernet (Plugable USB2-E1000)|
|USB 10/100 Ethernet|
These are low-level performance numbers (raw TCP/IP throughput). Real world throughput like copying a file over the network will be substantially lower due to transport overhead and any bottlenecks on the network or on either side of the transfer.
Using a tool like iperf and isolating the ethernet adapters to a direct connection establishes a base line for data speeds. To further identify potential networking bottlenecks, introduce one network component at a time and rerun your tests to see how the throughput is effected by the increasing complexity.
For detailed instructions on installing Mac drivers for the Plugable USB2-E1000, see Howto: Installing ASIX’s USB Gigabit Ethernet Driver on Mac OS X Lion 10.7.
We hope these numbers are useful to set performance expectations. Have any questions? We’d be happy to help. Reply here or email [email protected] anytime. Thanks![usb2-e1000
To successfully design a class compliant USB audio device that works seamlessly with the Mac, it is important to understand the features of the Mac's USB audio class driver, AppleUSBAudio. This document explains the driver's architecture, features, and algorithms available in Mac OS X v10.6 and later. It also includes a section discussing recently enhanced support for devices that comply with the USB Device Class Definition for Audio Devices 2.0 specification. The insights and design tips presented here are intended to assist device developers in creating high quality plug-and-play USB audio devices.
This document assumes the reader is familiar with the Core Audio framework, Audio HAL, I/O Kit basics and USB fundamentals. Please review these documents for more information:
Note: There is often confusion when referencing the various USB related specifications. See Table 1 for a summary of the terms used in this article to reference USB specifications.
Terms used in this document
USB Audio 1.0 USB Audio 2.0
Revisions of the USB Device Class Definition for Audio Devices
USB Audio Data Formats 1.0USB Audio Data Formats 2.0
Revisions of the USB Device Class Definition for Audio Data Formats
USB 1.0USB 1.1USB 2.0
Revisions of the Universal Serial Bus Specification
The reader is strongly encouraged to review the documents in Table 1.
Class Driver Overview
AppleUSBAudio is an I/O Kit based kernel driver that is designed to support both USB Audio 1.0 and USB Audio 2.0 class compliant devices. Figure 1 shows where AppleUSBAudio fits in the Mac OS X audio stack architecture. In addition to transporting audio data between the hardware and the host’s sample buffer, it also communicates format and control changes between the host and the device (like volume, mute, format, input/clock source, etc.) AppleUSBAudio presents these hardware resources to applications through the HAL (audio hardware abstraction layer.)
The AppleUSBAudio driver communicates to devices via the USB transport, using the IOUSBFamily APIs. AppleUSBAudio builds upon the IOAudioFamily layer which provides general audio driver functions like maintaining the sample and mix buffers, facilitating communication over the kernel and user space boundary through user clients, and more. Please see the Audio Device Driver Programming Guide for more details.
AppleUSBAudio is a mature driver that supports many USB Audio 1.0 and 2.0 features. Table 2 highlights some of the supported features that are discussed in this article.
USB Audio 1.0devices
USB Audio 2.0devices
Input stream sample synchronous to output stream
Streams must meet requirements to occupy the same engine
Unified Engine Model
Endpoint Synchronization Types
Output adaptive endpoints
Usually paired with an asynchronous input endpoint. Input adaptive endpoints are not supported.
Endpoint Synchronization Types
Endpoint Synchronization Types
Device informs host of volume, mute, input selector, clock validity
Predefined and custom channel names
Clock entity descriptors
Clock Source, Clock Selector, Clock Multiplier
High speed isochronous audio data transfers
Can support high channel count/sample rates. Example: 10 channels of input and 10 channels of output, 32-bit @ 192 kHz
High Speed Streaming
Usb 2.0 Driver Mac Download
Unified Engine Model
AppleUSBAudio represents the streams of a USB audio device to the application layer using IOAudioFamily's IOAudioStream entities. One or more streams are associated with each engine.
In Mac OS v10.5.6 and earlier, AppleUSBAudio restricted each engine to one stream only. Then in v10.5.7, AppleUSBAudio’s engine model was redesigned to combine multiple streams per engine when possible. In cases where input and output streams can reside on the same engine, this architecture achieves sample synchronization and consistent latencies between streams.
In order to combine multiple streams on one engine, the following criteria must be met by the stream interfaces:
All sample rate sets must match.
The same synchronization type is used for all interface alternate settings.
The streams reside in the same clock domain.
Please note the following behaviors of streams that occupy the same engine:
These streams operate in the same time domain and sample rate setting (but not necessarily the same format.)
These streams cannot be activated independently. They will always start and stop together.
Important: If a device is designed to combine multiple streams on a single engine, it must support starting multiple streams at the same time. If the device needs more time to do this, consider increasing the lock delay (see Section 22.214.171.124 of the USB Audio 1.0 Spec and Section 126.96.36.199 of the USB Audio 2.0 Spec.)
The primary and most important function of the AppleUSBAudio driver is to support reliable, artifact-free audio streaming. Developers can aid the driver in achieving this goal by selecting the appropriate endpoint descriptor values for synchronization type and maximum packet size.
Endpoint Synchronization Types
To maintain glitch-free audio, AppleUSBAudio must regularly present timestamps to Core Audio that accurately represent the audio data rate of the engine (see “The Audio I/O Model Up Close” in the Audio Device Driver Programming Guide for more details.) When the device publishes the correct endpoint synchronization types in its configuration descriptors, AppleUSBAudio can pick the appropriate stream from which to generate the most accurate timestamps for the engine.
The driver supports all three synchronization types defined by the USB 2.0 Specification (see Section 188.8.131.52 Synchronization Type and Table 5-12):
Usb 2.0 Driver Mac
Synchronous: synced to host via SOF
Asynchronous: not synced to host, data rate is locked to a free-running internal clock on the device or an external source like S/PDIF
Adaptive: synced to host via data rate
Table 3 below lists synchronization type combinations that work well with Mac OS X.
Device derives its clock from
Timestamps generated from
Output data rate
Free-running internal or external source
Device or external
If a device supports multiple clock domains, USB Audio 2.0 clock entity descriptors should be used to clearly communicate its clock architecture to AppleUSBAudio. Please see the Clock Entities section later in this article for information about these descriptors.
Note: Devices may use USB Audio 2.0 descriptors for full speed devices, not just high speed devices. This can be useful to more accurately describe full speed devices with complicated clock architectures such as multiple clock domains.
Feedback for Asynchronous Output Streams
To stream audio via an asynchronous sink endpoint, a device must continuously update the host of its desired data rate relative to the SOF frequency (see Section 5.10.4 of the USB 1.0 Spec and Section 5.12.4 of the USB 2.0 Spec.) AppleUSBAudio supports two feedback mechanisms:
Explicit feedback endpoint: The device provides an associated isochronous feedback endpoint which sends packets containing the number of samples per USB (micro)frame (see Section 184.108.40.206 of the USB Audio 1.0 Spec and Section 220.127.116.11 of the USB Audio 2.0 Spec.)
Implicit feedback: The driver uses the number of sample frames in the main input stream's packets to construct the packets for all output streams within the engine. No feedback endpoint is required (see Section 18.104.22.168 of the USB 2.0 Spec.)
In order to use implicit feedback, the device must satisfy the following requirements:
Asynchronous input and output streams reside on one engine (i.e. needs to meet criteria for the Unified Engine Model.)
The polling intervals (bInterval) for the stream endpoints must match.
Either the input stream endpoint “Usage type” is set to “Implicit feedback data endpoint” (USB Audio 2.0 only, Section 22.214.171.124) and/or the sync feedback endpoint is omitted (see Table 4.)
Table 4 illustrates the synchronization method used by the driver in various scenarios. If indicated by the “Usage type” field, the driver will treat the input stream as implicit feedback and ignore an additional sync feedback endpoint if present (Config 2.) This allows a device to implement both feedback mechanisms if needed for compatibility reasons. Config 3 is only recommended for USB Audio 1.0 devices where endpoint “Usage type” is not available.
Input endpoint descriptor specifies implicit feedback usage type
Feedback endpoint present
Meets implicit requirements
Only for compatibility
Only for USB Audio 1.0 devices
Note: We recommend using implicit feedback when possible because it conserves both device and host resources, and increases feedback precision.
Maximum Packet Size
It is very important to specify the correct value for each endpoint’s maximum packet size because an incorrect value could result in audio corruption. The packet size cannot exceed 1023 bytes for full speed devices and 1024 bytes for high speed devices (Section 5.6.3 of the USB 2.0 Specification.) To determine the exact value, one needs to identify the supported format and sample rate configuration that consumes the largest possible bandwidth for the endpoint.
The amount of audio data contained in each packet may vary depending on the speed of the device. If the device is full speed, each packet contains 1 millisecond (ms) of data. On high speed USB devices, each USB frame is split into eight 125 microsecond segments called microframes. Endpoints can specify the polling interval at which transfers can occur, i.e. every microframe, every other microframe, etc. This frequency must be taken into account when calculating the max packet size. (At this time, AppleUSBAudio supports at most one transaction per microframe. See the High Speed Streaming section for more information.)
The following full and high speed examples illustrate the calculation procedure:
A) 48 kHz / 24-bit / 2 channel / full speed
Each sample frame contains 2 channels of 3 byte samples which is 6 bytes per sample frame. The packet size is calculated as follows:
This value assumes that the data rate will never vary, as is the case when the stream is synchronous to SOF. If the endpoint is adaptive or asynchronous, one additional sample frame should be added to accommodate adjustments in the data rate. Section 126.96.36.199 of the Audio Data Formats 2.0 Specification limits variation in the packet size by +/- 1 sample frame.
Synchronous: Max packet size = 288 bytes
Adaptive or asynchronous: Max packet size = 288 + 6 = 294 bytes
B) 44.1 kHz / 16-bit / 8 channel / full speed
Each sample frame contains 8 channels of 2 byte samples which is 16 bytes per sample frame. The packet size is calculated as follows:
Packets cannot contain partial sample frames. So, while most packets will contain 44 sample frames, every tenth packet will contain 45 sample frames.
Synchronous, adaptive or asynchronous*: Max packet size = 720 bytes
*The extra permitted sample frame has already been included.
C) 192 kHz / 32-bit / 10 channel / high speed
This example assumes one transaction every microframe (i.e. the polling interval is 1 microframe.)
Each sample frame contains 10 channels of 4 byte samples which is 40 bytes per sample frame. The packet size is calculated as follows:
Adaptive or asynchronous: Max packet size = 960 + 40 = 1000 bytes
Sample rate (Hz)
Average sample frames per ms
Max sample frames per ms (sync)
Trans-actions per ms
Max packet size, sync (bytes)
Max packet size, adapt & async (bytes)
How AppleUSBAudio Uses the Max Packet Size
When starting a stream, the driver reserves the minimum USB isochronous bandwidth possible: the minimum of the max packet size and the bandwidth required for the current sample rate and format. This maximizes the remaining available bandwidth for other USB devices, including other audio devices connected to the Mac. It also increases the likelihood that the bandwidth request will be granted in situations where much of the bandwidth is already in use.
When determining the max packet size, make sure not to forget the extra sample frame in the calculation for these special cases:
Sample rates that do not divide evenly into packets (i.e. 44.1 kHz)
Adaptive and asynchronous endpoints
When streaming, devices must always observe the bandwidth restrictions for each of the sample rate and format settings. This includes the +/- 1 sample frame rule in Section 188.8.131.52 of the Audio Data Formats 2.0 Specification.
Warning: Failure to comply with the bandwidth rules for the current sample rate and format may not only result in audio corruption for that particular stream, but for all of the other streams on the same engine.
USB Audio Controls
AppleUSBAudio parses the audio control interface descriptors to discover the audio topology for a USB audio device. The topology consists of building blocks or units that represent the audio function and provide a mechanism to manipulate parameters, like adjusting the audio controls. Figure 2 shows a simple topology that consists of Input and Output Terminals in blue, Feature Units in yellow, and a Selector Unit and a Mixer Unit in orange.
AppleUSBAudio uses the information contained in the audio topology to find a device’s input and output volume/mute controls, hardware play through controls, input selector, and even clock source options for USB Audio 2.0 devices. AppleUSBAudio exposes these controls to Core Audio as IOAudioControls. This section focuses on volume, mute, and play through controls specifically.
Feature Units contain volume and mute controls which can logically map to volume, mute, and hardware play through controls on the Mac. When AppleUSBAudio creates input and output stream volume and mute IOAudioControls, these appear in Sound Preferences and the Audio MIDI Setup (AMS) application. In the case of play through, a Feature Unit’s mute control appears as a “Thru” toggle in AMS only. The play through volume controls are also published by AppleUSBAudio but do not appear in AMS or the Sound Preferences pane. However, they can be accessed via the developer audio utility HALLab.
Important: Since play through volume is not accessible to the user in AMS, developers should set the device's play through volume control default to a reasonable level to ensure a good user experience.
Control Publishing Rules
Since multiple Feature Units can exist in an audio path, AppleUSBAudio uses a special algorithm to select the Feature Unit that contains the logical controls to expose to the Audio HAL. The algorithm seeks to accommodate the most common cases and to minimize undesirable side effects. The rules are as follows:
* Volume/mute for input sources: AppleUSBAudio will publish the controls contained in the Feature Unit closest to the selector unit on the Input Terminal side as shown in Figure 3.
Important: Volume and mute controls intended to control the same source should be contained in the same Feature Unit (i.e. do not separate volume and mute in two consecutive Feature Units.)
* Volume/mute for output sources: AppleUSBAudio will publish the controls contained in the Feature Unit closest to the Output Terminal as shown in Figure 4.
* Hardware play through with Mixer Unit in path: AppleUSBAudio will publish controls contained in a Feature Unit between the Input Terminal and the Mixer Unit. Searching from the Input Terminal to the Mixer Unit, the driver selects the first Feature Unit that isn't shared with another audio path. An example is shown in Figure 5.
Important: Play through controls cannot be shared with another audio path because this could result in unwanted side effects. For example, if a play through control is also contained in a record path, muting the play through control would also unintentionally mute the recording input.
* Hardware play through without Mixer Unit in path: AppleUSBAudio will publish controls contained in the Feature Unit closest to the Input Terminal that isn't shared with another audio path.
A status interrupt pipe can be used to inform the host that a setting has changed on the device. This feedback maintains synchronization between the Mac’s user interface and the device state. Currently, AppleUSBAudio updates certain audio controls on the Mac for interrupts originating from Feature, Selector and Clock units as described in Table 6.
Example device event that triggers an interrupt
Mac response to interrupt
Volume and mute
User turns volume knob
Volume is updated in AMS and Sound Preferences UI
Input path selector
User switches toggle from microphone input to line input
“Source” selector is updated to “Line input” in AMS’s input tab for the device
Clock unit (USB Audio 2.0 only)
Clock validity, supported sample rate(s) changed
User disconnects S/PDIF cable which was in use as the Clock Source
AppleUSBAudio switches to an alternate valid Clock Source and updates selector in AMS
Please refer to Section 184.108.40.206 of the USB Audio 1.0 standard and Section 6 of the USB Audio 2.0 standard for more information.
Another way to improve the user experience with a USB audio class device on Mac OS X is to provide meaningful and descriptive device and channel names. The following sections will explain how to accomplish this with the device’s configuration descriptors.
The device name will appear in many places on the Mac, including in Audio MIDI Setup, Sound Preferences, and in third party audio applications. Core Audio represents each engine as a device in the system. If an engine has a name, Core Audio will use that as the device name, otherwise it will use the USB device name. Figure 6 shows how AppleUSBAudio and Core Audio will determine the descriptive name assigned to the device, depending on the number of streams associated with the engine, and the presence of the control and stream interface names, and USB device name.
AppleUSBAudio supports the Audio Cluster Descriptors as described in section 220.127.116.11 “Audio Channel Cluster Format” of the USB Audio 1.0 specification and section 4.1 “Audio Channel Cluster Descriptor” in the USB Audio 2.0 specification. These descriptors allow device developers to name the channels in a stream, using either predefined names (such as “Front Left”, or “Low Frequency Effects”, etc.) or custom names. Listing 1 shows the descriptor fields of interest, as represented in AppleUSBAudio. Please refer to the USB Audio specification sections previously mentioned for a thorough explanation of the use of these fields.
Listing 1 Structure representing the Audio Cluster Descriptor in AppleUSBAudio
Audio Cluster Descriptors can be embedded in Input Terminal, Mixer, Processing, and Extension Unit descriptors. AppleUSBAudio searches for the Audio Cluster Descriptor on an audio path starting from the Output Terminal to the Input Terminal and uses the first one it finds.
Supported USB Audio 2.0 Features
AppleUSBAudio was enhanced in Snow Leopard to support many of the key features contained in the USB Class Definition for Audio Devices 2.0 specification. The following features are currently supported:
High Speed Streaming
(USB 2.0, Sections 5.6 and 9.6.6)
Mac OS X supports high speed streaming, up to 1024 bytes per microframe for each isochronous endpoint, including overhead.
Note: The actual bandwidth available for endpoints depends on the current available bandwidth on the USB bus.
For example, Snow Leopard (and later) is able to stream 10 channels of 32-bit audio at 192 kHz to and from a USB Audio 2.0 device. Additional information pertaining to isochronous data transfer can be found in the USB Device Interface Guide.
Interface Association Descriptor
(USB Audio 2.0, Section 4.6)
This required descriptor identifies an Audio Interface Collection. The interfaces grouped in the collection must be contiguously numbered and in the following order:
AudioControl Interface (mandatory)
(USB Audio 2.0, Sections 3.13.11, 18.104.22.168 - 22.214.171.124)
Clock Domains are described using the new 2.0 Clock Entities: Clock Source, Clock Selector, and Clock Multiplier. The AppleUSBAudio driver also supports the associated clock related AudioControl Requests as specified in Sections 126.96.36.199 through 188.8.131.52.
Unlike USB Audio 1.0 devices, the use of switching the Alternate Setting to control the sampling frequency is prohibited for USB Audio 2.0 devices. Instead, a Clock Source entity serves as the master clock for a clock domain, which can provide a sampling signal frequency. Clock Selectors enable both the host and the audio function to switch clock inputs. Figure 7 shows how a Clock Selector appears in AMS. The Clock Multiplier provides a mechanism to derive additional sampling frequencies within a clock domain that are synchronous to the input clock signal.
Status Interrupt Control Endpoint
(USB Audio 2.0, Section 184.108.40.206, 6)
AppleUSBAudio contains additional support for parsing the Interrupt Data Message Format in Section 6.1. The only additional 2.0 status interrupt support added to the driver was for the Clock Source unit.
AppleUSBAudio responds in various ways to an interrupt generated from a Clock Source unit that is currently driving the data rate. If the clock validity bit indicates the clock is invalid and the audio topology contains a Clock Selector, the driver searches for an alternate valid Clock Source and switches to that (as described in Table 6.) If the Clock Source is valid, then it assumes the sample rate has changed. In this case, it republishes the available rates and updates the current device sample rate on the host.
Ways to Extend the Class Driver
AppleUSBAudio was designed to allow for some vendor specific extensions. This gives developers the advantage of adding special features without having to maintain the basic feature set of a high performance audio driver.
One way to augment the behavior of the class driver is to provide a codeless kernel extension (kext) that overrides certain properties of a USB audio device. These properties include the USB device and interface names, localization bundle, Core Audio HAL plugin, providing access to a custom control panel via Audio MIDI Setup's 'Configure device...' option and more. This sample code illustrates the various properties that can be modified.
Another way to customize AppleUSBAudio is to add vendor specified DSP processing to input and/or output audio streams. Developers can create a custom USB audio plugin that performs audio signal processing only for their device. This mechanism can also be used to provide access to a custom control panel. In the initialization routine, call
super::pluginSetConfigurationApp() with the control panel's application bundle ID.
Document Revision History
Updated to include integrating a custom control application from a codeless override kext.
Updated with a new section describing feedback mechanisms for asynchronous output streams, including implicit feedback. Made minor editorial corrections.
New document that details Apple's support for USB audio to help developers design class compliant devices that work seamlessly with the Mac.