05.01.2013 Views

Dialogue Editing

Dialogue Editing

Dialogue Editing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

18 NO ONE WORKS IN A VACUUM<br />

reference, 24 fps fi lm) or “pulled down” for video (44.056/47.952 kHz, 29.97<br />

frame TC, 59.94 Hz line reference, 23.976 fps fi lm speed), keep the picture and<br />

the sound at the same reference at any given step and you’ll have no problems.<br />

You can pull up and pull down as many times as you want; just do the<br />

same to sound and picture at each step and your NTSC blues will vanish.<br />

A Note about Drop-Frame Timecode<br />

Let’s get something straight. “Non-drop-frame timecode” does not mean<br />

30 fps and “drop-frame timecode” does not mean 29.97 fps. The dropness or<br />

non-dropness of a timecode fl avor has to do with how it counts, not how fast<br />

it runs. A drop-frame calendar (say, the Gregorian) includes leap years to<br />

keep it in sync with the solar year, while a non-drop-frame calendar (the<br />

Islamic, for instance) has no mechanism to keep it in solar sync. Both calendars<br />

run at the same rate—a day is a day, an hour is an hour, a minute is a<br />

minute. But one has a built-in “hitch” to force it back into sync with the<br />

seasons, while the other doesn’t. Christmas always holds a hope of snow, but<br />

Ramadan can occur in any season.<br />

SMPTE timecode works much the same way. Both non-drop-frame and dropframe<br />

timecode count 30 frames per second, 60 seconds per minute, and so<br />

forth. The difference is that with 29.97 drop-frame timecode an hour of timecode<br />

equals an hour of clock time because the counting mechanism has a<br />

way of realigning with reality, whereas an hour of 29.97 non-drop-frame<br />

timecode is 3 seconds—18 frames longer than a clock hour. Still, despite its<br />

seeming inaccuracy, non-drop-frame’s simplicity makes it the standard in<br />

fi lm production.<br />

Single-System NTSC Production and <strong>Editing</strong><br />

There are no secrets to single-system NTSC production. It’s very straightforward—the<br />

sound is recorded onto the videotape along with the picture,<br />

and there’s no speed change throughout postproduction. The timecode for<br />

the sound and the picture is the same, so it’s the most straightforward of all<br />

of the processes. Figure 2-2 shows the NTSC single-system workfl ow.<br />

After the shoot, the video dailies are loaded into the picture workstation, the<br />

picture is usually highly compressed to allow for manageable storage. There’s<br />

nothing to sync, plus sound and picture share the same timecode so list<br />

management is not complicated.<br />

When picture editing is fi nished, the editor makes an OMF and sound EDLs<br />

for the sound department. The OMF (which will be discussed in Chapter 5)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!