Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Task family

Stereo Glass Etching and Glassblowing Data

Masking glass and revealing a design, or gathering molten glass on a pipe, blowing it, shaping it with tools and transferring it to anneal: these are slow, fragile, hands-and-tools tasks in a glass studio. This page covers the stereo and container side of glassblowing robot training data for the two catalog rows that name this work: what a calibrated stereo pair adds to stereo glass etching video, what MCAP is according to its own documentation, and what the site does not state. We run custom studio craft data collection fast and on demand against a spec you write, through custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog rows
Two, in Glass & Mosaic Studio
Status
Medium and Hard, both Available on request, as the catalog lists them
Container
MCAP (.mcap), open source
License
Perpetual, buyer-owned

Why stereo and MCAP here

What do a stereo pair and an MCAP file add to glass etching and glassblowing video?

01

Depth around a pipe, a piece and a design

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair. A pipe, a gathered piece and the tools that shape it sit at different distances from the head camera, and depth helps separate them.

02

Hands behind the piece, flagged when hidden

Pieces are small and are often hidden by the fingers that hold them. 3D hand pose with a visibility flag per joint says which joints were seen and which were not, rather than guessing silently.

03

Two different task shapes on one scoped order

Etching is a masked, stepwise surface job. Glassblowing is a continuous sequence at the pipe. Both sit in one catalog environment, so one written spec can carry both, with each sequence defined and labelled separately.

04

One open container for several timestamped streams

MCAP stores multiple channels of timestamped, pre-serialized data with schemas alongside, so stereo, hand pose and IMU can sit in one file. Topic names and layout are agreed in the skill spec.

05

Rights you can ship on

A perpetual, buyer-owned commercial license backed by a documented consent chain, so a policy trained on the data can go into a product.

Why it matters

What is stereo glass etching and glassblowing data, and why does it need its own page?

Stereo glass etching and glassblowing data is real-world, first-person video of a person doing the work the catalog rows describe: masking the glass, applying etching cream or using a rotary tool and rinsing to reveal a design, and gathering molten glass on the pipe, blowing and shaping it with tools and transferring it to anneal. The stereo side means that, where a stereo pair is agreed in the spec, two calibrated cameras record the view. The container side means the files can be packaged as MCAP.

The work is a demanding test for a manipulation policy. Pieces are small, the steps are sequential and the hands do most of the work with tools that hide the fingers. A mask has to cover the right area before anything is applied, and a gathered piece has to be turned and shaped in order. Those are the situations where depth and hand pose help most.

The site already has an egocentric glass and mosaic page covering all four studio rows, and a stereo glass cutting and forming page covering five glass rows across two environments. This page does something narrower: it treats glass etching and glassblowing as one stereo and MCAP order, built on two rows that live in one catalog environment.

Catalog rows

Which catalog rows cover glass etching and glassblowing?

The site lists two rows in its Glass & Mosaic Studio environment, in the Creative Workshops & Crafts sector. "Glass etching" reads "Mask the glass, apply etching cream or use a rotary tool and rinse to reveal the design." and is rated Medium. "Glassblowing" reads "Gather molten glass on the pipe, blow and shape it with tools and transfer it to anneal." and is rated Hard.

Both rows list their capture mode as Phone (head-mounted) / multiview rig, and both are listed as Available on request. The environment lists its examples as "Glassblowing studio, stained glass, mosaic tiling, glass etching", and it holds two further rows, mosaic tiling and stained glass assembly, which this page does not claim.

The site names no tool, equipment model, glass type, thickness, temperature or etchant brand for these rows, so those details are agreed in the written spec.

Status

What does Available on request mean for these rows?

The site defines Available on request plainly: the work is scoped and recruited to spec when a buyer asks. It is not the same as Ready to deploy, where contributors and site access are already set up, and it is not Active collection, where recording is already running and a spec can join an existing stream.

That means recruitment comes first for a glass etching or glassblowing order, and the timeline is quoted against your spec. The site does not state a volume, a number of studios or a number of hours for either row, and none are claimed here.

The site lists no off-the-shelf glass dataset, so this work is custom collection.

Glass etching

What does the glass etching half involve?

The row describes a short chain: mask the glass, apply etching cream or use a rotary tool, and rinse to reveal the design. An episode can cover the whole chain or isolate one part of it, for example only the masking, or only the rinse.

The row offers two routes to the same result, etching cream or a rotary tool, and a spec can ask for one or both. The site gives no mask material, no cream or tool model, no design, no number of pieces per episode and no task time for this row. It also gives no chemical details and no handling instruction beyond the wording of the row, and this page adds none.

The site rates the row Medium. How a design is chosen, where the mask goes and where an episode begins and ends are agreed in the spec rather than assumed.

Glassblowing

What does the glassblowing half involve?

The row describes a longer sequence: gather molten glass on the pipe, blow and shape it with tools, and transfer it to anneal. The catalog rates it Hard, and it is the more demanding of the two rows.

The site states no temperatures, anneal times, glass types, tool models or piece sizes for this row. It also lists no thermal stream, so a stereo glassblowing episode carries no temperature reading unless a spec sets one up. This page gives no instruction for working with hot glass beyond the wording of the row.

How the sequence is cut into episodes, what counts as a finished piece and how the transfer to anneal is framed are agreed in the written spec.

One order

Why capture glass etching and glassblowing together?

They share an environment, a capture mode and a status, and they share a setting: a glass studio where one person works one piece with hand tools. A buyer building a studio craft policy often wants both a surface skill and a shaping skill, and a single spec keeps the vocabulary, the accept criteria and the delivery format the same across them.

Keeping the two sequences separate matters just as much. Etching ends with a design revealed on a piece. Glassblowing ends with a shaped piece transferred to anneal. A spec can ask for them as two episode types, with action segments marking where each step starts and ends.

The site does not state that any episode combines the two, so how often each appears is set in the spec.

Stereo

Is this data captured in stereo?

Not on the rows as listed. The catalog names a head-mounted phone or multiview rig as the capture mode for both, and stereo applies only through the site general stereo offer: a stereo pair is agreed in the skill spec and confirmed on a Spec Pilot. This page claims no delivered stereo footage of glass etching or glassblowing.

The stereo head rig, off-the-shelf dataset 06, is listed with dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output, shipped as MCAP. It is a rig the site describes, and the site does not state that it was used to record these two rows.

If you want a stereo pair for this work, say so in the spec and confirm it on the Spec Pilot batch. If a head-mounted phone or a multiview rig is enough, the egocentric glass and mosaic page describes that capture directly.

What stereo adds

What would a stereo pair add to this work?

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, and that stereo collection lists stereo RGB, depth, IMU and audio, with calibration measured every session and shipped with the episode. For etching that means the piece, the mask, the tool and the hands sit in the same depth frame.

For glassblowing it means the pipe, the gathered piece and the shaping tool can be separated by distance as well as by colour. A policy that has to decide where a tool meets a piece benefits from knowing how far apart they are, not only what they look like.

The site does not state a depth accuracy figure, a working distance or a resolution specific to these rows. Hand pose is stated as 21 joints per hand with a per-joint visibility flag, and the cross-stream sync ceiling is stated as 2.0 ms on one hardware clock.

Hard cases

What goes wrong when you record glass in stereo?

Hands are the first risk. Pieces are small and are often hidden by the fingers that hold them, and a pipe or tool can hide the part being worked. The visibility flag on each joint is the answer the site gives, contact events mark when a hand meets an item, and masks are recorded per frame.

Surfaces are the second. The site states that wet and reflective surfaces degrade active-stereo depth and that depth confidence maps mask low-confidence regions. How a transparent or reflective piece behaves in depth is not stated, and an etching order in particular should expect that and check it on a Spec Pilot.

Heat is the third. The site notes that no thermal stream is listed, which matters for a row that works with molten glass, and force and tactile readings are not among the listed streams either. Calibration is the fourth, measured at the start and end of every session.

Capture setup

What does the capture setup look like, and what is not stated?

The catalog lists one capture mode for both rows: a head-mounted phone with a multiview rig. That is a first-person view of real work, with a multiview rig adding synchronized third-person angles when the spec asks for them, and wrist cameras giving a closer view of the hands.

