Recordings

A recording session includes everything related to a single recording session. Recording files, configuration files, media files, and the recording session's description.

If you head over to Recordings you will see a list of all the recordings sessions in the current project.

How-to list recordings

Console

Simply click the navigation path Recordings.

Cli

$ remotive cloud recordings list --project my-project [ | jq. ]

[
  {
    "sessionId": "13303517729834103000",
    "recordings": [
      "cycle04_chassie.zip",
      "cycle04_vehicle.zip"
    ],
    "displayName": "Turning Torso drive cycle - 2x CAN",
    "uploaded": "2023-03-09T19:38:53.373Z"
  }
]

Manage recording sessions

---

A recording session is created as soon as you upload a recording file. A broker recording session that outputs multiple recording files will belong to the same recording session.

Upload

The first recording file that you upload will create a new recording session and subsequent uploads of recording files from the same broker recording will be uploaded to the previously created recording session.

See details

Anyone in the project can access a recording session.

How-to see details

Console

Click a recording session to access the recording session details view.

Cli

$ remotive cloud recordings describe 13303517729834103000 --project my-project

{
  "sessionId": "13303517729834103000",
  "recordings": [
    {
      "fileName": "cycle04_chassie.zip",
      "displayName": "cycle04_chassie.zip",
      "metadata": {
        "database": "Model3CAN2.dbc",
        "namespace": "ChassiBus"
      },
      "sizeInBytes": 14245975
    },
    {
      "fileName": "cycle04_vehicle.zip",
      "displayName": "cycle04_vehicle.zip",
      "metadata": {
        "database": "Model3CAN.dbc",
        "namespace": "VehicleBus"
      },
      "sizeInBytes": 10561391
    }
  ],
  "displayName": "Turning Torso drive cycle - 2x CAN",
  "uploaded": "2023-03-09T19:38:53.373Z",
  "description": "## Turning Torso drivecyle\nDrive around Malmö, dockan and MINC.\n\n#### Vehicle \n\nTesla Model Y\n\n#### Collected data\n\n###### Bussses\n\n- Chassis (CAN)\n- Vehicle (CAN)\n\n###### Video\n- Front facing camera",
  "mediaFiles": [
    {
      "fileName": "Remotive-Turning-Torso_Highres.mp4",
      "displayName": "Remotive-Turning-Torso_Highres.mp4",
      "mimeType": "video/mp4",
      "sizeInBytes": 338346895,
      "startTimeZoned": "2021-09-27T18:38:00.848Z"
    },
    {
      "fileName": "Remotive-Turning-Torso_Lowres.mp4",
      "displayName": "Remotive-Turning-Torso_Lowres.mp4",
      "mimeType": "video/mp4",
      "sizeInBytes": 17787770,
      "startTimeZoned": "2021-09-27T18:38:00.848Z"
    }
  ],
  "brokerConfigurations": [
    {
      "name": "configuration_hidden",
      "files": [
        {
          "name": "configuration_hidden/PERF_STEERING_ANGLE.lua",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 495
        },
        {
          "name": "configuration_hidden/dbc/Model3CAN.dbc",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 322430
        },
        {
          "name": "configuration_hidden/interfaces.json",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 654
        },
        {
          "name": "configuration_hidden/scripts/PERF_STEERING_ANGLE_2HZ.lua",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 1375
        },
        {
          "name": "configuration_hidden/vss_mapped.json",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 406
        }
      ]
    },
    {
      "name": "configuration_model3",
      "files": [
        {
          "name": "configuration_model3/PERF_STEERING_ANGLE.lua",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 495
        },
        {
          "name": "configuration_model3/dbc/Model3CAN.dbc",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 322430
        },
        {
          "name": "configuration_model3/interfaces.json",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 604
        },
        {
          "name": "configuration_model3/scripts/PERF_STEERING_ANGLE_2HZ.lua",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 1375
        },
        {
          "name": "configuration_model3/vss_mapped.json",
          "mimeType": "application/x-www-form-urlencoded",
          "sizeInBytes": 406
        }
      ]
    }
  ]
}

Delete

Deleting a recording session will remove all recording files, configuration files, media files, and its' description from the project. A user with the right permissions can delete a recording session.

How-to delete recording

Console

Click the highlighted trash can icon to remove the recording session.

Cli

$ remotive cloud recordings delete my-recording-session \
  --project my-project

Access files

Inside a recording session you can find all files related to that recording session. Anyone in the project can view the related file

How-to guide

Console

Click the highlighted files tab to view all files related to the current recording session.

Cli

