Skip to content
Qualia Docs

Datasets_CorrectCameraLags

POST
/v1/accounts/{account}/datasets/{dataset}:correctCameraLags
 
curl --request POST \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example:correctCameraLags \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <X-API-Key>' \
  --data '{ "name": "example", "corrections": [ { "upload": "example", "topic": "example", "stampOffsetMs": 1, "useEstimate": true } ], "requestId": "example" }'

Corrects camera stamp offsets through a recorded corrective re-ingest. Explicit offsets are desired absolute values. A trusted legacy estimate on a zero-offset channel maps to -lag_ms. FAILED_PRECONDITION on a merged dataset (QUA-3511: correct its uploads before they merge) and on an upload merged into one (naming it).

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

Request Body required

Section titled “Request Body required ”
Media type application/json

Request for Datasets.CorrectCameraLags.

object
name
required

Upload or merged dataset to correct.

string
corrections
required

Each upload in a merged dataset must be covered. Names disambiguate topics.

Array<object>

An absolute camera offset to publish through a corrective re-ingest.

object
upload
required

The upload containing this camera topic.

string
topic
required

Camera topic in this upload.

string
stampOffsetMs

Desired absolute stamp_offset_ms, not a delta.

number format: double
useEstimate

Apply a trusted estimate only when its measurement basis is known.

boolean
requestId
required

Required UUID4; retries return the same member re-ingest receipt for 24 hours.

string
Example generated
{
  "name": "example",
  "corrections": [
    {
      "upload": "example",
      "topic": "example",
      "stampOffsetMs": 1,
      "useEstimate": true
    }
  ],
  "requestId": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

The member re-ingest operation for each corrected upload.

object
reingests

Accepted operations or per-upload dispatch errors.

Array<object>

The corrective re-ingest operation started for one upload.

object
upload

Upload whose camera offset was corrected.

string
reingest

Name to poll with Datasets.GetReingest.

string
unchanged

True when the requested config was already published.

boolean
dispatchError

Non-empty when dispatch for this member failed; other members may proceed.

string
Example generated
{}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}