The site also states that Firsthand does not capture at a customer facility, and it does not say which glass studio a given program uses. The studio and the contributors are agreed in the skill spec before capture begins.

The site describes two stereo setups, a hard-environments stack and the dataset 06 rig, and does not say which one a glass order uses. The capture table below sets what is stated beside what is not.

MCAP

What is MCAP, per its own documentation?

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, as described at mcap.dev.

The MCAP specification states that a Message record carries a channel ID, a log time, a publish time and the data, with timestamps as uint64 nanoseconds since a user-understood epoch. It names calibration data as an example of an attachment. The foxglove/mcap repository lists reader and writer libraries for C++, Go, Python, Rust, Swift and TypeScript, plus a command-line tool, under an MIT license that belongs to the MCAP project, not to a Firsthand delivery.

Firsthand is not affiliated with Foxglove or the MCAP maintainers. The facts about MCAP on this page come from mcap.dev and the foxglove/mcap repository, linked in the sources.

MCAP streams

Which Firsthand streams can ship in an MCAP delivery?

For dataset 06 the site states a calibrated stereo head rig with hand-tracking output and a 9-axis IMU, shipped as MCAP. Site-wide, hand pose is 21 joints per hand with a per-joint visibility flag, and stereo collection lists stereo RGB, depth, IMU and audio with calibration shipped with the episode.

What is not stated is which of those streams are channels in an MCAP file for a glass etching or glassblowing order, how they are named, or at what rate. Depth, wrist cameras, action segments, contact events and masks are all in that category. If a stream matters to you, name it in the skill spec and confirm it on a Spec Pilot batch rather than assuming it.

The stream map below sets out what the site states and what it leaves to the spec. No topic names, schemas or rates are claimed on this page.

Streams and labels

What does each episode contain?

Each attempt is delivered as one episode, following the episode schema used across Firsthand custom collections: 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. Each episode carries one task instruction, and per-frame instance masks are stored at the depth resolution of 848×480.

Action segments divide an episode into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun. For this work, a segment might be one etch, as written in the skill spec. The site lists no label for the outcome of a step, such as whether a design came out clean.

Object labels use the terms your spec sets, so labels follow the vocabulary your training stack expects rather than a generic taxonomy.

Not stated

Which values does the site not state for these rows?

Glass types and thicknesses, temperatures, anneal times, etchant or cream details, tool and equipment models, studio types and sizes, task times, throughput, force or tactile data, thermal readings, a task-completion label and any success rate are not stated anywhere on the site for these rows.

If your policy needs any of them, they are defined in the written spec as annotation depth, and the quote covers them before capture begins. This page does not promise them by default, and it names no tool, product or chemical brand.

Neighbouring pages

How is this different from the glass and mosaic, glass cutting and forming and glass manufacturing pages?

The egocentric glass and mosaic page covers all four studio rows as first-person craft video, including mosaic tiling and stained glass assembly. Glass etching and glassblowing are two of its four rows, not its subject.

The stereo glass cutting and forming page covers five rows, one in Heavy Industry & Fabrication and four in the studio, treating glass handling as the main topic. The egocentric glass manufacturing page covers the one heavy industry row. The stereo window and glass cleaning page covers a cleaning row that uses applicators and squeegees on glass.

None of them makes etching and glassblowing its main topic. The comparison table below sets each against this page.

Privacy

How is contributor privacy handled?

Every contributor signs a written release before capture, and each delivered episode links to that record through a documented consent chain. Contributors are paid and consented, and footage that cannot be de-identified is discarded rather than shipped.

At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.

Whether finished pieces or original designs are blurred or protected beyond the license is not stated. Safety certifications, protective equipment and injury handling for glass work are not stated either, and this page makes no such claim. None of this is legal advice, and the executed agreement controls.

Delivery

How is the data labeled and delivered?

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd, and a custom order can be packaged as MCAP. The first three are training-loader formats, HDF5 and zarr carry arrays for custom pipelines, and Rerun .rrd gives a multi-stream synchronized playback file for review. The format table below sets each against its official documentation where it was read.

