Straight answers about sync review, Shot Tracker, pipeline publishing, subtitles, color-critical ingest, NLE exports, native file workflows, and how teams run production collaboration in RemoteRoom.
Jump to section
What RemoteRoom is, how rooms are organized, and who it is built for.
RemoteRoom is a modular collaboration workspace for production and creative teams. It combines livestream monitoring, frame-accurate review, video calls, shared documents, whiteboarding, and file workflows in one password-protected room.
You create a room, enable the modules you need, set access permissions, and share one link. Team members move between room tabs without leaving the session, so context stays intact while you stream, review, and discuss.
RemoteRoom is designed for post-production teams, live event crews, agencies, studios, and client teams that need to collaborate on media with speed and precision.
Current modules include Livestream, Review, Calendar, Video Call, Blackboard, Playbook, Media Browser, Shot Tracker, Board, and Subtitles. Rooms are modular, so each project can run a different combination.
Calendar adds a production planner directly inside each room. Teams can plan by lane or by assigned user, create milestones, save client-facing views, and keep room and dashboard calendars in sync live.
How synced review works in real sessions.
Yes. Review rooms support synchronized playback modes, including presenter-led control when teams need strict alignment.
Yes. Zoom and pan can be synchronized so everyone inspects the same detail area during feedback and approvals.
Yes. Horizontal/vertical guides and aspect-ratio overlays can be adjusted live and shared with all viewers in sync.
Compare mode supports side-by-side, wipe, and difference views, with synchronized behavior designed for practical before/after review.
Version stacking groups iterations under one item so teams can compare cleanly without messy filename chains like final_final_v002.
How shots, tasks, dailies, metadata, and external integrations fit into RemoteRoom.
Shot Tracker adds shot status, task ownership, assignments, dailies, versions, thumbnails, todo progress, comments, and activity history inside the same room where review and media already live.
Yes. Review comments can be copied into shot context, linked to shot todo state, and viewed alongside the relevant task, version, and media so feedback turns into accountable follow-up.
Yes. Shot Tracker has external API support for uploads, sequence uploads, shots, tasks, team members, events, comments, media linking, and API keys. Team-scoped keys can target selected rooms by room ID or slug.
Yes. RemoteRoom reads promoted metadata from uploads, including rr* fields such as shot name, task name, version, status, colorspace, frame range, asset status, comments, and variants when those fields are provided.
Yes. The repo includes RemoteRoom Nuke Studio and Hiero publishing tools plus a pure Nuke ShotTracker review panel for room browsing, comments, status changes, media pulls, and dailies publishing.
Yes. Subrooms and share links can show or hide the Shot Tracker page, and owners can separately control whether viewers may create shots or change shot status and assignments.
File workflows, uploads, and quick sharing.
It is intentionally native-feeling, with icon/list/column views, familiar navigation patterns, drag-and-drop, and folder workflows.
Yes. Folder-aware drag-and-drop is supported for media workflows, including nested file handling.
DropSpot is a fast, in-room file handoff area for quick uploads and downloads, with progress feedback and real-time updates for participants.
Yes. Rooms support direct uploads, download links, and export-friendly handoff flows so teams can move assets quickly through review and delivery.
Yes. Calendar saved views can include visibility presets that hide usernames, lane names, assignees, status chips, tags, or descriptions. That makes it easier to prepare client-safe screenshots, exports, and shared room views.
How planner views, assignments, milestones, and exports work in the room calendar.
Planner view is the production-oriented overview for lane-based or user-based scheduling across days and weeks. Schedule views are the more traditional day, week, month, and agenda calendars for detailed timing.
Milestones are point-in-time markers shown with a triangle marker rather than a duration bar. Duration tasks can span multiple days and optionally skip weekends so breaks stay visible in the schedule.
Yes. Calendar items can be assigned to room team members, and planner rows can switch from lanes to users so you can see who is booked on what across the room or the all-rooms overview.
Yes. Owners can lock a subroom or share link to one or more approved saved calendar views and optionally disable search and filtering. In that locked mode, viewers can scroll, change density, and switch between allowed views without discovering filtered-out work.
Yes. Room calendars can export to print/PDF or CSV. Exports follow the active filters and visibility preset, which makes it practical to create cleaner client-facing outputs.
Ingest formats, quality targets, and color workflows.
RemoteRoom supports SRT and WHIP ingest. If your source can output one of those protocols, you can stream directly into a room.
WHIP is typically used for extremely low-latency ingest paths, while SRT is favored for stable, color-accurate remote monitoring workflows.
Yes. Video calls support high-resolution sessions up to 4K. Livestream and review workflows support 10-bit media paths, and HEVC/H.265 mode supports HDR-capable workflows on compatible browsers.
No. Reviewers and viewers join in the browser. Ingest operators can keep using existing tools that already output SRT or WHIP.
Subtitle import, editing, translation, locks, and export workflows.
Yes. The Subtitles module lets teams work with subtitle tracks tied to review media, with timeline editing, status updates, SRT import, and SRT export.
Subtitle editing uses track locks and lock heartbeats so one active editor can make changes without another person silently overwriting that work.
Yes. The current implementation includes AI-assisted transcription and translation workflows, with provider integrations for transcription and DeepL-backed translation where configured.
Yes. Subtitle access follows room, subroom, review-link, and folder write permissions, so a viewer can be allowed to see subtitles without being allowed to edit or export them.
How access, hosting, and privacy are handled.
Rooms are password-protected and support role-based access with granular viewer and presenter permissions. Communication is end-to-end encrypted.
RemoteRoom is built and operated from Hamburg, Germany, with infrastructure hosted in the EU.
Yes. Room owners can define access rules per participant so teams can separate presenters, reviewers, and viewers as needed.
No. RemoteRoom focuses on production collaboration and does not include advertising trackers in room experiences.
Delivery handoff, billing model, and beta access.
Yes. RemoteRoom exports marker-ready formats for Autodesk Flame and DaVinci Resolve, plus universal EDL/CSV formats commonly used in Premiere-oriented post workflows.
Teams can export CSV and PDF reports for broader stakeholder distribution, documentation, approval tracking, and room-calendar planning handoff.
RemoteRoom uses per-room pricing, not per-seat pricing. Team size can grow or shrink per project without multiplying user-seat costs. Billing access is being rolled out in stages, pricing is subject to change, and customer feedback is being collected.
That is the goal. Many teams use RemoteRoom to combine workflows that would otherwise be split across review apps, call tools, and file-sharing platforms.
Frame.io is strong for review. RemoteRoom includes review capabilities and combines them with livestream monitoring, calls, docs, whiteboard, and file workflows in one room context.
Zoom and Meet are call-first tools. RemoteRoom includes calling but is built around media workflows where streaming, review, approvals, and file context must happen together.
RemoteRoom is currently in private beta. Request access through the website and the team will follow up for onboarding.
Need a specific answer for your workflow?