# Heads up regarding ffmpeg processing BlackVue videos from Debian Bookworm/Deb-multimedia

**URL:** <https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577>\
**Category:** Command line tools\
**Created:** [November 19, 2023, 3:47am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577 "2023-11-19T03:47:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [November 19, 2023, 3:47am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/1 "2023-11-19T03:47:51Z")

</div>

I have not run this completely to ground, but it appears that the latest deb-multimedia 10:6.0.1 now fails with a header error trying to decode frames from a BlackVue DR900S camera. eg;

[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55e6a7a762c0] error reading header  
20231119\_115953\_NF.mp4: Invalid data found when processing input

So if I try to run the tools locally it may fail. (I upload the mp4’s direct though)

If anyone knows a way to ignore the error would you please advise as I use frames for local OSM work

---

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [November 20, 2023, 1:36am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/2 "2023-11-20T01:36:02Z")

</div>

Note, downgrading back from 10:6.0.1 to 10:6.0 (dpkg install) versions in /var/cache/apt was/is a viable workaround.

---

<div class="post-metadata">

**Author:** ![boris](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/boris/32/71767_2.png) [@boris](https://forum.mapillary.com/u/boris)\
**Post date:** [November 20, 2023, 9:21am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/3 "2023-11-20T09:21:03Z")

</div>

Hi @bob3bob3 - do you need ffmpeg for these uploads or are you able to upload directly using mapillary\_tools or the desktop uploader? They should be able to process the mp4 files directly. Give it a go and let us know what you find. cc: @adalvit

---

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [November 20, 2023, 7:59pm UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/4 "2023-11-20T19:59:57Z")

</div>

Hi @boris @adalvit

The direct upload works fine. I did a small upload run to test if the Mapillary server processing was affected. I was going to suggest your dev/server people keep this in mind.

I do however also locally process the videos, so I can filter and do OSM edits. [bob3bob3's Diary | OpenStreetMap](https://www.openstreetmap.org/user/bob3bob3/diary) if you wish to read. I also sent a document to @eneerhut

I am using one of the Mapillary supplied BlackVue/firmware combinations. I run at 2FPS which is probably quite rare. I’d suggest that the header damage was something in the original or mapillary firmware. If I am the only one with the problem the workaround I have in place works fine.

As I recall ffmpeg always quoted a warning on BV videos, but since it always worked I haven’t examined that. I’ll check that later today.

---

<div class="post-metadata">

**Author:** ![boris](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/boris/32/71767_2.png) [@boris](https://forum.mapillary.com/u/boris)\
**Post date:** [November 21, 2023, 8:49am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/5 "2023-11-21T08:49:11Z")

</div>

Got it, thanks for the explanation on your custom workflow!

---

<div class="post-metadata">

**Author:** ![adalvit](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@adalvit](https://forum.mapillary.com/u/adalvit)\
**Post date:** [November 23, 2023, 9:28am UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/6 "2023-11-23T09:28:44Z")

</div>

> [@bob3bob3](#):
>
> The direct upload works fine. I did a small upload run to test if the Mapillary server processing was affected. I was going to suggest your dev/server people keep this in mind.

Thanks Bob, it’s appreciated, I’ll check how we are selecting the internal version!

---

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [November 23, 2023, 6:41pm UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/7 "2023-11-23T18:41:31Z")

</div>

@boris @adalvit

Warning message from (downgraded) ffmpeg deb-multimedia 10.6.0-dmo6 on extracting frames;

Command;  
ffmpeg -i 20231119\_090257\_NF.mp4 -s 3840x2160 -vf “select=eq(pict\_type,I)” -fps\_mode vfr -qscale:v 1 -qmin 1 -qmax 1 %3d.jpg  
ffmpeg version 6.0 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14)

[mov,mp4,m4a,3gp,3g2,mj2 @ 0x562195ee1ec0] Found duplicated MOOV Atom. Skipped it

---

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [February 13, 2024, 11:41pm UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/8 "2024-02-13T23:41:04Z")

</div>

Just for your interest only.

@boris @adalvit

Holding back the ffmpeg version was getting difficult as its libraries had many hooks into other applications. It became almost unworkable when Bookworm upgraded to 12.5.

I have got around it by downloading a static version from [Index of /ffmpeg/old-releases](https://www.johnvansickle.com/ffmpeg/old-releases/) in my case [https://www.johnvansickle.com/ffmpeg/old-releases/ffmpeg-6.0-amd64-static.tar.xz](https://www.johnvansickle.com/ffmpeg/old-releases/ffmpeg-6.0-amd64-static.tar.xz) I created it as ffmpefg-600 in my /usr/local/bin and it works fine with my script now.

My BlackVue direct uploads to Mapillary continue to work fine.

Cheers

---

<div class="post-metadata">

**Author:** ![adalvit](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@adalvit](https://forum.mapillary.com/u/adalvit)\
**Post date:** [February 14, 2024, 3:29pm UTC](https://forum.mapillary.com/t/heads-up-regarding-ffmpeg-processing-blackvue-videos-from-debian-bookworm-deb-multimedia/7577/9 "2024-02-14T15:29:18Z")

</div>

Thanks @bob3bob3 . I tested now with the packages in trixie and our internal ones, and they work smoothly. If you need to stick with deb-multimedia repos, maybe you can notify their maintainer?
