Ricoh theta flutter SDK video start with custom name

Kalpesh_Shinde · November 14, 2024, 5:22am

Hello,

We are developing a Flutter app using the Ricoh Theta SDK along with network APIs. Is there a way to set a custom file name for the video before saving, for example, during initialization or when starting the recording?

final videoCapture = await _thetaClientFlutter
    .getVideoCaptureBuilder()
    .setMaxRecordableTime(MaxRecordableTimeEnum.time_7200)
    .setFileFormat(VideoFileFormatEnum.video_5_7K_5F)
    .setGpsTagRecording(GpsTagRecordingEnum.on)
    .build();

craig · November 20, 2024, 2:35am

I don’t think you can set the filename through the SDK prior to saving on the camera. You can do this with a plugin API. See this discussion on GitHub.

github.com/ricohapi/theta-plugin-camera-api-sample-x

Custom string with the api

opened 02:28PM - 01 Aug 24 UTC

iFieldSmart-Tech

Our use case is we have a plugin that acts as a bridge for communication between… our mobile app and the camera. For images, we call the plugin's api which has a parameter that accepts a string, the plugin calls the camera's api to take picture and once done, update the resulting image's exif data with the string received with the api. We tried the same with the video, but after the camera's stop recording api is called, it exits, we do not receive any response from the camera. The recording stops, but we do not get to update the video's exif data with the string received in the plugin's api. We also tried adding a 15-20 seconds wait, but even after waiting it does nothing, the code exits, no breakpoints are hit. Can you please help us with understanding what we are doing wrong? or any other way to pass a custom string with the start or stop recording api calls?

You can also change the name on a mobile app or embed exif data there.

Can you provide more information your use case?

For example, can you attach meta-data to the file or just associate it with another data file and then store it in the cloud?

If we know the use case, we may be able to provide more advice.

Kalpesh_Shinde · November 21, 2024, 9:44am

We are developing a 360 image extraction feature based on location, where metadata is stored after video creation. However, if the camera shuts down unexpectedly, the metadata is not saved. When recording starts, we collect the Android device’s latitude and longitude. The issue arises when the camera is restarted, and the user records a test video to check if it’s working. In such cases, the app may incorrectly link the last video with the wrong location data. Additionally, while the Android device can get a backup location, we are unable to determine which video or filename should be associated with the correct latitude and longitude.

craig · November 21, 2024, 4:24pm

https://github.com/ricohapi/theta-api-specs/blob/main/theta-web-api-v2.1/commands/camera.start_capture.md

With THETA X firmware 2.61.0, you should be able to get the _fileUrls value at the time that startCapture is executed. Previously, you could only get the _fileUrls value after the video had been recorded.

For movie shooting, the response includes _fileUrls information at the timing of camera.startCapture.
This feature is available with THETA X firmware v2.61.0 or later.

{
    "_fileUrls": [
        "http://192.168.1.1/files/100RICOH/R0011234.MP4"
    ],
    "id": "1234",
    "name": "camera.startCapture",
    "state": "done"
}

Please update your firmware to the newest THETA X firmware and advise if the above update is “good-enough” for your solution.

Firmware 2.63.0 is out. It is a bug fix. I don’t know what the bug was.

I have not checked the response from theta-client library. I don’t know if the _fileUrls is in the response. You may need to test it with Flutter http or dio package.

First, please advice if the above firmware update meets your application requirement.

craig · November 25, 2024, 6:46pm

@Kalpesh_Shinde as the previous post was marked as the solution, I’m assuming that it is OK for your application to use the filename at the beginning of startCapture. I’m assuming that you don’t need to get a custom filename.

I’m closing a discussion item i had with RICOH about the “custom filename” for the video as it appears that getting the filename for the X video at the beginning of startCapture is good-enough.