-
Motion 5 refuses to ‘save as’
updated 8 years ago
4 Members
·
9 Posts
-
Brand new MBP running latest Motion. On many occasions it refuses to save or ‘save as’. Very frustrating as I loose work. Is there a known problem or work around I can adopt?
Thanks
XdcamEx & HD, C300, DSLRs, all sorts of production & post gear and a very untidy desk. On the East Coast of the UK
-
I hate to be one of “those guys,” but it’s working fine here.
Is it possible that you’ve filled you destination drive?
Tim
—
Tim Jones
CTO – TOLIS Group, Inc.
https://www.tolisgroup.com
BRU … because it’s the RESTORE that matters! -
No, I wish! (it was as simple as that!)
A
XdcamEx & HD, C300, DSLRs, all sorts of production & post gear and a very untidy desk. On the East Coast of the UK
-
BUT.. It is formatted ExFAT. Having said that, the ‘save as’ command doesn’t open the dialogue at all, so no opportunity to save as test to the desktop.
XdcamEx & HD, C300, DSLRs, all sorts of production & post gear and a very untidy desk. On the East Coast of the UK
-
Not a fix, but can you save regular cmd S? Why the save as? If it’s for versioning, you can always just dupe the original in the finder and rename it v1, v2, etc. and just save the one you’re working on.
I recently had the old can’t save can’t undo bug crop up. Maybe it’s related. I was basically out of RAM and motion got all wonky. I did have FCP X, Motion, AE, PS, and AI open along with iCal, mail, Safari and who knows what else.
-
[Bret Williams] “I did have FCP X, Motion, AE, PS, and AI open along with iCal, mail, Safari and who knows what else.”
Just for the record… thanks to OS X’s dynamic memory management (and compression), as long as you don’t have any HUGE unsaved files open in any, then you could technically have as many apps open as you wanted, and it would (i.e. shouldn’t) hardly make any difference in RAM usage overall. 😉
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Should work that way. But get a memory app like memory clean. As you use Motion and FCP X, you might feel FCP X lagging or Motion start to act squirrelly (less common). Take a look up and the memory available and you’ll see something like 245mb. Keep working and you’ll get a crash. Especially in FCP X.
-
Whereby that’s actually (part of) a feature not a bug. Because those unlimited undos in FCP have to go somewhere (which would technically qualify as “unsaved” as mentioned above). But I personally have never had that lead to a CRASH either. Slowing, yes.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Oh sure. And I have 32gigs. My biggest fault is having all that cool motion vfx object stuff there in FCP X and scrubbing it. Or any 3rd motion templates really. Depending on their complexity, they’re pulling a full version of motion up into ram just to render them. Then, X is caching it into ram so that the next time you scrub it, it’ll be ready to go. The mObject ones are of course very ram heavy. As are ones with mflare.
Log in to reply.