I did a inspection job for a client today. I recorded the videos using cockpit in BlueOS.
When i ended the recordings, some videos processed succesfully but a few videos failed to prosess. When i clicked the download button, I usally get one VLC video file and one ASS-file.
On the videos that failed to process, i did not get the ASS-file. How can I get these? It is important that i get the overlay on the videos to see depth, time, date and so on…
Hi @Jhans!
Which version of Cockpit are you running?
Hi @Jhans -
Can you also share why you’re using Cockpit lite in the browser? You’re likely to have a better experience in the future using the standalone full version!
Hi. Need to check what version it is, but I am using the Browser version.
I will try to install the desktop version. Is it any way for me to still get the .ASS-files out from yesterday?
Hi @Jhans -
It might be possible to generate a subtitle .ASS file from a vehicle .BIN log that overlaps with the mission, definitely see if you can find the corresponding log under Log Browser. This would take some fiddling with a custom python script, and could be a challenge to sync the log to the video. @rafael.lehmkuhl may have more useful insights!
Hi. Ok, i would need some help with this. I can see the cockpit browser version i used on the mission was version 1.16.0-beta.1
I have now downloaded the desktop version of cockpit and tried to download all the unprocessed video chunks from the browser version and add the zip files into the desktop version. I got some videos out of it, but none had the .ASS files with them, so they came out with no overlay on them.
Please see if there is anything more I can do to get this to work, as the client will need to have this info from the videos.
That explains the problem. This bug was fixed around December of the last year, but your version is from March.
One first thing to try: update your browser version to the latest beta version, open the video library (Video Library button on /menu/settings/video), go to the Raw tab, and download your chunk groups from there. There’s a chance the .ass files will come in the zip, if they were generated but not registered.
There’s a good chance that will solve the problem, but if it doesn’t, we can process with a custom solution to retrieve the raw .ass chunks from Cockpit’s memory (as long as you didn’t hard-erase the browser cache, they will be there).
I have opened a PR replicating the Standalone subtitle pipeline to Lite. Basically it re-generates the subtitle file from the raw logs if it doesn’t find it.
I will finish working on the PR and will send you instructions today on how to test it and find your files.
Thanks Rafael!
When can i expect the instructions?
@Jhans could you tell me which BlueOS version are you running, so I can give the correct instructions to your version?
Detailed instructions :
**Do this on the same computer and the same browser you used during the inspection. Do not clear cache, cookies, or site data.** The video chunks and the logs used to rebuild the overlay live there, not on the vehicle.
Changing the Cockpit Docker tag (or installing a custom image) is hidden until Pirate Mode is on. The Extensions store only lists published releases, and this test build is not one of those.
In the BlueOS header, click the happy robot / skull-and-crossbones icon to enable Pirate Mode.
Confirm the icon switches to the pirate/skull state.
Go to Extensions → Installed. You should now see an Edit button on Cockpit and a blue + in the bottom right.
You can turn Pirate Mode off again after the extension has updated.
The vehicle needs internet for this step (it pulls a ~28 MB image).
Open BlueOS → Extensions → Installed.
Find Cockpit and click Edit (do not add a second Cockpit with the `+` button — a new copy would be a different address and would not see yesterday’s recordings).
Leave the Docker image as `bluerobotics/cockpit`.
Change the Docker tag to:
issue-3000-regenerate-missing-ass
Save / confirm and wait until the extension finishes updating and is running again.
Open Cockpit from the BlueOS sidebar, same way as usual.
Hard-refresh the page (`Ctrl+Shift+R` on Windows/Linux, `Cmd+Shift+R` on macOS) so the browser does not keep the old JavaScript.
Check Menu → About (or the version shown in the menu). It should no longer be `1.16.0-beta.1`, but 52bb9930 from 2026-09-02.
Menu → Settings → Video → Video Library.
Open the Raw tab.
For each chunk group that previously failed / had no overlay, click Download.
What you want to see:
A ZIP download that includes both the video chunks and a `.ass` file.
Not the old red error `Failed to find .ass telemetry file for the recording.`
A yellow warning like `Downloading the chunks without a telemetry subtitle file` means the telemetry log for that time window is also gone, and that recording cannot be rebuilt from the browser.
Thank you Rafael! I was able to retreive almost all .ASS files execpt one, but i can live with that. Even though the overlay on the ones i recovered was a bit different from the ones i set up before the dive. It had the time/date and depth and that was most important for me.
Another issue I found after testing the Cockpit version 1.18.2 on the desktop was that soon as i armed the ROV the thrusters starts spinning, even it’s in Manual mode. I tried calibrating the Joystick but still no difference. When i use Qgroundcontrol, everything works fine there. What can be the issue here?
Happy to hear that it worked!
About the different overlay setup , we are going to soon add the ability to download the raw logs and regenerate the overlay as desired after the dive.
That’s super weird and was reported by two other forum users this week.
Which versions of Ardusub and BlurOS are you running?
Did you recently changed any of those two?
I am using BlueOS version 1.4.3
Ardusub Firmware version: 4.5.7 (STABLE)
I have not changed any of these two lately.
Hi @Jhans -
Have you tried a beta version of Cockpit, 1.19 +? If so, and if you’r enow using 1.18, that may be the cause of your issue…
He has tried my fix build, which contains the axes migration. It’s certainly one of the affected cases.
Tried the new Cockpit 1.18.3, and that fixed the thruster issue. I also updated to BlueOS 1.4.5.
