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
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
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 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.
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.
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?