Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Importing Motion 2 Project in After Effects 7?

  • Importing Motion 2 Project in After Effects 7?

    Posted by Jhankins on June 1, 2006 at 4:17 am

    I thought it was supposed to be possible to import a native Motion 2 project into After Effects? When I try, the file is greyed out, if I set the import dialog to all files, it fails to import with a plugin error. Am I missing something here? Wrong versions or the like?

    On the Final Cut Studio side I’m running 5.1 (recently crossgraded)

    Thanks!

    Jim

    Steve Roberts replied 19 years, 8 months ago 5 Members · 7 Replies
  • 7 Replies
  • Mylenium

    June 1, 2006 at 5:44 am

    I don’t hink this works. I’m not on a Mac, but all I’ve ever read is that you could open AE projects (up to 6.5) in Motion 2.

    Mylenium

    [Pour Myl

  • Filip Vandueren

    June 1, 2006 at 2:32 pm

    I’ve read that Motion 2 projects are actually also cleverly disguised quicktime-movies, just like .qtz (Quartz composer files)

    so you should be able to import the motion-project via “all files”, be sure to choose quicktime movie as type.

    But you won’t be able to edit the separate layers etc. in AE

  • Wes Plate

    June 1, 2006 at 11:27 pm

    Some people will tell you to rename the project file with a .mov extension.

    Because I didn’t want to rename my file, I did it one day by creating an alias to the .motn file, then renaming that alias with a .mov extension, then I imported that alias into AE 7.

    — Wes Plate
    Automatic Duck

  • Steve Roberts

    September 16, 2006 at 9:44 pm

    Hmm. Nothing’s working for me on this issue.

    – If I try it with a .motn file, using “all files”, and importing as “quicktime movie”, I get the “no Quicktime movie found” error, then the “files of type “mofo” not supported” error. Heh.

    – If I try it with an alias with a .mov extension using “all acceptable files”, AE says the .motn file (that the alias points to) is “not a recognized file type”. If I try “all files”, and import the alias, I get the above errors.

    This happens with my own files as well as Apple’s pre-made motn files.

    (Motion 2.0.1, AE 7.0, G5 dual 2.0, QT 7.1.0.)

    … and sorry Wes, the duck’s not in the budget right now. 🙂

    Thanks,
    Steve

  • Filip Vandueren

    September 16, 2006 at 10:27 pm

    Hmmm.

    Can you open it in Quicktime Player ?

    perhaps reinstall quicktime…

    I don’t think QT pro vs. Standard should be an issue if you’re not on Pro.

  • Steve Roberts

    September 16, 2006 at 10:50 pm

    Hmm. Good suggestion, Filip. (I’m on QT Pro, by the way)

    Dragging my own Motion 2.0 file (as a mov alias) onto the QT icon opens the file, but it then crashes after about a half-second. The same thing happens when I drag the motn file onto the QT icon.

    However, dragging an apple pre-made 2004 Motion 1 file from the Pro Training book (no motn or mov extension, no alias) works. It opens and plays fine. But it won’t import into AE — same two error messages. Neither motn or mov alias will import.

    Dragging a pre-made 2.1 file opens in QT, but plays with a “media missing” image. It won’t import into AE either — same messages as the other files, whether motn or mov alias.

    So the issue seems to be AE’s interaction with QT?

    Thanks,
    Steve

  • Steve Roberts

    September 16, 2006 at 10:59 pm

    By the way Filip, I just checked AE 6.5, and it works exactly the same way QT worked as I wrote in my last post. That’s sort of good.

    – able to import my 2.0 motn file, but AE crashes after about a half-second of scrubbing.
    – able to import the pre-made Motion 1.0 file, no problems.
    – able to import the pre-made Motion 2.1 file, but with missing media.

    All sort of good and workable … but I can’t do any of this in AE 7. No import.

    Any thoughts?

    Thanks,
    Steve

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy