Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

SMPTE Time Code and Console Automation: A Common Foundation - Prof. Billy W. Prince, Study notes of Speech-Language Pathology

An overview of smpte time code, its role in console automation systems, and the different modes of operation for automation systems. It covers the history of smpte time code, its use in various industries, and the functions of write, read, and update modes.

Typology: Study notes

Pre 2010

Uploaded on 12/12/2009

absentvirtue
absentvirtue 🇺🇸

15 documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
General Console Automation Info:
There are probably as many automation makers for audio consoles as there are console manufacturers.
Most automation systems, however can be fitted to most console manufacturers’ consoles. But there
are some basic things that they all share in common.
1. SMPTE Time Code. SMPTE time code, developed by the “Society of Motion Picture
Technicians & Engineers”, has for the most part become the universal time code reference for
computer automation systems and many other sync applications. Originally produced as a
means to synchronize motion pictures with audio, 24 fps (frames per second), made it possible
to eliminate the voice/picture delays that was often the result of voice-overs and editing. It’s
logical, since the picture frame rate itself is 24 still pictures per second. Other frame rates were
developed as technology progressed. EBU (European Broadcast Union) adopted 25 fps as their
frame rate. The audio recording industry adopted 30 fps for automation reference and control.
Video synchronization, because of scanning and clocking was close to 30 fps, but required an
adjustment in the frame rate of .03 frames, and what we know as “30 drop-frame” was born. In
actuality not a whole frame, but a small portion of a frame is dropped, and we now have the
rate of 29.97 fps. The full 30 fps rate is called “30 non-drop”. Analog tape is “striped” with
SMPTE on one track, usually track 24, and track 23 is left blank for safety reasons, so that the
time code will not “bleed” onto the adjacent track. Normally, a signal level that is between -
10dB and -7dB will be plenty of level, and will not present a crosstalk problem. RADAR has a
built in time code generator, so that other equipment can be “slaved” to and thereby “chase”
radar.
RADAR can also be set to receive time, code and thus be set to “chase” other
equipment. So then what sends the code is the MASTER unit, and the equipment
that receives it is the SLAVE. PRO TOOLS can also be set to be either the Master
or the Slave. The hardwire device that sends and/or receives SMPTE time code for PRO
TOOLS is the SYNC I/O.
2. Write Mode. For the most part, automation itself consists of recording Fader position (audio
level) data, and mute on/off data. The position or the conditions of these two components are
recorded into the computer along with the SMPTE time code. This is the WRITE Mode. This
is always the first mode of operation.
When the automation is in WRITE mode, it will either be writing new data, or
Replacing (writing over) existing data. The NEVE FLYING FADERS term for
WRITE is RECORD. The SSL Ultimation terminology for WRITE is
ABSOLUTE.
3. Read Mode. In the READ mode, the computer will play back the information that it recorded
in the WRITE or UPDATE mode, according to the values stored at the specific time code
location. While in READ, no changes can be made to the automation data. Some programs,
however, have touch write functions so that the automation can instantaneously be switched
from READ to WRITE just by touching or moving the fader. The NEVE term for READ mode
is PLAY. For SSL it is REVIEW.
4. UPDATE mode. In UPDATE, existing data may be adjusted, added to or subtracted from, but
is not overwritten. Both FYING FADERS, and ULTIMATION call this TRIM.

Partial preview of the text

Download SMPTE Time Code and Console Automation: A Common Foundation - Prof. Billy W. Prince and more Study notes Speech-Language Pathology in PDF only on Docsity!

General Console Automation Info : There are probably as many automation makers for audio consoles as there are console manufacturers. Most automation systems, however can be fitted to most console manufacturers’ consoles. But there are some basic things that they all share in common.

  1. SMPTE Time Code. SMPTE time code, developed by the “Society of Motion Picture Technicians & Engineers”, has for the most part become the universal time code reference for computer automation systems and many other sync applications. Originally produced as a means to synchronize motion pictures with audio, 24 fps (frames per second), made it possible to eliminate the voice/picture delays that was often the result of voice-overs and editing. It’s logical, since the picture frame rate itself is 24 still pictures per second. Other frame rates were developed as technology progressed. EBU (European Broadcast Union) adopted 25 fps as their frame rate. The audio recording industry adopted 30 fps for automation reference and control. Video synchronization, because of scanning and clocking was close to 30 fps, but required an adjustment in the frame rate of .03 frames, and what we know as “30 drop-frame” was born. In actuality not a whole frame, but a small portion of a frame is dropped, and we now have the rate of 29.97 fps. The full 30 fps rate is called “30 non-drop”. Analog tape is “striped” with SMPTE on one track, usually track 24, and track 23 is left blank for safety reasons, so that the time code will not “bleed” onto the adjacent track. Normally, a signal level that is between - 10dB and -7dB will be plenty of level, and will not present a crosstalk problem. RADAR has a built in time code generator, so that other equipment can be “slaved” to and thereby “chase” radar. RADAR can also be set to receive time, code and thus be set to “chase” other equipment. So then what sends the code is the MASTER unit, and the equipment that receives it is the SLAVE. PRO TOOLS can also be set to be either the Master or the Slave. The hardwire device that sends and/or receives SMPTE time code for PRO TOOLS is the SYNC I/O.
  2. Write Mode. For the most part, automation itself consists of recording Fader position (audio level) data, and mute on/off data. The position or the conditions of these two components are recorded into the computer along with the SMPTE time code. This is the WRITE Mode. This is always the first mode of operation. When the automation is in WRITE mode, it will either be writing new data, or Replacing (writing over) existing data. The NEVE FLYING FADERS term for WRITE is RECORD. The SSL Ultimation terminology for WRITE is ABSOLUTE.
  3. Read Mode. In the READ mode, the computer will play back the information that it recorded in the WRITE or UPDATE mode, according to the values stored at the specific time code location. While in READ, no changes can be made to the automation data. Some programs, however, have touch write functions so that the automation can instantaneously be switched from READ to WRITE just by touching or moving the fader. The NEVE term for READ mode is PLAY. For SSL it is REVIEW.
  4. UPDATE mode. In UPDATE, existing data may be adjusted, added to or subtracted from, but is not overwritten. Both FYING FADERS, and ULTIMATION call this TRIM.