Twitter media upload failed

[mythofechelon]

Similar to Shotcut's videos cannot be uploaded to twitter, I regularly use Windows 10’s Xbox Game Bar to capture gameplay and used Shotcut to trim and export using the default, unchanged profile “H.264 Main Profile”.

Unfortunately, sometimes, uploading it to Twitter fails with error “Some of your media failed to upload”. Example below below:

I’ve had the same problem with videos from other sources and, in those scenarios, I tried uploading from my iPhone, using all sorts of different profiles, etc.

FFprobe version 4.3 reports the following:
“Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘D:\Users\ben\Documents\Work in progress\Shotcut-Twitter problem\PORTAL 2 2020-09-08 21-46-56 (Xbox Game Bar capture).mp4’:
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: mp41isom
creation_time : 2020-09-08T20:46:57.000000Z
artist : Microsoft Game DVR
title : PORTAL 2
Duration: 00:01:31.93, start: 0.000000, bitrate: 33121 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1728x1080 [SAR 1:1 DAR 8:5], 32830 kb/s, 53.83 fps, 59.94 tbr, 60k tbn, 59.94 tbc (default)
Metadata:
creation_time : 2020-09-08T20:46:57.000000Z
handler_name : VideoHandler
encoder : AVC Coding
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 195 kb/s (default)
Metadata:
creation_time : 2020-09-08T20:46:57.000000Z
handler_name : SoundHandler”
“Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘D:\Users\ben\Documents\Work in progress\Shotcut-Twitter problem\PORTAL 2 2020-09-08 21-46-56 (Shotcut H.264 Main Profile default).mp4’:
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.45.100
Duration: 00:00:20.50, start: 0.000000, bitrate: 4565 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1728x1080 [SAR 1:1 DAR 8:5], 4305 kb/s, 53.83 fps, 53.83 tbr, 296880000.00 tbn, 107.67 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 255 kb/s (default)
Metadata:
handler_name : SoundHandler”

[shotcut]

It can work
https://twitter.com/shotcutapp/status/1303449739468431361?s=20

If you are using Automatic Video Mode, I suspect your variable frame rate input is causing Shotcut to output a bizarre frame rate they do not support. You can make a custom video mode with your resolution and aspect ratio that defines a simple frame rate like 50 or 60.

Video Mode

Introduction Video Mode is the project resolution, aspect ratio, frame rate, and color space. It is important to set this as you desire at the beginning of your project. If you try to change it later Shotcut will try to retain the timing of edits, but some users have reported problems, and it is risky. Also, at this time Shotcut will not automatically adjust anything for you related to size and positioning of elements like text and picture-in-picture when changing resolution. You can think of…

[mythofechelon]

You may be on to something.

I clicked on “Settings” → “Video mode” → “Custom” → “Add…” and increased “Frames/sec” to 60. The resolution was already set correctly.

I re-exported the video which generated the following file:
“Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘D:\Users\ben\Documents\Work in progress\Shotcut-Twitter problem\PORTAL 2 2020-09-08 21-46-56 (Shotcut H.264 Main Profile with 60 FPS).mp4’:
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.45.100
Duration: 00:00:20.50, start: 0.000000, bitrate: 4560 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1728x1080 [SAR 1:1 DAR 8:5], 4298 kb/s, 60 fps, 60 tbr, 60k tbn, 120 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 256 kb/s (default)
Metadata:
handler_name : SoundHandler”

Twitter accepted this on the first attempt:

I’ll post here again if I have the same problem but setting a standard framerate doesn’t resolve it.

Thanks.

[shotcut]

@mythofechelon

Twitter accepted this… setting a standard framerate doesn’t resolve it.

Which is it?

[mythofechelon]

It did resolve it.

The second bit was taken out of context. In context, I said “I’ll post here again if I have the same problem but setting a standard framerate doesn’t resolve it.” As in, if there’s a second cause of the same error.

[shotcut]

Of course, thanks for clarification.

[timlewis808]

I actually stumbled across a solution for this - at least in my case. It seems that the issue is with GOP not being fixed in the Codec options. Setting it as fixed on the H.264 High Profile option causes the outputted video to be uploaded to Twitter correctly. I wasted several hours last night trying to get this right, so wanted people to have this solution to hand.

I discovered this in some obscure media developer API documentation for Twitter where it says it doesn’t support “Open GOP” which I presume is non-fixed GOP.