Camtasia Supported Versions

[Nathen Paisley]

Ijust upgraded my Premiere Pro CC 2018 to v12.1.2 (Build 69) and now when I attempt to open a file that I was previously working on just prior to the upgrade, Premiere Pro tells me that my .MOV files are no longer supported. Exact error message is, "File format not supported."

The extension of your file ( mov, avi, etc. ) are thought of as "wrappers'. Like you buy food and it is in a thing that you can put in microwave or oven or something, and that is the "wrapper". What is actually IN the wrapper is a matter of what the contents are, which in this case is called CODEC. The Codec ( "Compression / DE-compression ) is similar to what you actually HAVE within the wrapper.

These codecs are sometimes being favored by some companies or dropped by others. In the current situation you are in, Adobe is discontinuing support for certain codecs that they deem is really old and no longer used by most users of the program.

That means that the CODEC ( rather than the WRAPPER) is no longer being supported by the newest versions of PPro. It takes a lot of programming stuff to differentiate those codecs and support them ( some are 8 bit old stuff and no longer used by most people ).

Thanks for the lesson on codecs. Unfortunately that doesn't solve my problem. I need a workaround. I can tell you the codec is H.264 and I've just read that it's discontinued. So I'd rather know what codecs still work with .MOV. Maybe I can convert these files to something that still works without losing the quality of the image?

That would be a older version of the Aple company QuickTime code which Apple decided not only would not be "supported" by them anymore but they have asked other software companies to discontinue accepting this version of Qt mov fles.

This is a standard problem for data, whether images or text, in digital formats. And requires the users figuring out how to convert to a newer format without lost od quality, formatting, all that sort of thing.

Thank you Neil, that's getting me in the right direction. Ideally, it would be great if I could translate to a lossless version of a .MOV file and I don't see that as an available option in Handbrake. If I'm missing something or if you have a recommended setting I'd be grateful to know what it is. My objective would be to create another .MOV file of the same name that Adobe Premiere will support so I can hopefully use it in my current project without losing the edits I've already created.

The Handbrake conversions to H.264, I think actually are mp4, which many consider a better codec anyway. If you stay above 4.2 or above in the quality, maybe going to 5, and keep the compression settings to "near placebo" so the resultant file size is at least as big as the original media, if not a bit bigger ... it does a very good job of the transcode. Fairly close to 'visually lossless'.

Sometimes one can simply rename the extensions on mov and mp4 files before import, and PrPro is just as happy. Try a couple files through Handbrake, and if as I recall it's in mp4 extension, try changing the extension to mov and see if PrPro accepts it. I know, if one does an offline/relink process, one can direct it to ignore the extensions, only 'read' the file name prior to the extension.

Yea, Apple want's to shaft a ton of people, no big surprise there ... bunch of jealous kindergartners that they are ... and while I can see why Adobe wants to stay at least somewhat comfortable with that bunch, still ... I wish they'd told them no. I've noted some other apps are for now still holding taking the earlier Qt mov's.

Doesn't matter the camera, it's whether there is an early QuickTime version used in the encode process. It's something like QuickTime 7 or close to that. Whichever number it is, that earlier version Apple wants to "denigrate". So it would be an mov format in that earlier QuickTime codec.

In these last days I have read, Premiere does not support AVI, Premiere does not support nvenc h264, and now that does not support MOV h264, I am thinking that I started to participate in Adobe forums only to suffer a heart attack.

Maybe, although I've not heard of the company. Check around on them. For instance, there's been several groups/firms that have announced providing full ProRes support in PrPro/Windows for write as well as read. None have lasted six months due to Apple's vengeance application team, er ... laywers.

Lol! "vengeance application team" Well stated. I've got an email dialogue going with the people who sell MediaReactor. Seems promising and they're willing to check over a sample file. I'll see what transpires.

Aside from the transcoding potential, if your camera ( like my Nikon DSLR and some canon cameras) have an HDMI port you can record to a better 10 bit space via atomos or something, to pro res or DNxHD etc. The SD card stuff with h264 mov was kinda junky anyway for editing. Although many people claimed new fast cpu's and stuff could deal with it nicely.

My problem is that I don't have time to deal with these kinds of issues, as I'm sure many others can attest. If I license software from a company there's a certain amount of expectation that it will work as advertised. No excuses. If not, I would be totally happy with some kind of workaround that would allow the software to work as it had previous to the upgrade that removed that functionality. I got nothing. Adobe doesn't really offer any thoughtful support options either. Just this forum really. And as much as I appreciate anyone's help here, this problem seems beyond the scope of what any peer can resolve. But thank you for trying though.

At this point I'll hang on for a couple of days to see if anything promising develops. Beyond that I'll need to look into other solutions. Perhaps an old analog Beta tape editor. At least that worked for over a decade.

Ok... It worked for a whole hour. I wish I could tell you why but I have no idea. I even tested it with several other projects and it was working, until I cleared the plug-in cache (a lot of my 3rd party plug-ins stopped working after the update). Now it's not working again.

This easily converts .mov files to a codec that can be imported in to the current Premier Pro. I just tried it and it works. It's for Camtasia but works the same for Premier Pro -resources/convert-alpha-movs-to-work-in-camtasia-9/

1. I'm working on an urgent AE project... The project has 30 .mov files (from a DJI Phantom Pro 4). Out of nowhere, an error message appears: "this .mov file is damaged or no longer supported" while i'm editing a totally different .mov file.

Google Chrome 50.0.2661.102m (FREE, OS, UNS) [Apr. 2016] Download from FilePuma: 32 bit 64 bit (After downloading, extract the file using the file extraction software of your choice [such as 7zip]. After extracting, run Chrome.exe directly, and the browser should run just fine in Windows Vista).

VMware Tools 10.3.10 (FREE, CS) Download here. While newer versions may be installed on Vista, the drivers rely on functions found in only Windows 7 or later which may cause unexpected errors with certain applications.

The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details.

WSUS Offline Update 10.9.2 (FREE, OS) Download from vendor here. While newer versions will run on Vista, this is the last version with which you may download updates for Windows Vista.

Anyway, this is one of those weird instances where XP and Windows 7 are supported, but Vista is ignored. It isn't that big of a deal though, the only thing Vista users miss out on is technical support from Adobe if you have a problem with the software. The CS6 software itself will still install and run perfectly fine in Vista.

For some reason Chrome feels better when browsing websites, hence why I still use it in Vista, though Firefox is the one that will still support it... YouTube, for example, runs much better in Chrome in here than Firefox, but there won't be any other option than upgrade to 7/2008 R2, or stay with kinda "degraded in performance" software or unsupported ones.

You can't say Haswell completely doesn't support it, since it's only some specific companies and chipsets (and mostly chipsets) that don't. Even so, probably unofficial support is in those 7 drivers for such boards from other companies like MSI too.

But there is a software timing issue with Windows Vista and haswell that causes it to not boot up half the time, and some services fail to start. Unless Microsoft or intel release a hotfix, I cannot guarantee that Vista will work properly with haswell. I will add EVGA as an exception for Vista, but again, whether or not that timing bug will appear I cannot tell. It could only affect H97 (which is what I tested Vista on), but I doubt it.

Just before the Startup Orb animation appears, you'll get an error that says "Interactive Logon Process Initialization has failed. Consult the event log for more details". Upon clicking Ok, sometimes Windows will proceed with the boot up process, and sometimes it won't. Usually, when it does, after you logon, some services fail to start. The one I saw most often was Windows Defender, and sometimes Windows Audio. If you experience any of these problems, the only solution as of right now is to upgrade to Windows 7 SP1 or later, where the problem is non-existent.

3a8082e126