# Video recording not working

**URL:** <https://discuss.bluerobotics.com/t/video-recording-not-working/11831>\
**Category:** Blue Robotics Vehicles\
**Created:** [March 28, 2022, 8:11pm UTC](https://discuss.bluerobotics.com/t/video-recording-not-working/11831 "2022-03-28T20:11:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephenmcgovarin](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@stephenmcgovarin](https://discuss.bluerobotics.com/u/stephenmcgovarin)\
**Post date:** [March 28, 2022, 8:11pm UTC](https://discuss.bluerobotics.com/t/video-recording-not-working/11831/1 "2022-03-28T20:11:43Z")

</div>

Hello,

I am having some trouble making the video work for BlueROV2. I followed the previous threads ([Parameters from firmware are missing](https://discuss.bluerobotics.com/t/parameters-from-firmware-are-missing/9746)) and ([Troubleshooting · GitBook](https://www.ardusub.com/reference/troubleshooting.html)) but I am unable to resolve the issue. Could it be related to the missing parameters warning as shown in the picture?

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/244aeb64aaa784790529f79c2351d53461eb0ac6.png)

Thank you!

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [March 29, 2022, 4:31am UTC](https://discuss.bluerobotics.com/t/video-recording-not-working/11831/2 "2022-03-29T04:31:25Z")

</div>

Hi @stephenmcgovarin, welcome to the forum 🙂

> [@stephenmcgovarin](#):
>
> Could it be related to the missing parameters warning as shown in the picture?

Video functionality is unrelated to the autopilot telemetry and parameters - it’s handled by the onboard/Companion computer. Which versions of QGroundControl and Companion/BlueOS are you using? 🙂

If you’re using Companion (the default, unless you’ve changed it yourself) then can you confirm that the camera appears in the Detected Devices on the [System](https://www.ardusub.com/reference/companion/system.html) page of the web interface?

If you’re using BlueOS, we found an issue earlier today when using BlueOS with QGroundControl 4.1.6 which [should be fixed soon](https://github.com/mavlink/qgroundcontrol/pull/10228).

---

<div class="post-metadata">

**Author:** ![stephenmcgovarin](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@stephenmcgovarin](https://discuss.bluerobotics.com/u/stephenmcgovarin)\
**Post date:** [March 29, 2022, 2:34pm UTC](https://discuss.bluerobotics.com/t/video-recording-not-working/11831/3 "2022-03-29T14:34:47Z")

</div>

Hi Eliot,

Thank you for your response and for welcoming me to the forum! I was able to see a previous thread that you resolved. I had installed the QGC 4.1 which apparently doesn’t allow the camera to work on macs. I downloaded a previous version (4.0) and the camera is now working!!

Thank you!

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [March 30, 2022, 4:42am UTC](https://discuss.bluerobotics.com/t/video-recording-not-working/11831/4 "2022-03-30T04:42:55Z")

</div>

> [@stephenmcgovarin](#):
>
> I had installed the QGC 4.1 which apparently doesn’t allow the camera to work on macs.

Mac video support was added in QGC 4.1.6, which is our [latest recommended version](https://bluerobotics.com/learn/technical-reference/#software-and-firmware) (for all operating systems). 4.1.6 seems to have an issue specifically with video _recording_ when used with BlueOS, which as per my previous comment

> [@EliotBR](#):
>
> [should be fixed soon](https://github.com/mavlink/qgroundcontrol/pull/10228)

If you’re having an issue with video display (or just recording if you’re on Companion) in QGC v4.1.6, when 4.0 is working, then that’s something we’d like to hear more about because it shouldn’t be the case.

It’s at least good that you’ve got a workaround available for your issue(s) for now 🙂
