[Allan Houston]

This can be irritating in Premiere and even more problematic in After Effects.

This is what I do for each.

Most recent versions of Premiere seem to handle it better but in previous versions, when you open the ‘link media’ dialogue box and after you click ‘locate’, you can locate the MTS file in finder (I assume it’s roughly the same in windows explorer) and right click the AVCHD file > ‘Show Package contents’ > Right click on BDMV file > ‘Show package contents’ again > navigate to ‘Stream’ folder and with Premiere in the background, so you can see both it and the finder window, drag the Stream folder into the locate box.

In After Effects I drag in the files again and, with the offline media selected in the comp, hold down option (or alt) and drag the newly imported footage into the comp. It replaces the offline footage in the comp with the exact same effects, position, timing etc.

There must be a better way and it would be a pain if this involved many files but this works for me most of the time.

[Allan Houston]

Updates for both Premiere and After Effects were release this week, so hopefully they cure some of the problems. I haven’t checked them out yet.

Dividing 2014 into 2 versions without backwards compatibility between projects was a terrible idea. At least this version of AE produces projects that are compatible with the previous version. Premiere doesn’t unfortunately.

I would like to make one point though. On another thread I have criticised Creative Cloud’s horrible login issues but it must be said that there is an amount of responsibility one must take when new versions come out. Don’t rush in. Test the waters first and try it out. It’s the reason it took me a while to update to Mavericks and why I haven’t updated to Yosemite yet. So just be sensible. Of course you shouldn’t automatically switch to the new version when it comes out as you won’t be able to go back to the previous version, without at worst losing some of that work, or at best having to fiddle around with an XML. There can be many befuddling problems with this new software, but the part you should be playing is to test things out, be wary and don’t rush into a big change before you’ve got your projects finished and are confident the apps are stable.

[Allan Houston]

Agree with the above posts.

The new big releases do tend to have bugs so a little restraint is required. DEFINITELY finish current projects.

I have completed a couple of small projects in Premiere 2015 without too much hassle but the biggest annoyance as the dynamic link between AE and PP. If you import an AE comp, sometimes it doesn’t appear in the list of comps in a project in the import dialogue, so I had to export from AE and import the rendered mov or mp4, rather than “render and replace” on the timeline.

I think a few times the “replace with after effects comp” command created the comp in AE but in Premiere there was an error and I was left with the original clip so, again, I had to render from AE and import in PP.

A few other bugs were present but I can’t remember the specifics. They were fairly small projects so I didn’t get to give it a full Audio Editing workout etc. My current projects, I still have in 2014. I am excited to try out the new features like the morph transition in the future though as I edit a lot of talking heads!

AE comps seemed to play better directly on the PP timeline though (when I was able to import them or “replace with…”).