Grass Valley K2 AppCenter v.9.0 - Manual (Page 238)

Does data track
have AFD packets?
No AFD output
Output AFD directly
from data track
Output translasted AFD
value from clip property Output AFD value
from clip property Output translated AFD
values from data track Output default
generated AFD
Was ARC
performed?
Does data track
have AFD packets?
Is “generate AFD”
set to “never”?
Is AFD/ARC clip
property set?
Was ARC
performed?
Does data track
have AFD packets?
Is “generate AFD”
set to ”always”?
Start
Yes Yes
Yes Yes Yes
Yes Yes
Yes
No
No
No
No
No
No
“never”
No
“always”
“when
known”
“when known”
or “always”
Storing AFD on K2 Summit/Solo systems
The K2 Summit/Solo system stores clip metadata in clip properties and uses this data throughout
the workflow. You can modify the AFD setting in AppCenter.
You can store AFD in a data track. Grass Valley recommends selecting this for HD clips; if using
SD, this is optional. This method takes more storage (it is approximately equal to four tracks of
audio) but this method enables AFD and CC/Teletext support for HD.
Ingesting SDI
An SDI video signal stores AFD in the vertical ancillary data. The K2 Summit/Solo system processes
the signal as follows:
• If present, the AFD setting from two seconds into the file is copied into the clip properties. This
is the default K2 system behavior and occurs unless you set it to
No in Configuration Manager.
• If selected, the ANC data is copied into the K2 data track.
Using AFD with file transfers
The following tables describe the AFD file priorities and the AFD behavior with GXF and MXF
transfers.
238 K2 AppCenter User Manual 29 October 2012
Specifications