Difference between revisions of "Working Lives: Audio Decision List (ADL) Template"

From UA Libraries Digital Services Planning and Documentation
(New page: Notes need to be precise and direct with minimal verbiage. For now, the only processes we can apply are: 1. Normalization, 2. Volume, 3. extraneous silence/noise deletion (do this only ...)
 
 
(31 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{rfd}}
 +
 +
<!--
 +
The following guidelines and ideas are based on experimental documentation of Edit Decision Lists(EDL)/Audio Decision Lists (ADL) information that was not performed for the entire audio collection.
 +
It will serve, however, as the basis for future audio digitization projects.
 +
Eventually, [[Audio Specifications and Standards#Resources and Links: |ADL standards]] and compatible software will be further researched for automated EDL/ADL creation. - arora, 042909
 +
 +
==Editing Working Lives: Audio Decision List (ADL) Template==
 +
 
Notes need to be precise and direct with minimal verbiage.
 
Notes need to be precise and direct with minimal verbiage.
 +
  
 
For now, the only processes we can apply are:
 
For now, the only processes we can apply are:
1. Normalization,  
+
#Normalization,  
2. Volume,  
+
#Volume,  
3. extraneous silence/noise deletion (do this only after the extraneous beginning and end of the recording).  
+
#extraneous silence/noise deletion (do this only after the extraneous beginning and end of the recording).  
4. and hard limiting using the setting "[Sys] Limit levels to -6 dB (hard limiter)". We will truncate the hard limiter to be written as "-6db HARD LIMITER".
+
#and hard limiting using the setting "[Sys] Limit levels to -6 dB (hard limiter)". We will truncate the hard limiter to be written as "-6db HARD LIMITER".
 +
 
  
All notes, should be prefaced with "Note:" and should be written only after all technical information regarding levelling, etc. The notes should be complete sentences, but if they refer to only a particular portion of the recording  
+
All notes, should be prefaced with "Note:" and should be written only after all technical information regarding leveling, etc. The notes should be complete phrases, but if they refer to only a particular portion of the recording always begin with the timecodes.
  
always begin with the timecodes.
 
  
 
Note that all timecodes are surrounded by [brackets]. This includes numerical data as well as [START] and [END].
 
Note that all timecodes are surrounded by [brackets]. This includes numerical data as well as [START] and [END].
  
DO NOT notate;
 
1. our additions of 2s silence at beginning and 1s silence at end of recording.
 
2. silence we delete from the beginning and end because it was created by the digitization process or because it represents blank tape on the source recording. We are only interest in notating silence we remove once the audio has gotten
 
  
underway.
+
'''DO NOT notate:'''
3. Deletion/Addition of markers.
+
#our additions of 2s silence at beginning and 1s silence at end of recording.
 +
#silence we delete from the beginning and end because it was created by the digitization process or because it represents blank tape on the source recording. We are only interested in notating silence we remove once the audio has gotten underway.
 +
#Deletion/Addition of markers.
  
  
 +
'''example:''' ''(note the use of CAPS for processes and timecodes)''
  
example:
+
_0001: DELETED [00:10:10:001] to [00:10:13:001] due to silence.
  
_0001: DELETED [00:10:10:001] to [00:10:13:001] due to silence.
 
 
DELETED [00:11:10:001] to [00:11:13:001] due to cable noise.
 
DELETED [00:11:10:001] to [00:11:13:001] due to cable noise.
 +
 
LEVELLED RECORDING to -25db AVERAGE RMS.
 
LEVELLED RECORDING to -25db AVERAGE RMS.
 +
 
APPLIED -6db HARD LIMITER from [00:21:01:001] to [00:21:10:001].
 
APPLIED -6db HARD LIMITER from [00:21:01:001] to [00:21:10:001].
 +
 
LEVELLED RECORDING to -25db AVERAGE RMS.
 
LEVELLED RECORDING to -25db AVERAGE RMS.
 +
 
APPLIED +2db VOLUME from [00:21:01:001] to [END].
 
APPLIED +2db VOLUME from [00:21:01:001] to [END].
 +
 
NOTE: [01:21:01:001] to [01:25:10:001] is a recording of a baseball game. The interview resumes at [01:25:10:001].
 
NOTE: [01:21:01:001] to [01:25:10:001] is a recording of a baseball game. The interview resumes at [01:25:10:001].
 +
 
NOTE: [START] to [00:05:10:001] is recorded at a higher pitch. This is native to the recording and is likely due to operator error during the interview.
 
NOTE: [START] to [00:05:10:001] is recorded at a higher pitch. This is native to the recording and is likely due to operator error during the interview.
 +
 
10:23 AM 2/24/2009 na.
 
10:23 AM 2/24/2009 na.
  
 
_0002: ...
 
_0002: ...
 +
 
10:45 AM 2/24/2009 ww.
 
10:45 AM 2/24/2009 ww.
  
 
_0003: ...
 
_0003: ...
 +
 
11:00 AM 2/24/2009 na.
 
11:00 AM 2/24/2009 na.
  
  
*HINT/SHORTCUT: pressing F5 in Notepad adds a  
+
*HINT/SHORTCUT: pressing F5 in Notepad adds a timestamp with time/date.
timestamp with time/date.
+
-->
 
 
 
 
 
 
 
 
*Notes for Nitin:
 
1. administrative metadata needs to say that RMS levelling would only, in case of potential clipping, normalize recording to 0db.
 
2. Admin metadata needs to also say that we are using HH:MM:SS:SSS timecode not SMPTE NON-DROP as we are in the JHOVE output. With the next project, maybe we should switch to SMPTE NON-DROP?
 

Latest revision as of 14:55, 19 August 2010