Although iVGA™ is highly efficient, it does require significant system resources, especially when a large portion of the display is refreshed.  This is not normally problematic as – for iVGA purposes – the client system is not required to perform other concurrent tasks. Its entire duties involve providing a video source for the (downstream) TriCaster via the iVGA client software.  However, it is very unwise to install and run the iVGA client software directly on a TriCaster itself.

TriCaster’s live video processing requires unhindered CPU and GPU access.  Adding the resource demands of the iVGA client to TriCaster would almost certainly cause frames to be dropped on output, and should simply never be done. The same warning applies to other ‘screen-sharing’ or ‘remote desktop’ applications, which would actually be as bad or worse.

Of course iVGA benefits from the fastest possible network connections between remote clients and TriCaster even when “used as directed”.  This is especially true if you intend to stream high resolution motion graphics to TriCaster using iVGA.


For more information please download the entire document at


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.