Quick update, trying to keep on and understanding what happens I’ve figured that:
first, the MP4 preview provider does not exists and Movie should take care of all the video content. Another thing is that the ffmpeg command at
fails for the specific files with an error:
[mov,mp4,m4a,3gp,3g2,mj2 @ ...] moov atom not found
/tmp/oc_tmp_ecpDfD: Invalid data found when processing input
files are mp4 files. The files that succeed use a different provider surprisingly maybe because they are just 1 sec long.
The reason I didn’t see any error previously is that the previewgenerator app fails silently at: (Yes, you should log that).
Further examining the files shows that they are all of the same size of 15728640 (15.0M) although some of the videos I’ve uploaded are only 10M, which means they aren’t just cropped or uploaded incorrectly (viewing works fine).
I figure it has something to do with the s3 object storage.
If anyone has any help he can offer it will be much appreciated.
I will continue to look into it and keep this post updated.
Figured it out, hope this will help the next guy.
It is pretty simple looking at the code.
The movie preview generator only uses the first 5M (at least according to the code, no idea yet as to why the tmp files are 15.0M) of a movie when it is not stored locally (object storage in my case), I guess this is not enough to generate the preview for some movie, I will continue the discussion over a fix within the open issue in the git and will hopefully fix it sometime soon.