8.6 "Auto Eject" Function (v2.0)
Buffering
Usually just:out buffers between 0.5 and 3 seconds of the uncompressed final output in the RAM to make sure the playout can continue without dropping frames even under bad conditions.
Bad Conditions
- Case 1: The storage system is not fast enough to deliver the required data. This could happen because…
- the disk is getting full
- heavy copying of files
- many users access the same storage system at the same time
- 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.
In both cases a buffer underrun may occur and eventually just:out will begin to drop video frames.
Auto Eject
If the pipeline buffer reaches a critical state and stays there for 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-infinite graphics will be automatically ejected.
Test any graphics before taking them on air to ensure they will be played out properly.
Visual Representaion of the Buffer
just:out diagnostic windowThe 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. | |
just:connect and just:live user interfaceThe 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. | |
just:play user interfaceIn the just:play user interface, the buffer status is shown in the control area, right below the master TC. |
Adjusting the sensitivity of the "Auto Eject" function
It is possible to change the sensitivity of the auto eject function. In case on air graphics keep being ejected every time you change an attribute, please → contact us to get more information how the sensitivity can be adjusted.