MCAP is a container for timestamped log data, not a training format. If your training loop expects RLDS, LeRobot or WebDataset, name that format in the spec alongside MCAP. The site does not say that an MCAP file is exported from the same canonical episodes as the other formats, so confirm that in the spec.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch.

Fast · on demand · at scale

How fast can a custom glass etching and glassblowing dataset be collected?

Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that timeline up front. Both rows are Available on request, so recruitment comes first and the range that applies is confirmed when the spec is quoted.

On-demand top-ups run against the same spec and accept criteria after each training run, so new data stays consistent with what you already hold. The site does not state a batch size or a later-batch turnaround, so those are quoted against your spec.

This is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states no provider counts, hours or throughput for this task, and none are claimed here.

The spec

How do you start a pilot?

You describe the etching and glassblowing sequences your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price against that document before any capture begins.

A Spec Pilot, a small and fast first batch, can prove the spec, the stereo pair and the accept criteria before you scale volume. The collection runs through the same seven-stage end-to-end custom collection pipeline as every Firsthand program: contributor recruiting, capture, per-batch QA, anonymization and licensed delivery. Billing is per validated hour, a reject log ships with every batch, and rejected items are recaptured at our cost.

Rights

How is the data licensed?

Every custom collection ships under a perpetual, buyer-owned commercial license, and exclusivity is available so the data is never resold. The license is documented alongside the consent chain, so a policy trained on the data can go into a product.

At a glance

What you get.

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

What the site states

What does the site state about glass etching and glassblowing?

Where the work appears on this site, what each place states and how this page uses it.
Where it appearsWhat the site statesUsed on this page as
Task catalog, Glass & Mosaic StudioTwo rows: glass etching (Medium) and glassblowing (Hard), both Available on requestThe stated tasks
Environment examplesGlassblowing studio, stained glass, mosaic tiling, glass etchingContext for the setting
Task catalog, same environmentTwo further rows: mosaic tiling and stained glass assemblyNeighbouring work, not claimed here
General stereo offerA stereo pair is agreed in the skill spec and confirmed on a Spec PilotHow stereo applies to these rows
Stereo head rig (06)Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAPA rig example, not stated as used for these rows
Task catalogNo temperature, anneal time, glass type, tool model or success rate is statedNot stated; scoped in the written spec

Catalog rows

Which two catalog rows does this page cover?

The two rows exactly as listed in the Glass & Mosaic Studio environment, with the catalog description, skill rating, capture mode and status.
Task familyCatalog task and descriptionSkillCapture modeStatus
EtchingGlass etching: mask the glass, apply etching cream or use a rotary tool and rinse to reveal the designMediumPhone (head-mounted) / multiview rigAvailable on request
Hot glassGlassblowing: gather molten glass on the pipe, blow and shape it with tools and transfer it to annealHardPhone (head-mounted) / multiview rigAvailable on request

Capture setup

How is this work recorded?

The capture mode named in the catalog for the two rows, and where stereo applies.
Capture modeWhat the site says it recordsWhere it applies
Phone (head-mounted) / multiview rigA head-mounted phone records the first-person view of real work; a multiview rig adds synchronized third-person angles when the spec asks for themBoth catalog rows
Head-mounted cameraKeeps the hands, the piece and the tool in frame from the viewpoint a manipulation policy acts fromAll episodes
Wrist-mounted cameraAvailable alongside the head camera for close-range detailStated as an option; per-task use set in the spec
Stereo pairApplies only through the site general stereo offer: agreed in the skill spec and confirmed on a Spec PilotNot stated on the rows
Stereo head rig (06)Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAPRig example from the off-the-shelf stereo category
Hard-environments stack4K/60 head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMUWhether a glass order uses it: not stated
Customer facilityCapture at a customer facility is not offeredStudio and contributors agreed in the spec

Streams and labels

What does each episode carry, and what is not stated?

