Updates / Piston Server

Organisation Camera Sharing

· Build 889

Session Sharing

  • Sharing a session now shows a Shared Cameras section for each organisation — only cameras assigned to that organisation are offered, ticked by default, and the operator can deselect any stream that must not be visible to the receiving team
  • Camera restrictions are enforced everywhere — a receiving organisation can't see or borrow a restricted stream from the web form or the API, and an organisation with no shareable cameras is skipped instead of receiving everything
  • The session page marks restricted shares with a lock badge — hover an organisation's avatar to see exactly which cameras it receives
  • Third-party integrations can restrict shares with share_camera_ids on POST /api/sessions (see API docs)

Organisations

  • The Manage Organisation modal now lists the organisation's assigned camera groups below its cameras, each section with a quick link into Settings (the Cameras link previously jumped to the wrong widget)

Cuts

  • The Video Encoder "Auto" setting now tests that a hardware encoder actually works on this machine before using it — servers whose ffmpeg lists Intel QSV without working hardware no longer produce failing cuts, and if an Auto-selected hardware encoder fails at cut time the cut automatically re-runs on the software encoder so the clip still comes out

Fixes

  • Copying a markup while in All Organisations mode (root) no longer fails — the copy is created as a global markup
  • API sign-in for an account with a blank auth token now issues a fresh token instead of returning an empty one

Control Centre

  • Signing in through a jump server no longer fails (per-instance session cookie + corrected nginx forwarding — Control Centre deploys separately from this build)