Repairing a svo2 file

Software
1

Hello good.

I have an SVO2 file recorded with a Jetson that I’m trying to repair with the “ZED SVOEditor” tool in a windows machine, but I get the following error:

(base) C:\Program Files (x86)\ZED SDK\tools>“ZED SVOEditor.exe” -repair E:\Ruben\gb2s\proyectos\CAMARIA\Data\Cantabria\1749032830\0.svo2
-repair option detected

  • Repair in progress… Please wait *
    [2025-06-05 05:57:46 UTC][ZED][WARNING] ERROR SVO 2 REPAIR: Decompression failed for chunk data starting at 1749033095226403000 and ending at 1749033095759573559
    [2025-06-05 05:57:46 UTC][ZED][WARNING] ERROR SVO 2 REPAIR: Corrupted message size at byte offset 372589220
    ** SUCCESS: SVO file has been repaired under the name: “E:\Ruben\gb2s\proyectos\CAMARIA\Data\Cantabria\1749032830\0_repaired.svo2”

The most curious thing is that, from Jetson, the file can be opened with ZED Explorer.

How could I repair this file so that it can be read on other machines? Is there another way to repair the file?

Thanks and best regards.

2

Hello Ruben,

Thank you for reaching us. Could you please run a diagnostic of your setup using the ZED_Diagnostic tool, save the generated json report and send it to us to have more details on your setup ?

Best regards,

Stereolabs Support

3

Thanks Hugo for the response.

I have a problem: I don’t have access to the Jetson file currently because it’s installed on client facilities, so it won’t be quick to do so.

I had tried this recording program many times, and sometimes closing the recording gave me problems. The resulting SVO2 file was corrupt, but it could always be fixed with the ZED_SVOEditor tool and the -repair option.
It’s related with this topic (there you can find an old diagnostic json file)

But in this case, it can’t do it and only repairs the initial part of the video. My question was more about whether there was any other way to recover that file.

4

Hello Ruben,

If you can send us your svo, it could be useful to help you to solve your issue.
Also, do you have a snippet of the code you use to record ? For the recording, please ensure to terminate safely your record by using the Camera::close() function. If your process was interrupted or not terminated properly it could affect the end of the record.

Best regards,

Stereolabs Support

5

Hi Hugo.

The svo2 file can be found here:

Yes, I terminate safely mi recording using close() method in python.

Best

6

Hello Ruben,

Thank you for the SVO file. I see that it contains 7339 frames and the duration is about 10 minutes. How long is the part of the svo you lost ? It seems to be only 500ms at the end, do you confirm this ?

Also, we are working on the recording and streaming to provide more stability. I see you are still using 4.2 sdk version, I recommend you to upgrade your sdk version to 5.0 and stay tuned for new version which will be published soon.

Best regards,

Stereolabs Support

7

Hi Hugo.

I think it could be a compatibility issue between Ubuntu and Windows computers. I have:

  • A Jetson installed in a vehicle, where I record the videos, with ZED SDK 4.2
  • My Windows laptop, where I view and analyze these videos, with ZED SDK 5.0.

Recordings on the Jetson sometimes generate SVO videos that, if I read in Windows, tell us they’re corrupt. Usually, there’s no problem because I can then repair them with SVO_Editor on my Windows computer. But that video I sent you had something else that the tool couldn’t fix. But new videos were recorded later, and I didn’t have that problem.

For your information, I think this issue related with closing recorded videos occurs when the SVO has information from captures taken in the vehicle (with movement?). It’s never happened to me in laboratory tests, even though I did a multitude of tests.

Updating the Jetson to 5.0 is not possible at this time because the equipment is in operation elsewhere and installed in a test vehicle.

Thanks Hugo!.