Файл: Audio and Radio Engineering.pdf

10-14 Audio Production Standards, Equipment, and System Design

AES22-1997

: Storage of Polyester-Base Magnetic Tape

This standard provides recommendations concerning the storage conditions, storage facilities,
enclosures, and inspection for recorded polyester-base magnetic tapes in roll form. It covers ana-
log and digital tape and includes tape made for audio, video, instrumentation, and computer use.

AES24-1-1999, (Revision of AES24-1-1995):

 Application Protocol for Controlling and

Monitoring Audio Devices via Digital Data Networks—Part 1: Principles, Formats, and
Basic Procedures

This document describes the architecture of AES24, the name assigned to an extensible applica-
tion protocol for controlling and monitoring audio devices via local area networks, and, when
possible in the future, devices designed for other media.

AES26-1995

: Conservation of the Polarity of Audio Signals

This document standardizes the polarity of the signals at the various interface points between dif-
ferent items of equipment, in particular from the acoustical, electrical, and the magnetic aspects.
Each item of equipment complies separately with the polarity requirements for the input and out-
put signals.

AES27-1996

: Managing Recorded Audio Materials Intended for Examination

This document specifies recommended practices for safekeeping, conveyance, inspection,
description, and labeling of audio recordings offered as evidence in criminal investigations, in
criminal or civil proceedings, or in other forensic applications. It does not cover analysis of mag-
netic tapes or other recording media for the purposes of authenticity determination, talker identi-
fication, copyright violation, enhancement of oral conversations or other signals, or otherwise
characterizing signals recorded on such tapes.

AES28-1997

: Method for Estimating Life Expectancy of Compact Discs (CD-ROM),

Based on Effects of Temperature and Relative Humidity

This standard specifies test methods for estimating the storage life expectancy (LE) of informa-
tion stored on compact discs (CD-ROM). Only the effects of temperature and relative humidity
are considered. Block error rate (BLER) is the measured response and the end-of-life criterion.
An Eyring model is developed from accelerated test results. Data are normalized to 25 degree C
and 50 percent relative humidity, and the LE, percent compliance, and confidence intervals at
these conditions are calculated.

AES31-3-1999

: Audio-File Transfer and Exchange—Part 3: Simple Project Interchange

This standard provides a convention for expressing edit data in text form in a manner that enables
simple and accurate computer parsing while retaining human readability. It also describes a
method for expressing time-code information in character notation.

AES33-1999

: Database of Multiple-Program Connection Configuration

This document specifies the purpose and procedures for the maintenance of data on an AESSC
database of connectors for multiple-program applications. Purchasers of this standard obtain full
access to the database using their names and order numbers for identification.

Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)

Copyright © 2004 The McGraw-Hill Companies. All rights reserved.

Any use is subject to the Terms of Use as given at the website.

Audio Production System Standards

Audio Production System Standards 10-15

AES35-2000

: Method for Estimating Life Expectancy of Magneto-Optical (MO) Disks,

Based on Effects of Temperature and Relative Humidity

This standard specifies test methods for estimating the life expectancy of information stored on
magneto-optical (M-O) disks. Only the effects of temperature and relative humidity on the media
are considered.

AES38-2000

: Life Expectancy of Information Stored in Recordable Compact Disc Sys-

tems—Method for Estimating, Based on Effects of Temperature and Relative Humidity

This standard specifies test methods for estimating the life expectancy of information stored in
recordable compact disc systems. Only the effects of temperature and relative humidity on the
media are considered.

AES41-2000

: Recoding Data Set for Audio Bit-Rate Reduction

This document describes a format for the data to be transmitted to identify a number of popular
audio bit-rate reduction techniques. Provision is also made for the transmission of additional
ancillary information. This document also describes a mechanism whereby the data derived from
the coded signal can be transported with the decoded signal so that the data may be recovered
and used to aid a subsequent re-encoding process.

AES42-2001

: Digital Interface for Microphones

This standard describes an extension of the existing digital audio interface AES3 to provide a
digital interface for microphones.

AES43-2000

: Criteria for the Authentication of Analog Audio Tape Recordings

The purpose of this standard is to formulate a standard scientific procedure for the authentication
of audio tape recordings intended to be offered as evidence or otherwise utilized in civil, crimi-
nal, or other fact finding proceedings.