Streams and labels the site states for Firsthand custom collections, and fields the site does not state for these rows.
ItemStatus on this siteWhy it matters here
Head and wrist RGB, depthStated; ten streams synced under 2 msKeeps the piece, the tool and the hands on one timeline
3D hand pose with per-joint visibilityStated; 21 joints per handCarries the grip on a pipe, a rotary tool or a shaping tool
Contact and grasp eventsStatedMarks when the fingers make and break contact with an item
Per-frame instance masksStated; stored at 848×480Separates the piece from the pipe, the tool and the bench
Action segmentsStated; frame-accurate, with start_ns, end_ns, verb and nounMarks masking, etching, rinsing, gathering and shaping as separate steps
Task instructionStated; one per episodeNames the sequence the episode shows
Stereo RGB, IMU, audio, calibrationStated for stereo collection; calibration measured every sessionOnly where a stereo pair is agreed in the spec
Thermal stream, force or tactile dataNot listedDefined in the spec if the policy needs them
Temperatures, anneal times, glass types, tool modelsNot statedDefined in the spec
Task-completion label, success rateNot statedNo such claim is made on this page

MCAP at a glance

What the official MCAP documentation states

Each property with what the MCAP documentation says and where it says it. These are facts about MCAP, not about a Firsthand delivery.
PropertyWhat the MCAP documentation statesOfficial source
What it isAn open source container file format for multimodal log data, with multiple channels of timestamped pre-serialized datamcap.dev
SerializationSerialization-agnostic: Protobuf, DDS (CDR), ROS, JSON and moremcap.dev
Write designRow-oriented and append-onlymcap.dev
SchemasStored alongside the datamcap.dev
Index and compressionOptional index; optional LZ4 or Zstandard chunk compressionmcap.dev
File identityExtension .mcap; registered media type application/vnd.mcapMCAP specification
Timestampslog_time and publish_time per message, uint64 nanoseconds since a user-understood epochMCAP specification
AttachmentsAuxiliary artifacts such as text, core dumps or calibration dataMCAP specification
Libraries and CLIC++, Go, Python, Rust, Swift and TypeScript; CLI to inspect, merge and split filesfoxglove/mcap on GitHub
License of the projectMIT Licensefoxglove/mcap on GitHub

Stream map

Firsthand streams and what the site states about an MCAP file

Left to right: the stream or item, what the site states about it, and what the site states about it in MCAP. Not stated means the site does not say.
Stream or itemWhat the site statesIn an MCAP delivery, as the site states it
Stereo pairDual fisheye, 1080p per eye, 62 mm baseline (dataset 06)Dataset 06 is stated as shipped as MCAP; channel layout not stated
CalibrationPer-unit (dataset 06); measured every session and shipped with the episodePlacement in the file not stated
Hand pose21 joints per hand with a per-joint visibility flag; dataset 06 lists hand-tracking outputChannel layout and joint order not stated
IMU9-axis (dataset 06)Channel layout and rate not stated
Depth and instance masksListed among stereo collection streams and the episode schemaNot stated
Wrist cameras, action segments, contact eventsListed in the site episode schemaNot stated
Topic names, schemas, encoding, ratesNot statedAgreed in the skill spec
SynchronizationHardware-triggered onto one clock; 2.0 ms cross-stream ceilingHow it maps to message times not stated

Formats

Which formats carry this data?

Delivery formats stated on the site, set against what each format official documentation states where the documentation was read.
FormatWhat the official documentation statesUsed for here
MCAPAn open source container for multimodal log data with multiple channels of timestamped pre-serialized data (mcap.dev)Multi-stream timestamped delivery, with layout set in the spec
RLDSA dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation)LeRobot dataset format and tooling
WebDatasetTar files in which files that belong together share a basename, split into numbered shards (WebDataset README)Sharded streaming for large training runs
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
Rerun .rrdStated by Firsthand onlyMulti-stream synchronized playback for review

Related pages

How is this page different from the neighbouring glass pages?

