Grass-valley K2 Edge Protocol Manual v1.0 User Manual

Browse online or download User Manual for Equipment Grass-valley K2 Edge Protocol Manual v1.0. Grass Valley K2 Edge Protocol Manual v1.0 User Manual

  • Download
  • Add to my manuals
  • Print

Summary of Contents

Page 1 - K2 Edge Protocol Manual

K2 Edge Protocol Manual Document version: 1.0 - 8-3-2012

Page 2 - Table of Contents

K2 Edge Protocol Manual – document version 1.0 – Page 10 4. API NRE Command 4.1. Introduction The K2 Edge API NRE command allows remote control ove

Page 3

K2 Edge Protocol Manual – document version 1.0 – Page 11 4.3. The exid field The exid field in the command string is a mandatory field. This field i

Page 4

K2 Edge Protocol Manual – document version 1.0 – Page 12 4.5. The role field The NRE command supports the concept of initiator roles, where differen

Page 5 - 2. Introduction

K2 Edge Protocol Manual – document version 1.0 – Page 13 4.6. Scene parameters Some sub commands accept scene parameters, plug-in values similar to

Page 6 - 3.1. Introduction

K2 Edge Protocol Manual – document version 1.0 – Page 14 4.8. Sub command preload-play Function: preloads a template instance and automatically star

Page 7 - 3.6. Waiting for feedback

K2 Edge Protocol Manual – document version 1.0 – Page 15 4.9. Sub command preload Function: prepares a template for playback. field name field type

Page 8

K2 Edge Protocol Manual – document version 1.0 – Page 16 4.10. Sub command play Function: starts playback of a template. field name field type valu

Page 9 - 3.9. The API protocol

K2 Edge Protocol Manual – document version 1.0 – Page 17 4.11. Sub command sg-preload Function: prepares a scene graph for selection by loading it

Page 10 - 4. API NRE Command

K2 Edge Protocol Manual – document version 1.0 – Page 18 4.12. Sub command sg-select Function: selects a previously preloaded scene graph waiting in

Page 11 - 4.4. The inst field

K2 Edge Protocol Manual – document version 1.0 – Page 19 4.13. Sub command object-info Function: returns information via feedback on an NRE object (

Page 12 - 4.5. The role field

K2 Edge Protocol Manual – document version 1.0 – Page 2 Table of Contents 1. Grass Valley Product Support ...

Page 13 - 4.6. Scene parameters

K2 Edge Protocol Manual – document version 1.0 – Page 20 4.14. Sub command sp-print Function: prints the values of all scene parameters to the stand

Page 14 - spvalue0=a0000123.mpg;}

K2 Edge Protocol Manual – document version 1.0 – Page 21 5. K2 Edge API NRE Feedback 5.1. Introduction The K2 Edge API NRE commands support a dedic

Page 15 - 4.9. Sub command preload

K2 Edge Protocol Manual – document version 1.0 – Page 22 During this life cycle the template instance passes a number of well-defined points such as

Page 16 - 4.10. Sub command play

K2 Edge Protocol Manual – document version 1.0 – Page 23 5.6. Feedback levels Three feedback levels can be defined: level description basic The def

Page 17

K2 Edge Protocol Manual – document version 1.0 – Page 24 5.8. What is returned Feedback messages are a copy of the original NRE command, enriched wi

Page 18 - 4.12. Sub command sg-select

K2 Edge Protocol Manual – document version 1.0 – Page 25 5.9. Sub command preload-play The preload-play command combines the individual preload and

Page 19

K2 Edge Protocol Manual – document version 1.0 – Page 26 5.9.2. Feedback level 'basic' Coverage from the reception point up to and includ

Page 20 - 4.15. Sub command control

K2 Edge Protocol Manual – document version 1.0 – Page 27 Note the presence and value of fb-term-sw in the last message, indicating feedback ends for

Page 21 - 5. K2 Edge API NRE Feedback

K2 Edge Protocol Manual – document version 1.0 – Page 28 Example: This example of a preload-play command sent to nexos uses feedback level 'mos

Page 22

K2 Edge Protocol Manual – document version 1.0 – Page 29 5.9.4. Feedback level 'full' Coverage from the reception point up to and includi

Page 23 - 5.7. Enabling feedback

K2 Edge Protocol Manual – document version 1.0 – Page 3 5.5. Life cycle points and events ...

Page 24 - 5.8. What is returned

K2 Edge Protocol Manual – document version 1.0 – Page 30 The feedback messages from nexos are listed. This time we show a failure path, note (8) in t

Page 25

K2 Edge Protocol Manual – document version 1.0 – Page 31 5.10. Sub command preload Sub command preload prepares a template instance for a later play

