Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

sunandsurf

macrumors regular
Original poster
Jul 23, 2008
130
3
just wondering: i've got an hour long clip that i imported into FCP; since i was going on a short trip, i thought i'd start the transcoding/analysis step. well, i'm back after 3 days and it's only 95% done! three days and nights??? is that normal? seems way too long but i'll listen to cooler heads.

thanks.

*** i watched it run from 95% to done; it's finally done. unbelievably long. does the mac mini go to sleep when not in use? could that be why it took so long???
 
Last edited:

monokakata

macrumors 68020
May 8, 2008
2,036
583
Ithaca, NY
You could fire up Console and look at the logs, which will show you when it went to sleep and when it woke up.

If I'm running something that's going to take a while, I always do set sleep to never (which means remembering to set it back, but that's another matter).
 

daybreak

macrumors 6502a
Sep 4, 2009
531
0
One hour of video is going to take a long time. Yes if you put it in sleep mode it will not carry on.
When you got FCP-X open and transcoding material make sure all your other applications are not open this will help to speed things up.
 

mBox

macrumors 68020
Jun 26, 2002
2,357
84
Where is this being saved to?
At times its your I/O that bottle-necks.
Ive done long shoots but with SD material.
 

sunandsurf

macrumors regular
Original poster
Jul 23, 2008
130
3
You could fire up Console and look at the logs, which will show you when it went to sleep and when it woke up.

If I'm running something that's going to take a while, I always do set sleep to never (which means remembering to set it back, but that's another matter).

Thanks for suggestion; am so busy now but will check it out tonight; I didn't change any settings regarding sleep but if the mini by default goes to sleep after X amount of time, then that's the problem; I had no other apps running (and the original file is on an external drive) but I doubt those were the key factors; most likely scenario is that it went to sleep and ceased working; Ugh!

*** Apparently, by default, it's set to sleep after X minutes of non-use BUT why would it go to sleep when FCP X is working hard at transcoding? Lesson learned: the next time, I'll set it to never sleep. Thanks guys.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.