Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Exporting a still frame from Motion 5

When I export a still frame from Motion 5 the process takes an exceptionally long time with the


User uploaded file


followed by this error:


User uploaded file


Any ideas or others with this experience?


Thanks all!

iMac i5 27, Mac OS X (10.6.7), MacBook Pro Mid 2007

Posted on Jul 3, 2011 2:54 PM

Reply
19 replies

Aug 13, 2011 10:46 AM in response to Douglas Suiter

Doug,

Maybe I don't quite understand the issue. From Motion 5 "share" menu I select "Save Current Frame", give it a name and pick a format such as JPG, and off it goes. i don't try to do this by exporting to compressor. It works fine for me. The catch-all fix for most of these is to delete your user preference file for Motion and try again. Seems to reset most 'bugs" Hope this helps.

Aug 15, 2011 8:08 AM in response to Douglas Suiter

Hmmm. I can suggest a few other things that have worked for me if nobody responds with a better idea. I have had random failures like this that just seem puzzling at first, but turn out to be a permissions issue. I had a Photoshop file that refused to save until I fixed permissions on my hard drive. Why they get off from time to time is a mystery to me. Launch your Disk Utility in Applications:Utilities and verify your disk permissions. If that's ok, make sure your codecs are up to date or haven't become corrupted. Perian codecs for Quicktime works perfectly for me - which is at Perian org.


I don't know how you installed Motion 5 in relation to Final Cut Studio from before. I haven't had issues with both M5 and M4 on the same boot partitian but I followed the recommended installations. If you didn't follow recommended installation steps then review them and see if something clicks there. And, I had a menu item in Photoshop called "magic extractor" that just didn't exist despite what the web was telling me. Uninstalled Photoshop, reinstalled and voila it appeared.


And as a really desperate workaround, I have expanded the frame to full screen and then hit Command Shift 3 to take a screen shot of the image. Hope this helps.

Aug 16, 2011 8:32 AM in response to Douglas Suiter

Doug,

I'll ask around and keep trying to help you. It's the "domain error" that makes me think it's file permissions problem. In addition to permissions, there's a verify disk button on the right. if your file is trying to save to a spot on the hard drive that is corrupted, it will keep trying about ten times then give up. There will be no indication you have a bad spot on the drive. Be sure to check that as well and please let me know how it's going. thanks.

Dec 1, 2011 6:14 AM in response to Douglas Suiter

I have the same problem. I have loaded Motion 5 on three different dual quad machines trying to figure out the issue and the problem exists on all machines. I want to purchaces Motion for a large group of machines, but this issues makes it a no go. I hope Apple gets their act together because this feature used to work flawlessly in all other versions of Motion. What a drag.

Jul 1, 2015 6:08 AM in response to Silicon Hills

Now 4 years later, and Apple STILL hasn't fixed this problem - so frustrating.


All that permissions advice solves nothing for me, still get the hanging/spinning wheel while Motion tries to (unsuccessfully) export a single still frame from the Motion project - it exports a full ProRes 4444 project in less time than it takes to prepare to save a single frame! Ridulous.


If Apple spent more time fixing these bugs than they did releasing "exciting" new versions of Motion 5 with not-very-useful new features like a Manga line generator (which I will likely never use) the dwindling community of Motion users would be so much happier - I know.


The only work around I've found for this problem is to export "video" of the frame or frames wanted. Import to FCP, (FCP 7 in my case) and export using Quicktime Conversion, which allows a single frame to be exported... that gives me what I need, but with a silly round tripping via FCP...


Hope that helps.


J

Jul 8, 2015 5:48 AM in response to jonathanhowells

This is certainly not a widespread problem.

Most people have no trouble with "Save Current Frame", so you should not assume it is a general bug.

It is more likely a local issue that may be more or less difficult to troubleshoot.


Let's start with specific information, like Motion version, OS version, Mac model; possible conflict-inducing plug-ins or extensions (the OP mentioned he had Perian installed, which has been abandoned years ago and is not recommended on recent OS versions - I'd look at that as a possible cause).


Did you delete the application preferences? In the current version of Motion, this is easy to do (hold down command and option while starting the application and confirm). For older versions you should use the Preference Manager application.

Jul 8, 2015 8:20 AM in response to Luis Sequeira1

Thanks Luis,


Perhaps so. But I have heard of many others experiencing this problem beyond this particular thread.


I have deleted the prefs, with the technique you describe, and the problem persists.

I am on the latest verision of Motion (5.2.1) and on Yosemite (10.10.2) am on a new (cylinder) Mac Pro (Late 2013).

Graphics card: AMD FirePro D700.


I do have several plug-ins running with Motion (Reel Smart Motion Blur, Twixtor, Red Giant Looks and few others) but figuring out which one may be conflicting with this seemingly simple task of saving a current frame, is a bit of a needle in a hay stack. I actually get an error message from Motion when trying the save current frame.


Or if it's a Permissions problem, I don't know how to solve that... why are Permissions in their default state, often a culprit with Mac problems?!

Jul 8, 2015 8:32 AM in response to jonathanhowells

What error message do you get, exactly? It may provide important clues as to where the issue lies. Can you post a screenshot of the error alert?


Permissions in their default state don't cause problems; only (sometimes) when they are wrongly set. Usually that happens because some installer messed up.

But unless the error message suggests that is the problem, I don't see permissions playing a role here (I could be wrong, of course).

Exporting a still frame from Motion 5

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.