Page 26

K2 Edge Protocol Manual – document version 1.0 – Page 32 5.10.3. Feedback levels 'most' and 'full' Coverage from the reception

Page 27

K2 Edge Protocol Manual – document version 1.0 – Page 33 5.11. Sub command play Sub command play starts a template instance at the start time, provi

Page 28

K2 Edge Protocol Manual – document version 1.0 – Page 34 Notes: 1) The command is considered valid at the reception point and the command started s

Page 29 - fb-sw=true; fb-lev=full;}

K2 Edge Protocol Manual – document version 1.0 – Page 35 5.11.4. Feedback level 'full' Coverage is complete from reception point up to a

Page 30

K2 Edge Protocol Manual – document version 1.0 – Page 36 5.12. Sub command object-info Sub command object-info returns info on a given NRE object vi

Page 31 - 5.10. Sub command preload

K2 Edge Protocol Manual – document version 1.0 – Page 37 Notes: 1) 1) The command is considered valid at the reception point and the command comple

Page 32

K2 Edge Protocol Manual – document version 1.0 – Page 38 6. K2 Edge API Source String Format 6.1. Introduction The source string format defines an

Page 33 - 5.11. Sub command play

K2 Edge Protocol Manual – document version 1.0 – Page 39 where the files are scanned in the order specified. Note that non-audio streams are ignored.

Page 34

K2 Edge Protocol Manual – document version 1.0 – Page 4 7.4.1. Channel Director option ...

Page 35

K2 Edge Protocol Manual – document version 1.0 – Page 40 6.3. Supported fields A complex source string is limited to a set of well-defined field/val

Page 36

K2 Edge Protocol Manual – document version 1.0 – Page 41 6.3.2. Routing table fields The following fields set up the routing table, where video- or

Page 37

K2 Edge Protocol Manual – document version 1.0 – Page 42 6.3.3. Timecode range fields The following timecode range fields allow the initiator to pl

Page 38 - 6.1. Introduction

K2 Edge Protocol Manual – document version 1.0 – Page 43 6.3.4. Relative timecode range fields Similar to the timecode range fields above, but this

Page 39

K2 Edge Protocol Manual – document version 1.0 – Page 44 6.3.5. Absolute timecode range fields for MXF files Similar to the timecode range fields ab

Page 40 - 6.3. Supported fields

K2 Edge Protocol Manual – document version 1.0 – Page 45 fileN-atc-end optional hh:mm:ss:ff timecode string in timecode format of media file Similar

Page 41

K2 Edge Protocol Manual – document version 1.0 – Page 46 fileN-lipsync-offset-ms optional [-10000, 10000] Specifies an explicit lipsync offset in mil

Page 42

K2 Edge Protocol Manual – document version 1.0 – Page 47 7. Channel Pack Management 7.1. Introduction When designing a channel, all elements of the

Page 43

K2 Edge Protocol Manual – document version 1.0 – Page 48 7.3. Channel pack workflow The workflow to bring a channel pack on-air contains the followi

Page 44

K2 Edge Protocol Manual – document version 1.0 – Page 49 7.4. How to bring a Channel Pack on-air The previous section generically described the step

Page 45

K2 Edge Protocol Manual – document version 1.0 – Page 5 1. Grass Valley Product Support Contact information: http://www.grassvalley.com/support/cont

Page 46

K2 Edge Protocol Manual – document version 1.0 – Page 50 8. Complex String Format 8.1. Introduction A complex string is a text string defining zero

Page 47 - 7. Channel Pack Management

K2 Edge Protocol Manual – document version 1.0 – Page 51 8.3. Field identifier The field identifiers (or field names) consist of lower case letters,

Page 48 - 7.3. Channel pack workflow

K2 Edge Protocol Manual – document version 1.0 – Page 52 8.6. Data wrappers The complex string format allows for data to be wrapped by a number of w

Page 49

K2 Edge Protocol Manual – document version 1.0 – Page 6 3. Nexos Socket Server Communication Setup 3.1. Introduction Nexos is the real-time playout

Page 50 - 8. Complex String Format

K2 Edge Protocol Manual – document version 1.0 – Page 7 3.3. Code examples This section provides a number of coding examples. Note that the example

Page 51 - 8.4. Field value

K2 Edge Protocol Manual – document version 1.0 – Page 8 3.7. Closing the link when no longer needed Remember to close the link with the socket serve

Page 52 - 8.6. Data wrappers

K2 Edge Protocol Manual – document version 1.0 – Page 9 3.9. The API protocol The nexos socket server supports a number of different services, the m

Comments to this Manuals

No comments