Grass Valley K2 Media Client System Guide Oct.10 2006 - Manual (Page 136)

136 K2 Media Client System Guide September 7, 2006
Appendix A Specifications
Internationalization
When you enable internationalization on a K2 Media Client, you can name your
media assets in a local language. The K2 Media Client supports the local language
name as specified in the following table:
Video network performance
The K2 Media Client supports streaming transfers to and from K2 Media Clients,
M-Series iVDRs, Profile XP Media Platforms, or any device that supports General
Exchange Format (GXF) as described in SMPTE 360M.
System Internationalization support
Media database • All external views of movie assets can be represented as wide-file names
• AppCenter runs in Unicode
• Only movie assets and searchable User Data keys are Unicode.
Media file system • Support for Kanji and wide-character file and folder names.
• File-folder representation of movie are internationalized, as well as the
QuickTime reference file it contains.
• Key names (V:\PDR) remain unchanged, but are Unicode.
• Elementary streams remain as GUIDs, but are Unicode.
K2 Media Client
applications • Movie assets are described in Unicode.
• Application user interfaces are Unicode compliant.
Protocols • AMP supports UTF-8. Unicode movie names pass through as opaque
bits.
• VDCP does not support UTF-8. VDCP protocols are ASCII and VDCP
protocol handler needs to convert movie names to Unicode.
FTP transfers • Non-ASCII localized characters represented as UTF-8 characters.
• All FTP client/server commands are in ASCII.
• The named movie asset is Unicode 16-bit characters
Parameter Specification Comments
Transfer bandwidth per internal storage K2 Media
Client Up to 50 MBytes per second —
Transfer bandwidth per Level 2 K2 Storage 50 MBytes per second —
Transfer bandwidth per Level 3 K2 Storage 80 MBytes per second Additional K2 Media Servers
dedicated as FTP servers add 80
MBytes per second each
Maximum concurrent transfers per transfer
engine 4 Additional transfers are queued.
Minimum delay from start of record to start of
transfer 20 seconds This applies to both 60Hz timing
and 50Hz timing.
Minimum delay between start of transfer into
destination and start of play on destination 20 seconds. —