Perhaps not applicable to the CLI but you can simply use the describe command and some jq parsing to get files.

Get recording file names

$ remotive cloud recordings describe the-session-id --project turning-torso-demo \
   | jq -r '.recordings[].fileName'
cycle04_chassie.zip
cycle04_vehicle.zip

Get broker configuration names

$ remotive cloud recordings describe the-session-id --project turning-torso-demo \
   | jq -r '.brokerConfigurations[].name'
configuration_hidden
configuration_model3

Manage recording files

---

Recordings files can be uploaded by anyone in the project. Recording files are managed in the files tab of the recording session detail page.

Upload

Recordings files can be uploaded by anyone in the project.

How-to upload recording

Console

Drag and drop a recording file to the highlighted area. You can also click the drag and drop area or use the highlighted button in the top right corner to open a file selector.

Cli

Choose a valid recording file and use the upload command.

$ remotive cloud recordings upload  ~/recordings/cycle04_chassie.zip --project my-project

Due to some background processing and validation of the recording its not possible to return wether the upload was successful or not as a response. You can validate the upload by listing recordings and make sure that its valid and also listing with status processing to see if something went wrong.

$ remotive cloud recordings list --is-processing --project my-project

If something went wrong due to invalid file it can look something like this. Once in this state you need to remove the file

[
  {
    "fileName": "my-invalid-recording.zip",
    "displayName": "my-invalid-recording.zip",
    "metadata": {
      "error": true,
      "message": "(Error) invalid signature: 0x474e5089"
    },
    "sizeInBytes": 103443
  }
]

Delete

Recordings files can be uploaded deleted by a user with the right permissions.

How-to guide

Console

Click the highlighted trash can icon to remove the recording file

Cli

$ remotive cloud recordings delete-recording-file cycle04_vehicle.zip
--project my-project
--recording-session the-recording-session

Download

Recordings files can be downloaded by a user with the right permissions.

How-to guide

Console

Click the highlighted download icon to download the recording file

Cli

$ remotive cloud recordings download-recording-file cycle04_vehicle.zip
--recording-session the-recording-session
--project my-project

Manage media files

---

Media files can be uploaded by anyone in the project. We don't support all file formats, but we support the most common formats for videos, images and archives. Media files are managed in the files tab of the recording session detail page.

Media files are not yet supported in CLI.

Upload

How-to guide

Drag and drop or click the drag and drop area to upload a media file

Delete

How-to guide

Click the highlighted trash can icon to remove the media file

Manage configurations files

---

Configuration files are used to modify a recording's signal output without modifying the actual recorded data. Configuration files are managed in the files tab of the recording session detail page.

Upload

Configuration files can be uploaded by anyone in the project. We don't support all file formats, but we support the most common formats for videos, images and archives.

How-to guide

Drag and drop or click the drag and drop area to upload a configuration file.

Not yet supported in CLI

Delete

Configuration files can be deleted by a user with the righ permissions.

How-to guide

Console

Click the highlighted trash can icon to remove the configuration file

Cli

$ remotive cloud recordings delete-configuration configuration_hidden
--recording-session the-recording-session
--project my-project

Download

Configuration directory can be downloaded as zip file

Details

Console

Click the download button next to the delete button on the configuration directory

Cli

$ remotive cloud recordings download-configuration configuration-hidden
--recording-session the-recording-session
--project my-project

Play a recording session

---

When you play a recording, we upload all the recordings files togehter with a configuration to a cloud broker. The broker will by default be your personal broker for the current project.

Play - with default settings

By pressing play, the recording will start with default settings.

For CLI - checkout "Play on specific broker"

How-to guide

Simply press the play button.

Play - on a specific broker

You can optionally select another broker to play the recording on.

How-to guide

Console

Step 1

Press the arrow on the left side of the play button.

Step 2

Select the broker you want to use in the dropdown menu.

Cli

Creates a broker my-broker if it does not already exist and plays the default configuration on that broker.

$ remotive cloud recordings play 13303517729834103000 \ --broker my-broker
--project my-project
[--ensure-broker-started]

Play - with custom configuration

You can optionally select another configuration, e.g. when working with VSS or AAOS.

How-to guide

Console

Step 1

Change the selected configuration file in the highlighted area.

Step 2

Simply press play, or, select a specific broker.

Cli

Creates a broker my-broker if it does not already exist and plays the specified custom configuration on that broker.

$ remotive cloud recordings play 13303517729834103000 \ --broker my-broker
--project my-project
--broker-config-name configuration-vss
[--ensure-broker-started]