Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Buffering

Usually just:out buffers between less than half a second and three 0.5 and 3 seconds of the final uncompressed final output uncompressed in the RAM to make sure the playout can continue without dropping frames even under bad conditions. A bad condition usually has two reasons:

Bad Conditions

  • Case 1: The storage system is not fast enough to deliver the required data. This could happen because (1) because…
    • the disk is getting full
    (2)
    • heavy copying of files
    (3)
    • many users access the same storage system at the same time
    (3)
    • the file system is heavily fragmented.
  • Case 2: The GPU isn't able to render the content fast enough, because the current graphic is too complex. Remember that real time graphics can put heavy load on the CPU, GPU and the file system – especially if they read out dozens of data sources at the same time.

In both cases the just:out pipeline buffer will be quickly exhausted (the buffer status will decrease and turn red) a buffer underrun may occur and eventually just:out will begin to drop video frames. To guard against this, just:out will automatically "eject" the most recently started graphic if the

Auto Eject

If the pipeline buffer reaches a critical state and stays there for half a second or longer. Further, if ejecting the graphic more than 0.5 seconds just:out will automatically eject the most recently started graphic. If this does not result in the pipeline recovering to a non-critical state then all non-in nite infinite graphics will be automatically ejected. We recommend that you test

Note

Test any graphics

...

before taking them on air to ensure

...

they will be played out properly.

Visual Representaion of the Buffer

Gliffy
size300
nameadmin 8.8a

just:out diagnostic window

The buffer status is shown in just:out's diagnostic window (if available). Before the buffer status reaches a critical level the auto eject function steps in.

Gliffy
size300
nameadmin 8.8b

just:connect and just:live user interface

The buffer status is also shown as an overlay in the proxy preview of just:connect and directly in the just:live user interface. Please see the just:live user manual 4.3 Control Area Buffer Status Overlay (v2.0) for more informations.

Gliffy
size300
nameadmin 8.8c

just:play user interface

In the just:play user interface, the buffer status is shown in the control area, right below the master TC.

...