Insane AVCHD (.mts) issues after CC 7.1.0 update
Red Planet Pictures Nov 12, 2013 8:00 PMSo technically I solved this myself, but I'm posting as a question in case anyone has a proper fix to make it a non-issue in the first place.
I often edit for a TV show shot on a Canon XA10, so for about a year I've been editing AVCHD files with little to no problem. I've had a mix of scratch disks with the full AVCHD file structures and just the .mts files on their own.
I applied the new CC updates last week (on Windows 7 64 bit), bought a Canon C100, and was excited to play with some test footage when I tried to import it and got the dreaded "The file has an unsupported compression type." error. The footage was imported using the included Pixela software, which joins segmented AVCHD clips if necessary, and gives you just the .mts files (no folder structure). So I turned to footage from one of my past projects, and sure enough, same thing. It seemed like I had a classic case of the old "revert to trial" bug on my hands, but I wanted to play around a bit more before reverting to a painful full reinstall, so I tried loading it into AME and AE - worked fine! I then opened the project that used that previous footage...and it worked! Sort of..
It loaded already imported videos fine, if I tried to reimport the same old clip that didn't work in my previous attempt, it worked fine. But then if I tried to import C100 footage, it wouldn't work. I closed the project and reopened the previous one where I first discovered the problems, and once again none of it would work.
So then I tried something crazy. I just renamed one of the clips....and it worked??? So then I renamed all of them and BAM they all work. Ridiculous. Not content with this, I reconnected my camera, and imported the footage manually, both as the entire AVCHD structure and as only .mts files, and now they all work, even without renaming. The old footage I have though? Doesn't work unless it's renamed. But, I tried importing the C100 through the Pixela software again thinking that might have been the cause...and it also works!
So in conclusion..I have no idea. But if anyone has any clue what is going on here, be my guest and explain this nightmare. But if you run into the same situation as I have, try just renaming your footage and playing around to see what happens.

