fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

Motion 5.0.4 crash on export

More
29 Nov 2013 22:48 #34886 by jjsanderson
I have a completed Motion project which, without fail, crashes Motion when I attempt to export it. Things I've tried, to no avail:

* Restart the Mac.
* Nothing much of use in the crash log. Crash occurs on the main thread, responding to NSButton (?!)
* Trash Motion preferences.
* Send to Compressor: Compressor goes unresponsive.
* Compressor Repair, then try Compressor again. No joy.
* Move the project to a different Mac (with Nvidia rather than ATI graphics)
* Fiddle with export settings (motion blue, render quality, etc.)
* Export ProRes 422 rather than 4444.
* Repair Permissions. Because hey, that always works.

What's odd is that the project is simple enough to play in real time and will render a RAM Preview with the canvas set to my chosen export settings. It just won't export. Other projects will.

It's a very simple project: a background movie (ProRes422, turned off for export. Or on, it makes no difference), with a couple of shapes animated via keyframes and some text labels. A couple of simple behaviours on the text and shapes.

At this point I can't see any option other than to give it up as a corrupt project and start over. Which isn't the end of the world – I've spent longer trying to export it than I did manually key framing – but still. Grrr.

Before I swear mightily at Motion - any suggestions? Cunning troubleshooting approaches which might help?

Big thanks for any suggestions. At this point I think I'm stumped.

Please Log in to join the conversation.

More
30 Nov 2013 00:25 #34898 by Gabriel Spaulding
I've certainly had that happen before, and it is maddening. I have no guaranteed fix for you, unfortunately. However, you might want to save the entire project in your Favorites section of the Library, then quit, relaunch, and then open that project in the Favorites section and try to export. You could also try copying and pasting into a new, blank project. Either way, tricking Motion has worked for me, from time to time.

Please Log in to join the conversation.

More
30 Nov 2013 09:34 #34912 by jjsanderson
Solved.

Copying-and-pasting into a fresh project did the trick. Don't know why I didn't think of that.

Curiously, I had to rework a couple of Link behaviours: I had some arrow shapes varying in width with a motion track, and the Link attached to them was horribly messed-up: impossible scaling factors for the result I was seeing in the corrupt project. I ended up deleting them and replacing them fresh to get the look I wanted. Export went without a hitch.

Huge thanks, Gabriel. I spent longer trying to export that overlay than I did creating it. :unsure:

Please Log in to join the conversation.

More
30 Nov 2013 16:59 #34920 by Gabriel Spaulding
You're very welcome! I'm glad I could export some helpful advice.

Please Log in to join the conversation.