AES45-2001

: Connectors for Loudspeaker-Level Patch Panels

This standard complements IEC 60268-12 including amendments 1 and 2, extending the stan-
dardization of application of AES45-series connectors to their use for loudspeaker-level patch
panels.

10.1.4 Bibliography

McCroskey, Donald C.: “Standardization: History and Purpose,” in The Electronics Handbook,

Jerry C. Whitaker (ed.), CRC Press, Boca Raton, Fla., 1996.

Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)

Copyright © 2004 The McGraw-Hill Companies. All rights reserved.

Any use is subject to the Terms of Use as given at the website.

Audio Production System Standards

Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)

Copyright © 2004 The McGraw-Hill Companies. All rights reserved.

Any use is subject to the Terms of Use as given at the website.

Audio Production System Standards

10-17

Chapter

10.2

Production Facility Design

Gene DeSantis

Jerry C. Whitaker, Editor-in-Chief

10.2.1 Introduction

The implementation of digital broadcasting has launched an industry-wide upgrade program—
both on the RF side and the studio side. Planning how the audio facility will function is a diffi-
cult exercise, and one that will have far-reaching effects. The success of any upgrade project
depends in large part on the planning that goes into the effort before any concrete is poured or
any cables are pulled.

10.2.2 Project Management

The need for a project may originate with management, operations staff, technicians, or engi-
neers. In any case, some sort of logical reasoning or a specific production requirement will jus-
tify the need. On small projects, such as the addition of one piece of equipment, money must
only be available for the purchase and installation costs. When the need justifies a large project,
the final cost is not always immediately apparent. The project must be analyzed by dividing it
into its constituent parts or elements:

•

Equipment and parts

•

Materials

•

Resources, including money and time needed for project completion

An executive summary or capital project budget request, which contains a detailed breakdown of
these elements, can provide the information management needs to determine the return on
investment, and to make an informed decision on whether or not to authorize the project.

A capital project budget request, which contains the minimum information, may consist of

the following items:

Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)

Copyright © 2004 The McGraw-Hill Companies. All rights reserved.

Any use is subject to the Terms of Use as given at the website.

Source: Standard Handbook of Audio and Radio Engineering

10-18 Audio Production Standards, Equipment, and System Design

•

Project name—a name that describes the result of the project, such as “control room
upgrade.”

•

Project number (if required). A large organization that does many projects will use some kind
of project numbering system, or it may use a budget code assigned by the accounting depart-
ment.

•

Project description—a brief description of what the project will accomplish, such as “design
the technical system upgrade for the renovation of production control room 2.”

•

Initiation date—the date the request will be submitted.

•

Completion date—the date the project will be completed.

•

Justification—the reason the project is needed.

•

Material cost breakdown—a list of equipment, parts, and materials required for construction,
fabrication, and equipment installation.

•

Total material cost.

•

Labor cost breakdown—a list of personnel required to complete the project, their hourly pay
rates, the number of hours they will spend on the project, and the total cost for each person.

•

Total project cost—the sum of material and labor costs.

•

Payment schedule—an estimation of individual amounts that will be paid out during the
course of the project, and the approximate dates that each will be payable.

•

Preparer’s name and the date prepared.

•

Approval signature(s) and date(s) approved.

More detailed analysis, such as return on investment, can be carried out by an engineer. Financial
analysis, however, should be left to the accountants, who have access to company financial data.

10.2.2a

Feasibility Study and Technology Assessment

In cases where an attempt must be made to implement new technology, and where a determina-
tion must be made as to whether certain equipment can perform a desired function, a feasibility
study should be conducted. The system engineer may be called upon to assess the state of the art
in order to develop a new application. In addition to a capital project budget request, an executive
summary or a more detailed report of evaluation test results may be required to help management
make its decision.

10.2.2b

Project Tracking and Control

A project team member may be selected by the project manager to report the status of work dur-
ing the course of the project. A standardized project status report form can provide consistent
and complete information to the project manager. The purpose is to supply information to the
project manager regarding work completed and money spent on resources and materials.

A project status report containing minimum information should contain the following items:

•

Project number (if required)

Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)

Copyright © 2004 The McGraw-Hill Companies. All rights reserved.

Any use is subject to the Terms of Use as given at the website.

Production Facility Design