Stereo Event Staging Setup and Teardown Data

It is first-person video of a person doing the physical work of building a stage in an event room and taking it down again, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: event staging robot training data, stereo stage deck assembly video, an egocentric staging teardown dataset, or custom event-venue data collection at scale. Stereo describes the capture, and MCAP describes the container. They are separate choices.

It is room work, not event footage. Neither staging row describes a guest, an attendee or an audience, and this page does not describe capturing event guests. The data is human capture by paid, consented contributors, not robot or teleoperation data, so using it for a specific robot still needs your own retargeting step. The site states one task instruction per episode as its language data. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Two, both listed under the Event Venue environment in the Hospitality & Events sector, whose examples line reads "Conference halls, wedding venues, stages and banquet rooms." Both are rated Medium, both list "Phone (head-mounted) / multiview rig" as the capture setup, and both are Ready to deploy. The first table below reproduces them with the catalog wording.

Ready to deploy means contributors and site access are set up, and capture starts once a spec is signed. The site states no delivered hours and no delivered stereo footage for these rows, so this page claims none. Words such as platforms, hand trucks, stage decks, equipment and lighting are catalog wording for item types, not models, and no brand is named.

The stereo event venue setup and AV cable taping page is the stereo and MCAP treatment of all eight Event Venue rows: staging, AV cables, table and chair layout and venue sweeping. Staging is one section of it, and it does not cover staging in depth. The egocentric event venue setup and teardown page covers the same eight rows as first-person video that is not stereo as its subject, and its main topic is general venue setup.

The egocentric AV cable management and taping page covers the two cable rows, so its tape runs along a cable. This page is the stereo treatment of the two staging rows alone. It does not repeat the layout, cable or sweep rows, and the second table below sets the pages side by side.

The catalog lists "Phone (head-mounted) / multiview rig" for both rows. The site does not state a stereo pair for either of them. Stereo applies through the general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. Camera count, resolution and frame rate for staging work are Not stated.

The site describes two stereo setups and does not say which one an order for these rows uses. The hard-environments stack is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output. On the rig tier every stream is hardware-triggered onto one PTP clock domain, and calibration is solved before capture starts and after it ends.

"Set up and tear down staging using folding platforms and hand trucks" is rated Medium and described as carrying staging platforms in on hand trucks, locking them together, then dismantling and stacking them. The catalog names three actions in the build, carrying, locking and positioning by implication, and two in the reverse, dismantling and stacking.

A spec that says "set up the stage" gives one long segment. A spec that names carrying, locking, dismantling and stacking as separate steps gives a sequence you can slice. Whether setup and teardown are one episode or two is a spec decision. The site states no platform size, deck count, load rating or locking mechanism, and two-person carries are named only as a warehouse skill on the site, so none is stated for this row.

"Stage & Equipment Setup / Teardown" is rated Medium and described as assembling stage decks, setting up equipment and lighting, then tearing down and packing after the event. It adds two things the platform row does not name: equipment and lighting, and packing at the end.

The catalog does not say which equipment is set up, how the lighting is mounted or what the packing involves. The site states no equipment list, no rigging method and no packing order, so a spec should say which items an episode covers and where packing begins. This page makes no stage-engineering, rigging, lifting or electrical safety claim.

In stereo, the same items are seen going up and coming down, and the depth stream records how a platform sits against its neighbour when it is locked. The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, and that the pair is calibrated per unit, so the platform, the floor and both hands are in one three-dimensional record.

The site states no depth accuracy figure for staging, and it states that depth degrades on wet and reflective surfaces. Whether a polished deck surface, a metal edge or a lit area counts as reflective is Not stated, so this page promises no depth figure. If depth matters to your policy, say so in the spec and check it on the Spec Pilot batch.

Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. For staging, hand pose tracks how the fingers lift, steer and release each platform, contact events mark when a hand or a hand truck meets a surface, and action segments mark each step.

Object labels use the terms your spec sets. Venue, event and client names, equipment makes, load ratings, setup times, force or tactile data and a stage-complete label are Not stated. They are defined in the spec if your policy needs them. The fourth table below sets each stream beside what the site states.

The site states that the hands occlude the work and that fingers disappear behind objects. That is why each hand joint carries a visibility flag, why contact events mark when a hand or a tool meets a surface, and why instance masks are recorded per frame. A platform carried against the chest or locked at floor level can hide the hands that hold it.

The site does not say how often a platform or a deck leaves the view for these rows, so that is Not stated. A spec that needs a clear view of a step, such as the moment two platforms lock, should name that step, ask for wrist views or a multiview angle and confirm it on a Spec Pilot.

Hand occlusion is the first risk, under the visibility flag above. Large items leaving the frame are the second, and how often that happens is Not stated. Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for the manipulated object out of frame for more than 15 percent of the episode, for more than 35 percent of depth pixels in the manipulation region being invalid, for an undocumented bystander or for a mismatch against the named skill spec.

A reject log ships with every batch, and rejected items are recaptured at the provider cost. The fifth table below lists the failure modes beside what the site states.

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For these rows the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch.

The site states a consent chain for contributors. Every contributor signs a written release, each delivered episode links to it through consent artefact IDs, and a break at any of the six checkpoints discards the footage. An undocumented bystander is a stated reject criterion. For every delivered episode the site states that faces, plates and screens are detected and irreversibly blurred at ingest, that a reviewer confirms the result before anything ships, and that footage that cannot be de-identified is discarded.

The site states no venue-specific bystander rule, so how people who are present are handled is settled in the spec. Attendance, capacity and PPE rules are Not stated. The site names no venue, operator, event or region for these rows. This is not legal advice, and the executed agreement controls.

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. None of them names event staging, so for stereo capture of these tasks this is custom collection, not an off-the-shelf purchase. Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which applies to staging, so the timeline is quoted against your spec.

This is custom event-venue data collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. On-demand top-ups run against the same spec and accept criteria after each training run. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe where each task starts and ends: platforms carried in and locked, a stage built and struck, equipment and lighting set up, or a teardown from the first dismantled piece to the last packed one. Say whether an episode covers one step, one stage or the whole build and its reverse, what counts as locked or packed, the setting and lighting, and the privacy rule for the room.

Then name the streams you want in the file, the topic naming and message encoding your reader expects, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset. Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The sixth table below shows what each spec element decides.