- Title
- An investigation into the hardware abstraction layer of the plural node architecture for IEEE 1394 audio devices
- Creator
- Chigwamba, Nyasha
- Subject
- IEEE 1394 (Standard)
- Subject
- Digital communications
- Subject
- Computer sound processing
- Subject
- Local area networks (Computer networks)
- Subject
- Computer network architectures
- Subject
- Sound -- Recording and reproducing -- Digital techniques
- Date Issued
- 2009
- Date
- 2009
- Type
- Thesis
- Type
- Masters
- Type
- MSc
- Identifier
- vital:4598
- Identifier
- http://hdl.handle.net/10962/d1004841
- Identifier
- IEEE 1394 (Standard)
- Identifier
- Digital communications
- Identifier
- Computer sound processing
- Identifier
- Local area networks (Computer networks)
- Identifier
- Computer network architectures
- Identifier
- Sound -- Recording and reproducing -- Digital techniques
- Description
- Digital audio network technologies are becoming more prevalent in audio related environments. Yamaha Corporation has created a digital audio network solution, named mLAN (music Local Area Network), that uses IEEE 1394 as its underlying network technology. IEEE 1394 is a digital network technology that is specifically designed for real-time multimedia data transmission. The second generation of mLAN is based on the Plural Node Architecture, where the control of audio and MIDI routings between IEEE 1394 devices is split between two node types, namely an Enabler and a Transporter. The Transporter typically resides in an IEEE 1394 device and is solely responsible for transmission and reception of audio or MIDI data. The Enabler typically resides in a workstation and exposes an abstract representation of audio or MIDI plugs on each Transporter to routing control applications. The Enabler is responsible for configuring audio and MIDI routings between plugs on different Transporters. A Hardware Abstraction Layer (HAL) within the Enabler allows it to uniformly communicate with Transporters that are created by various vendors. A plug-in mechanism is used to provide this capability. When vendors create Transporters, they also create device-specific plug-ins for the Enabler. These plug-ins are created against a Transporter HAL Application Programming Interface (API) that defines methods to access the capabilities of Transporters. An Open Generic Transporter (OGT) guideline document which models all the capabilities of Transporters has been produced. These guidelines make it possible for manufacturers to create Transporters that make use of a common plug-in, although based on different hardware architectures. The introduction of the OGT concept has revealed additional Transporter capabilities that are not incorporated in the existing Transporter HAL API. This has led to the underutilisation of OGT capabilities. The main goals of this investigation have been to improve the Enabler’s plug-in mechanism, and to incorporate the additional capabilities that have been revealed by the OGT into the Transporter HAL API. We propose a new plug-in mechanism, and a new Transporter HAL API that fully utilises both the additional capabilities revealed by the OGT and the capabilities of existing Transporters.
- Format
- 243 p.
- Format
- Publisher
- Rhodes University
- Publisher
- Faculty of Science, Computer Science
- Language
- English
- Rights
- Chigwamba, Nyasha
- Hits: 1842
- Visitors: 2007
- Downloads: 183
Collections
RU Department of Computer Science
| Thumbnail | File | Description | Size | Format | |||
|---|---|---|---|---|---|---|---|
| View Details Download | SOURCEPDF | 2 MB | Adobe Acrobat PDF | View Details Download |