videos exported from Camtasia are rejected by Twitter

  • 2
  • Problem
  • Updated 2 months ago
  • Solved
Twitter is rejecting all mp4 videos exported by Camtasia. I've tried every combination of mp4 settings, no luck. Twitter shows a preview of the video, but when you click the "tweet" submit button, Twitter shows an error saying the file was rejected. 

One workaround I've found is to use the 3rd party Handbrake app to re-encode the mp4 video. Then Twitter accepts it. This is a super painful workaround though as I share many screencasts to Twitter.

Please fix Camtasia video export so that we can upload videos to Twitter again. 

 
Photo of geddesign

geddesign

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 8 months ago

  • 2
Photo of Paul Middlin

Paul Middlin, Employee

  • 1307 Posts
  • 334 Reply Likes
Wow, that is really weird. I am able to get the same thing to happen. The video is able to play in the tweet preview, but refuses to post. Hard to tell whether the issue is on TechSmith's side or Twitter. Let me pass this to some people to see if we can find anything out.
Photo of catherine

catherine

  • 1 Post
  • 0 Reply Likes
Please figure this out. It's brutal that we cannot export video from Camtasia and it is rejected by Twitter even when the file size is correct.
(Edited)
Photo of Miriam Pereira

Miriam Pereira

  • 1 Post
  • 0 Reply Likes
Having the same problem here! Any solution in the meanwhile? 
Photo of nancy

nancy

  • 4 Posts
  • 0 Reply Likes
Having the same problem - traditionally, I've been able to post videos - but no more and very frustrating. Like one of the other posters, I tried all the suggested combinations for Twitter and nothing worked.  I tried importing the mp4 file to Adobe Premiere and could load the MP4 file to Adobe (the error message concerning improper compression). I had to download UniConverter from Wondershare and was able to immediately upload to Twitter.  


(Edited)
Photo of Paul Middlin

Paul Middlin, Employee

  • 1307 Posts
  • 334 Reply Likes
We believe we have fixed this issue- today's 2019.0.9 and the previously released 2020.0.1 should work. Get the latest and let us know?