Related collection pages on this site and how their main topic differs from this one.
PageMain topicHow this page differs
Stereo glass etching and glassblowing data (this page)The two Glass & Mosaic Studio rows for glass etching and glassblowing, with stereo and MCAP framingCentres on both tasks together
Egocentric glass and mosaic craft video dataAll four Glass & Mosaic Studio rows in first-person captureEgocentric framing; mosaic tiling and stained glass are in scope there
Stereo glass cutting and forming dataFive glass rows across Heavy Industry & Fabrication and the studio, with stereo and MCAP framingGlass handling is its subject; this page covers etching and glassblowing only
Egocentric glass manufacturing dataThe one Glass manufacturing row in first-person captureIndustrial glass work, not studio etching or glassblowing
Stereo window and glass cleaning dataCleaning interior and exterior glass with applicators and squeegeesA cleaning row, not etching or shaping

Skill spec

What the skill spec fixes for this order

Spec element and where a buyer can see it in the delivery. Set per program means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
Tasks and orderWhether an episode is etching, glassblowing or both, and where each starts and endsEpisode boundaries and action segments; set per program
Pieces and toolsWhich pieces are etched or blown and which tools are in scopeObject labels; set per program
Rig and streamsHead and wrist views, a stereo pair, a second angle, hand pose and any othersThe channels you can read; confirm on the Spec Pilot
Reflective and clear piecesWhether transparent or reflective pieces are in scope and how depth is checkedSpec Pilot result; set per program
Step labelsWhether mask, etch, rinse, gather and shape are separate labelled stepsAction segments; set per program
MCAP layoutStreams in the file, topic names, encoding and calibration placementSet per program
Delivery formatHow the data is packagedMCAP alone, or beside RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd
Accept criteriaWhat passes QA, including what counts as a rejectReject log per batch
PrivacyHow people, plates and screens in frame are protectedFaces, plates and screens blurred at ingest
LicenseWho owns the datasetPerpetual, buyer-owned commercial license; exclusivity available

Example footage

What does first-person stereo capture look like?

One real clip already published on this site, shown as a format and rig example: a head-mounted stereo capture with hands in frame. It does not show glass etching or glassblowing.

egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · rig example, not a glass etching or glassblowing clip

No glass etching or glassblowing clip is published on the site, so this is the nearest stereo clip, labelled as a format example. Request a sample to see delivered files. See stereo sample page, request an egocentric data sample.

FAQ

Glassblowing robot training data, answered.

What is stereo glass etching and glassblowing data?
It is first-person video of a person etching glass and gathering, blowing and shaping molten glass. The catalog rows name a head-mounted phone or multiview rig, and a stereo pair with depth and hand pose applies where it is agreed in the spec. Firsthand collects it to a written spec and can deliver it as MCAP.
Which catalog rows cover it, and what is their status?
Two rows in Glass & Mosaic Studio: Glass etching (Medium) and Glassblowing (Hard). Both are Available on request, with a head-mounted phone or multiview rig as the capture mode.
Is the data captured in stereo?
Not on the rows as listed. Stereo applies only through the site general stereo offer, agreed in the skill spec and confirmed on a Spec Pilot, and this page claims no delivered stereo footage of these tasks.
Which MCAP topics and schemas are in the files?
Not stated on the site. Topic names, message encoding and rates are agreed in the skill spec and confirmed on a Spec Pilot batch. MCAP itself is described by its own documentation at mcap.dev.
Does the data include temperature or force readings?
Not stated. The site lists no thermal stream and no force or tactile stream, so any such reading would have to be set up in the spec. The site also states no temperatures or anneal times for the glassblowing row.
How is this different from the glass and mosaic and glass cutting and forming pages?
The glass and mosaic page covers all four studio rows in first-person capture, and the glass cutting and forming page covers five glass rows with glass handling as its subject. This page centres on glass etching and glassblowing in stereo and MCAP.
How fast can a custom dataset be collected?
Where coverage is deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, and both rows are Available on request, so recruitment comes first and a Spec Pilot can prove the spec.
What license does the data ship under?
A perpetual, buyer-owned commercial license, with exclusivity available, documented alongside the consent chain.

Sources

Where are MCAP and the delivery formats documented?

Request a custom glass etching and glassblowing dataset.

Tell us the pieces and tools, whether an episode is etching, glassblowing or both, whether clear or reflective pieces are in scope, whether you want a stereo pair, the streams you want in the file and whether MCAP sits alone or beside a training format. We will quote reach, timeline and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.