Components of Pixotope
Main services | |
---|---|
Asset Hub | Asset management system to automatically synchronize files between connected machines. |
Control Panel | Interface to create custom control panels |
Chroma Keyer | The best-in-class real-time chroma keyer |
Data Hub | Extremely low-latency data bus which handles the communication between all Pixotope services. It includes an API that makes it easy to integrate multi-camera workflows (including MOS workflows), custom control panels, DMX light control and GPI. |
Data Mapper | Data Mapper allows to link external sources to any destination inside Pixotope |
Diagnostics | Service to monitor CPU, GPU and other hardware |
Director | Main user interface controlling all machines in a Pixotope network, in real time |
Editor | Intuitive, “What You See Is What You Get” workflow editor for level layout, lighting, VFX, animation and compositing, permitting the import of digital assets from all standard content creation tools, like Autodesk Maya and Cinema 4D |
Engine | Photorealistic real-time renderer using the Unreal Render engine |
Lens File Editor | Visualize and edit lens file data manually |
Plotter | Inspect and export, API values and incoming tracking data |
Tracking Service | Connecting Pixotope with the major real-time camera and object tracking systems |
VideoIO | GPU-based video processing pipeline |
Cloud solution for release, license and user management |
Other services | |
Daemon | Backend service responsible for starting all other services and storing machine related information |
Encryption | Backend service handling network encyrption |
Gateway | Backend service to relay HTTP requests to Data Hub and to respond with meaningful data when it makes sense |
License | Backend service which handles the communication to the Pixotope Cloud |
NetworkDiscovery | Backend service used for discovering other Pixotope machines |
QueryServer | Backend service which allows to run queries and combine data through relays |
Store | Backend service which stores show related data |
SysBridge | Backend service which allows system level operations |
WebHost | Backend service required for running Director in the browser |
ZMQProxy | Backend service which handles communication between ZMQ and Director |