Production logging
Our logging system is designed to provide an efficient way for the Production
Assistant (PA) to log timecodes and comments for each ‘take’ as
the recording of the programme progresses. When a script is available
for the programme, it can first be loaded into the logger, and this
then allows all ‘takes’ to be logged against their point
in the script.
The logger is mainly controlled from a small keypad which allows the
PA to save the start and end timecodes, mark the ‘take’ as ‘Good’ or ‘No
Good’ and save the details.
We also arranged for the logging system
to be able to control the studio recorder too. In this case, when the
start of a ‘take’ is
logged, a record command is automatically sent to the ‘Ingex’ recorder,
which then starts to store the incoming SDI feeds from a point five seconds
beforehand. Similarly, when the end of the ‘take’ is logged,
the recorder is stopped automatically three seconds later.
For situations
where integrated control from the logging system is not required, a separate
recorder control application provides the familiar ‘transport’ controls
for independent control of the ‘Ingex’ recorder.
As the programme
recording progresses, the PA can periodically ‘publish’ the
logged details, which will trigger the processing of the video content
and logs. As described later, this makes them available downstream in
the production workflow, e.g. for review on webpages or editing in an
edit suite, etc. |
