Apple recently released version 5.3 of Motion which has changed how files are imported. The previous media browser has been replaced with an “Import” feature which does not support Motion’s own .molo (Motion Object) file format. I’ve submitted a bug report with Apple but it might help if you do to!
Motion contains its own shapes object library within the application structure. Navigating to this library reveals files in .molo format. Unfortunately, dragging these files onto the desktop and attempting to open or import them from Motion also fails. Attempts to put custom .molo or renamed .molo files back into the application structure also fails as a list is maintained by Motion which restricts available shapes to those included with the application.
I am working on a way around this issue but am obviously hoping Apple’s exclusion of their own .molo file support within the new “Import” feature was an oversight which they will soon fix.
The file structure has not changed, the bug is simply a matter of Motion no longer recognizing its own object file format. Help me let them know!
Thanks Scott. I submitted a bug report as well.
http://play.askvideo.com/motion-100-5-3-new-features/3
Mentions a workaround – putting items in the favorite folder. It worked for me.
This is a fantastic suggestion and works quite well. Thank you for posting this and I’m happy to share your post with everyone else.
Beyond what the video shows it’s also possible, of course, to make an alias of Motion’s Favorites folder (/Users/[username]/Library/Application Support/Motion/Library/Favorites) on your desktop or any folder of your choosing for easier access.
It’s also worth noting that while an actual file can be placed in the Favorites directory an alias will suffice and likely reduce file clutter. However, in my testing Motion will not scan into subdirectories of a folder’s alias dragged into the Favorites folder. It does seem to look into subdirectories of folders copied into the Favorites folder. This may be related to permissions on the alias.
In the meantime this is absolutely a functional workaround for getting .molo and .motn shape files into Motion 5.3.