Christian Svanes
Forum Replies Created
-
thanks, olivia, for posting this!
it’s been a long time since i’ve last encountered a Quicktime -50 error but it happened just last night, repeatedly, and your post saved me hours of trial and error and probable hair pulling.
for me, clearing the render files, then copying the entire timeline and pasting it into a new sequence, with the sequence codec set to ProRes 422, seemed to do the trick. for what it’s worth, i never re-rendered the files on my timeline before sending the sequence to compressor.
additionally, i turned off the “auto-saving” feature, as well, and, to make sure none of my hard drives inadvertently went to sleep, i de-activated “put the hard disk(s) to sleep (when possible)” in system preferences.
thank you again!
. . . . . . .
\”climb mountains to see lowlands.\”
-
thank you, to both of you.
regarding the idea of doing all of the work in AE, i’ll see what i can do to improve my AE skills. i like doing my edits in FCP, but if i can edit just as easily in AE, then yeah, that makes a lot of sense.
-
sorry was a bit late in responding, so that i didn’t see joshua’s post until after i hit “post direct.”
not trying to make a sell on the mac mini…
-
that’s very likely true… but, when it comes to rendering and and creating large-ish video files, and only those things, i’ve given some thought to the idea that having a separate and cheap device that can manage that on its own, while i do other stuff with my MBP might not be a bad idea…
a colleague asked me – why do you need to be able to do everything on one machine?
and when i thought about where and when i set my machine to handle large render tasks, it occurred to me that this is not a bad question to ask.
granted, for me, speed is not always the primary concern – but then again, i’m rarely ever rendering more than 15 minutes of material for a final output…
i know a few people who use mac mini’s just for this purpose, and i don’t think they are crazy for doing so.
-
absolutely. thanks for clearing this up.
-
i have the same issue, but i’m not sure that this is an error.
from what i’ve read, i believe that FCP is simply non-functional while compressor is doing its thing.
i don’t know why exactly, but i’ve accepted it as a simple matter of course.
it would be interesting to know if i’ve been wrong about this all along.
-
i’m currently using a Macbook Pro, and so far, i’ve not encountered any unusual issues with working on HD projects.
that said, my projects tend to be very short in nature, and i’ve only upgraded to the MBP since january.
render times have not been as fast as i would have liked, but i’ve been able to handle it.
one thing i am considering, however, is buying a mac mini to supplement the MBP. i’d use the mac mini as my render farm. they are fairly cheap…. i figure that while i love having the portability of the MBP, i tend never to set it to heavy renders while i’m out and about – that always happens at the office. in which case, why not have a separate machine handle that particular task?
-
i’ve been following along in this discussion, and just wanted to say THANK YOU to those of you who have contributed. it has helped me resolve some similar AE export issues, for a project that i’m editing in FCP.
in my case, i created a series of text based graphics in photoshop (CS4), then moved those into AE (CS4), adding movement to the graphics (they essentially moved from right to left), then exported with alpha channel to FCP 5.1.4 – only to discover that the text-heavy graphics were very pixelated.
resolving the field dominance issue in FCP helped – by moving it to NONE. i’m also experimenting with doubling the frame rate for the AE composition, then re-importing that newly rendered mov. with alpha channel into FCP, making sure that the field dominance is none in the new FCP sequence.
i haven’t upgraded to FCP 6 yet, but i’m looking forward to that, since it might make some of these kinds of issues less painful for a newbie like me to grapple with.
thanks again!