C100: C100 - Windows - After Effects (CS6) glitch..

Scott Freestyle

Well-known member
It seems AE hates mts files and causes no end of "glitchiness" and problems. I'm using windows and when I load the files into Premiere, all is fine... but if I dynamic link those files to AE, some (not all) some of them glitch during the first few frames. Having searched the internet for solutions, it appears that the problem is down to the .mts file type.

So, I decided that I should try the 5DtoRGB, and this resolves the issue, but being a windows user this is'nt really the tool that I can reasonably use. None of the windows versions have "Batch" processing, and to do 50 or so clips would be painfully long winded.

Mpeg stream clip does not recognise .mts files.. Repeatedly giving me an error and offering a suggestion of updating to Quicktime Alternative 1.81.. This doesn't remedy the problem.

My CC workflow has always been After Effects so I am a little bit pissed that I am experiencing these issues..

Does anyone have any suggestions or solutions.

I have the latest updates from Adobe for CS6
I have played with the various setting for interpreting the footage... (its not that problem)

A batch processing solution is required me thinks :(
 
Last edited:
I work with Avid MC (not with AP CS6), but generally would be better to work with professional types of codec, like ProRes or Avid DNxHD, Cineform. These codecs are I-frame only 422 8bit or 10bit (with scaled bitrate) and this solve "AVCHD" problems in NLE sw. Cineform and AP CS6 could be ok.
 
What I suggest is that you have to switch to either speedgrade that Adobe offers, or Davinvci resolve (try lite first)

but again, it only solves your CC workflow, if you want to make effects in AE, you will still face the same issue

guess thats why the AVCHD is for prosumers, not professionals.
 
Cineform? Wouldn't that work?

I work with Avid Composer, as I wrote., so my codec is DNxHD. But I heard from a friend that CineForm with AP is ok. But you must try this, I suggest only the principle of solution.
 
Davinci Resolve does not recognise .mts files either...

Anyhow, I found a solution that I would like to share with other windows users who own a C100..

Donwload this and extract to a folder

Download either the 32 or 64 bit, for reference I used the 64bit

extract the FFBMC file and place it in to the WinReWrap folder... click on WinReWrap and choose from the options for audio and files type.

Literally within seconds you can convert all of your files to MOV or MP4 and get to work using AE, Resolve, etc without any of the problems relating to the .mts file type.

>mts files are a freakin nightmare... but I'm glad this solution deals with the issues swiftly....
 
Good to hear you've found a solution.

AVCHD was always designed as a "transport" file - it's useless for editing, despite Adobe's efforts to make us believe otherwise.

I take a sideways view on it - it's a brilliant storage/archive format and takes up a fraction of the space of Intra-frame editing codecs like Pro Res. It transcodes really quickly and, if you use a transcoder that will consistently re-name and ID files (I use FCP X just to do this), it's a robust long-term codec. I'm in the process of pulling back a couple of hundred gigs to update a client film and it's all smoothly re-linking. That would have otherwise been terrabytes of ProRes, with the consequent extra time and space to transfer and archive.

My old colleagues in broadcast still employ armies of people and huge servers and networks to manage intra-frame format workflows. I think we've got it good at the mo!

Ben.
 
Back
Top