We are currently using the Ricoh Theta X to capture 8k 2fps video in construction sites using the camera’s web api. There have been a variety of different scenarios where the camera operator will start a recording, and then part way through that recording, the camera will stop recording, and the video will not be saved and show a record time of “0:00” in the file menu of the camera. One additional note is that one of our camera operators said that when this was happening today that it would make 1 beep when stopping when the battery was inside the camera, and 2 beeps when stopping recording if it was being powered via USB
What I am curious about is what are the scenarios in which a recording is completed (either deliberately or accidentally) where the camera would not save the file properly.
Things we have considered but have not worked:
Battery level: the camera had plenty of battery level and did not fully shut off in these circumstances
Available Record Time: The camera had hours of available record time
Overheating: Any time the camera has stopped due to overheating, the video has been properly saved
Firmware version: The firmware versions of the camera are completely up to date
Auto power off setting: This is turned off
Format memory: This has been done and did not solve the issue
When performing continuous shooting by operating the camera while executing <Delete object>, <Transfer firmware file>, <Install plugin> or <Uninstall plugin> with the WebAPI or MTP.
I am using the web api, and I am monitoring for some of these errors already, but I’ll take a look and see if any of the other errors might apply in this situation
are you saving the video file to the internal memory storage of the X or the removeable microSD card?
I’ll ask my contacts at RICOH if they have any ideas. I’m trying to collect information that might help to either isolate the problem or allow us to replicate it.
I went on two photo shoots with Theta X, experiencing file corruption both times with videos that were longer than 20 minutes, when attempting 25-minute 8K videos at 2fps on both occasions. Shorter videos of about 5 to 10 minutes, however, did not present this issue. Despite using the newest firmware, the problem persisted for the longer videos. Curiously, after using FFProbe to check the video errors, the files were repaired, leaving me puzzled about the cause. It seems that the issue might be related to the addition of metadata during the final save process.
Note that I don’t work for RICOH. However, I work with @jcasman and we do submit reports of community feedback to RICOH. I’ll include this information in the report.
As you mention FFProbe, I’m wondering if you’re a developer. If you are, it would be useful to get the output of /osc/state to get the error code:
