MP4 Video being rejected with error

[GoNaytev]

Hi Twitter,

We are using the media endpoint to upload a video to be used in a tweet and recently twitter has started rejecting MP4 Videos. There is no information besides the video is “UnsupportedMedia” and it passes all the requirements laid out in the Media API endpoint.

Here is what Twitter responds with:
{“code”:3,“name”:“UnsupportedMedia”,“message”:“file is currently unsupported”}

Here is the video source file: https://www.sample-videos.com/video/mp4/720/big_buck_bunny_720p_2mb.mp4

Here is the metadata from FFMPEG:

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'SampleVideo_1280x720_2mb.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    creation_time   : 1970-01-01T00:00:00.000000Z
    encoder         : Lavf53.24.2
  Duration: 00:00:13.50, start: 0.000000, bitrate: 1248 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 862 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
    Metadata:
      creation_time   : 1970-01-01T00:00:00.000000Z
      handler_name    : VideoHandler
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 381 kb/s (default)
    Metadata:
      creation_time   : 1970-01-01T00:00:00.000000Z
      handler_name    : SoundHandler

Thanks for any help!

Mike

[andypiper]

Looks like this file has more than two audio channels? that’s unfortunately not supported. We should get this into the documentation.

[GoNaytev]

Thanks for the fast response Andy. What is interesting is here is another mp4 video that is failing with the same error but this time the audio is definitely two channels.

Here is the Video:

Here is what FFMPEG says:

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    title           : 221099955243661
    encoder         : Lavf57.71.100
  Duration: 00:00:15.23, start: 0.000000, bitrate: 445 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720 [SAR 1:1 DAR 16:9], 395 kb/s, 23.98 fps, 23.98 tbr, 11988 tbn, 47.95 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: aac (HE-AAC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 48 kb/s (default)
    Metadata:
      handler_name    : SoundHandler

Any idea what is going on with this video? I appreciate the help.

Mike

[GoNaytev]

Hey @andypiper, any idea why that second video is being rejected? It still isn’t working and our clients are eager to post these videos.

Thanks,

Mike

[spdustin]

Twitter doesn’t support “high efficiency” AAC audio. I’d suggest adding (or replacing, if you’ve already got this option) -acodec aac to the ffpmpeg command you’re using to transcode the video.

Source: https://developer.twitter.com/en/docs/media/upload-media/uploading-media/media-best-practices.html