If it is I have problems when I down load that newer version, my video freezes, i keep loosing vehicle connection , but with the v1.16 version all streaming etc works great , but it will not process videos of over 15-20 mins which is very frustrating when doing a mission,
I get these folders when i hit the processing tab, I have clicked on all folders but, all failed to do anything or process;
FYI, the MFF folder is all the video chunks that failed to process yesterday , so I copied them and saved to a folder on my desktop as back up
Hi @Mac1 -
You can find the beta18 under releases on the cockpit GitHub.
On the raw tab, you should be able to download the chunks as zip files grouped by video, from what is present in the video chunks folder. That zip can be dropped on processing tab to get the video!
Hello Tony
Hello Tony can you send me a download link so that i am sure that I am downloading the latest version, as I have been back and fore trying to get cockpit working correctly since the begining of dec,
I thought it was working ok until I tried to record longer than 15-20 mins video thanks appreciate, as I cannot understand why I am getting so many issues with working with Cockpit , if everyone else is working with it with out a problem , as i mentioned already to your I bought a new electronics enclosure just 6 months ago, a new FTI surface box 3 months ago , so I am not sure what the issue can be with my system :-/
This was the one I tried downloading , but I get issues of freezing, stalling and vehicle disconnecting
should I try installing windows 11 ? would that make a difference to cockpit ?
Hello, its getting late on my side now, if you could please give me us much information as possible I will then work on it tomorrow.
maybe if possible I could schedule an online meeting with someone tomorrow to see if we can resolve this occurring issue with my system , that would be appreciated , as I still have a pending survey that will require the use of two cameras and recordings of as long as possible (maybe 1-2 hrs )
Hi @Mac1-
From the previous issues you’ve had, I’d guess the root cause for video and connection issues on your system is your tether- new electronics and FXTI rule other things out. Have you installed the tether diagnostic extension? Screenshots of it’s results would be helpful in troubleshooting. They can be interpreted with the information in the extension documentation.
You can find all Cockpit releases here.
Your system looks sufficient to run Cockpit, the windows version should not impact anything.
The dashcam extension may help ensure you get quality video without issues from tether communications, as it records onboard the vehicle. These recordings would not have the subtle files cockpit generates.
Try this and let us know how it goes!
Hello Tony, I have just been in an online meeting with Rafael, he has gone through my system and all cockpit versions. he will explain better to you what he thinks the issues are , instead of me getting it wrong 
thanks
@tony-white I made a call with @Mac1 on Monday to see the problem by myself. As he was reporting a worse performance on v1.17 with respect to v1.16 I wanted to understand if we could have introduced something unaware.
On our tests we found out that indeed 1.17 induces about 15% more of CPU usage, and as Murdo’s topside computer was already on its limits with 1.16, this increase that happened in 1.17 was enough to cause CPU topping, consequently causing Cockpit to run slower, inducing telemetry disconnections and lag in the video decoding (this last was made worse by the fact that the computer had no dedicated video, with the integrated video having only 128MB).
I opened an issue about that with some info I’ve collected during the call and I’m investigating what can have caused that. I have already opened 4 PRs around performance improvements on different parts of the application that changed between 1.16 and 1.17 and will ask Murdo to test it in the next weeks. In the meantime I recommended an upgraded configuration so he can have an easier life, specially if trying to use 4K cameras and sonar (his ROV has a Ping1D) in the future. The recommendation around topside configuration can be found below:
Our recommendation, for you to have a machine that works today and that will work as well if you upgrade your cameras and attach sonars at some point would be the following:
- i7 from the 12th generation or above (not from the energy-efficiency series) (i7-12770H for example)
- Dedicated video card or a motherboard with a Vega integrated video-card or equivalent
- 16GB of RAM
That machine will be future-proof for you.
If you’re aiming for the minimum requirements, we would recommend at least:
- i5-1135G7 (this is from the 11th generation, which includes a decent integrated video-card)
- 8GB of RAM (although going to 16GB is very cheap and with only 8GB you cannot run other applications like SonarView or Chrome in parallel to Cockpit)
1 Like
Thanks for the PC specs. For Apple users, would an M4 Mac Mini suffice?
Hi @k-deboer -
Absolutely! I use an M4 air and it runs great - generally any Mac using an M series chip, (2020 onwards) can handle things quite well.
Perfect Tony!
I will add here that I develop Cockpit using a Mac Air M3 with 16GB of RAM, having 2 cameras (one 1080p and one 4K) connected all the time, so you can expect that any configuration above that will always be enough.
Thanks @rafael.lehmkuhl and @tony-white,
I just picked up a new M4 Mini: 24GB RAM/512GB SSD. Now to load everything. I’ll be running Cockpit, DWE Discovery Desktop for 3 DWE cameras, and Panasonic Lumix Tether for the 4/6K cinema camera. Although the Intel NUC i7 handled these, there were signs of it struggling. Similar to the issues in this thread.
This will be a great winter’s storm project this weekend! Arg.
1 Like
Hi @k-deboer -
Is there a reason you’re using that DWE discovery software? You should be able to add the camera streams normally in BlueOS, and have them all arrive in Cockpit. You can adjust the bitrate via the DWE OS BlueOS extension…
That M4 Mini should have no issues at all!
I must say, I’m super impressed in the way that the Cockpit software installed, and came up looking exactly how it was on the PC. I expected to have to redo all of the joystick mapping, and screen layout. Well done BR team!
@tony-white , I was running the DWE Discovery on a second screen with the three DWE cameras connected to a second RPi running DWE OS which is on the same vehicle LAN network. I did this mainly to give some redundancy on the video streams, and to offload some strain on the Navigator RPi. But as I’m having difficulties getting the DWE Discovery app running on this new Mac, I may have to visit your idea of displaying the extra cameras in Cockpit. I tried setting a redirect source as one of the streams from the DWE OS, but it failed to run. Question: Is it possible to add the streams from the DWE OS machine into the BlueOS Video manager?
2 Likes