Partial fix The uploaded file was not a video as expected.

Affected version
2.1

HJW

Active member
Sometimes get this for videos that play fine on mobile and desktop downloaded from a site using FBdown.net extenstion.

Is it something in my settings I need to change or a bug? Videos are too large to be allowed to be uploaded here
 

Chris D

XenForo developer
Staff member
Maybe a bug. We'd need to see an example video to test it.

To upload that here, please add it to a zip file first before uploading.
 

RobinHood

Well-known member
I just got this error with a video downloaded from WhatsApp.

Tried to edit it in the Apple Photos app on iOS to crop some information out and not even Apple Photos could edit it. Kept getting an ‘There was an error saving this video. Please try again later’ when trying to crop it.

So maybe it’s something weird that Facebook does with their videos.
 

RobinHood

Well-known member
So I tried re-encoding it using handbrake and that resulting video uploaded fine.

The original does also open up and play just fine in the browser on it's own.

It's an mp4 and this is the codec information according to VLC

1608386361261.png

It's a very low frame rate video, probably because it's from a security camera, maybe that's it. Although it does play just fine in the browser on it's own.

If a dev would like the file let me know and I can send it privately. Perhaps transcoding of vids uploaded to posts would help solve this.
 

XF Bug Bot

XenForo bug fixer bot
Staff member
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.2.3).

Change log:
Improve video validation for a specific type of MP4 video file.
There may be a delay before changes are rolled out to the XenForo Community.
 

Mike

XenForo developer
Staff member
I've tagged this as a partial fix because I have resolved this for the video that I was sent, though it's not really knowable if the video in the first post had the same particular issue. If you run into this problem in 2.2.3+, please open a new bug report.
 
Top