moov atom error when switching to Azure

[merlinbest5]

My colleagues are in the process of migrating their video project from AWS to Azure and are running into a new issue: "The video's moov atom position is invalid.
See the manual for how to fix this."

Example video here https://biigle.de/videos/9161/annotations

The volume is already annotated, and everything was working fine, the only change is the URL pointing to Azure vs. AWS.

It doesn't happen for every volume, for example this one is fine: https://biigle.de/videos/8602/annotations

My best theory was that the dot in some blob names and filenames was causing issues, but that doesn't seem to be the case as this one is working: https://biigle.de/videos/9152/annotations

Any suggestions would be very appreciated!

[mzur]

This is caused by a recent change in BIIGLE: #1056

In our understanding, videos with an incorrect moov atom position did not work properly in the video annotation tool. The videos could not be scrubbed, i.e. you could not jump forward or backward in the video until the entire file was downloaded. Was this different in your experience? If the moov atom is problematic only in some cases, we could change the current error message to a warning only.

At the moment, to fix this, you would need to reprocess the video files as described in the manual.

[merlinbest5]

Interesting. No, I don't believe they were experiencing this issue, over 13,000 annotations done with the original video and they seem to navigate fine. I'm not familiar with moov atoms, I'll do some reading, but the examples above are working without the reprocessing. I would love to see this error as a warning only since reprocessing and reuploading everything at this stage would be very time consuming.

[mzur]

I'll test one of your files and if they indeed behave correctly, we'll roll back the change.

[mzur]

I can confirm that with your videos, scrubbing works correctly and also Largo thumbnails are generated correctly (which was also a problem that we observed). I have rolled back the change that implemented the error message. We will work on a different solution that shows a dismissable warning message.

[merlinbest5]

Thanks for your help Martin.