How Pixelview Works ​

You do not need to know any of this to run a session. It is here for the curious, and for the IT and security people who ask.

Your suiteYour session's serverEach viewer

Your session gets its own server ​

When a project is active, Pixelview runs a dedicated server for your encoder, not shared with other customers. It receives your stream, prepares it for each viewer, and sends it on.

You choose the region where it runs. The one closest to you and your viewers gives the least delay. Changing region takes about a minute. See Region and Server Settings.

What the server does with your picture ​

  • Delivers it with low delay, so you can talk about the picture while watching it.
  • Keeps the quality you send, including 10-bit color, and carries the color information viewers' devices need to show it correctly.
  • Applies the watermark with each viewer's name, if you turn that on.
  • Applies a 3D LUT, if you use one. See 3D LUT Calibration.
  • Makes the thumbnail you see in Admin and viewers see in the apps.
  • Measures each viewer's connection, so you can see in Admin who has a problem and why.

Streams are passed through live. They are not recorded or stored as part of a normal session.

Color ​

Tell Pixelview what you are sending under Settings in Admin: Rec.709 for normal SDR work, or one of the HDR beta profiles. Test HDR with your real source, capture path, and the viewer's actual device before a client session. See Color Settings and HDR Remote Review.

If something looks wrong ​

  1. Check that your app or encoder is still streaming.
  2. Look at the viewer's stats in Admin. See Viewer Management.
  3. Restart the server from Admin.
  4. Try a closer region.
  5. Check your streaming settings against the setup guide.