What do public docs say a generative background tool for LED volumes (Cuebric) outputs, and what is the .2p5d file format that Disguise uses to receive those layered 2.5D backgrounds?
Cuebric publishes no technical documentation that curl can read: cuebric.com is an Angular shell with marketing text and a four-URL sitemap (home, app login, privacy, terms). The usable public record is on the receiving side: Disguise documents a Cuebric integration (segment and dimensionise a 2D image, export a depth package) and a .2p5d container (renamed zip with data.json and per-plate image/video, optional depth map or OBJ mesh, format version 1.0.0, inverse-normalised depth with an explicit conversion formula). Cuebric capabilities such as input resolution, supported generators, accuracy of segmentation/depth and output terms are not documented in anything read; the "ready to shoot" wording is a vendor-partner claim.
Structured fields
{
"citations": [
{
"url": "https://cuebric.com/",
"note": "candidate evidence excerpts"
},
{
"url": "https://cuebric.com/sitemap.xml",
"note": "candidate evidence excerpts"
},
{
"url": "https://help.disguise.one/workflows/vp/cuebric-integration",
"note": "candidate evidence excerpts"
},
{
"url": "https://help.disguise.one/workflows/vp/2p5d-workflow",
"note": "candidate evidence excerpts"
},
{
"url": "https://developer.disguise.one/formats/2p5d/",
"note": "candidate evidence excerpts"
}
]
}Evidence claims
- [sourced_fact] Cuebric publishes no technical documentation that curl can read: cuebric.com is an Angular shell with marketing text and a four-URL sitemap (home, app login, privacy, terms). The usable public record is on the receiving side: Disguise documents a Cuebric integration (segment and dimensionise a 2D image, export a depth package) and a .2p5d container (renamed zip with data.json and per-plate image/video, optional depth map or OBJ mesh, format version 1.0.0, inverse-normalised depth with an explicit conversion formula). Cuebric capabilities such as input resolution, supported generators, accuracy of segmentation/depth and output terms are not documented in anything read; the "ready to shoot" wording is a vendor-partner claim. · locator: candidate evidence excerpts source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |