beautypg.com

5 interpreting playback statistics, 1 current and peak player amounts (cur | peak), 2 update time (update tm) – Grass Valley Channel Composer v.1.6.2 User Manual

Page 84: Interpreting playback statistics

background image

Channel Composer User Manual - Channel Composer User Manual- document version: 1.6.2 - 83

11.5 Interpreting playback statistics


11.5.1 Current and peak player amounts (cur | peak)
Use these numbers to determine if started players - especially players that create a lot of load such as

‘clip’, ‘ani’ and ‘live‘ - are stopped later on. Values should stabilize and then decrease at some point in

time.
Example: if a template running a fixed length animation is started, the current ani-value will first increase

by one. If the template is well designed (i.e. the player is stopped on the timeline at some point) the value
should decrease by one sometime later.

Note that the number next to ‘clip’ will probably always be one, since usually a full screen clip is always

running.

When to act: if the player amounts keep increasing over a longer period of time, or if amounts are

high for important player types:

o clip > 2

o big ani > 2

o live > 2

o text > 20

o fullscreen clip + fullscreen ani + fullscreen live > 3

o fullscreen still > 2

How to act: check your templates for the existence of Out Points. Ideally, every player should have

an Out Point, except for probably the main Clip and Live players that run continuously.


11.5.2 Update time (update tm)
Shows the duration in milliseconds of the update phase. Within the update phase, the states of all active

objects are updated.

All durations listed below are based on NTSC. For PAL, add 25% to values.

When to act: when this value exceeds ~5ms.

How to act:

o If this value peaks above 5ms but then immediately falls back to an acceptable value:

This probably means that nexos is overloaded due to too many simultaneously occurring

object In Points.


Spread In Points of objects across multiple frames, where possible.

o If this value stays above 5ms:

This probably means that too many objects and/or templates are active at the same time.


Reduce the amount of running objects and/or templates. Use Out Points to deactivate objects.