Grass Valley K2 System Guide v.9.0 - Manual (Page 243)

Bin nesting limitations
The K2 media database supports nine levels of nested bins. This includes the top level (first) bin.
Exceeding this specification results in a database error. When creating a bin do not create a bin at
level ten or deeper.
For example:
• The following is supported:
default\en\fr\es\de\it\be\dk\cn
• The following is not supported:
default\en\fr\es\de\it\be\dk\cn\jp
Video network performance
K2 systems support streaming transfers to and from K2 Summit/Solo system, K2 Media Clients,
K2 SANs, Profile XP Media Platforms, or any device that supports General Exchange Format (GXF)
as described in SMPTE 360M.
Comments Specification Parameter
— Up to 50 MBytes per second Transfer bandwidth per internal
storage K2 Summit/Solo system
Depending on system design Up to 90Mbytes per second Transfer bandwidth per K2-SVR-100
Depending on system design Up to 600Mbytes per Second Transfer bandwidth per
K2-SVR-NH10GE
Additional transfers are queued. 4 to 10, configurable on SAN Maximum concurrent transfers per
transfer engine
This applies to both 60Hz timing and
50Hz timing. 20 seconds Minimum delay from start of record
to start of transfer
— 20 seconds Minimum delay between start of
transfer into destination and start of
play on destination
About file interchange mechanisms on K2 systems
K2 Summit, Solo, and SAN systems can send and receive files as follows:
• File based import/export — This is based on a file that is visible from the operating system. For
example, AppCenter import/export features are file based.
• HotBin import/export — This is file based import/export, with automated features that are
triggered when a clip is placed in a bin. Some HotBin functionality requires licensing.
• FTP stream — This is file interchange via File Transfer Protocol (FTP).
06 November 2012 K2 System Guide 243
Specifications