-
very long render times in FCP6
Ever since I upgraded to FCS2 I’ve been experiencing very long render times.
For example in Motion I made a 10 second slate using a tiff background with 2 text boxes. There is no movement, no particals, nothing fancy. It takes 7 minutes to render in FCP using an Intel quad Mac Pro to a 2.5TB eSATA raid.
All the setting and prefs in Motion match my timeline and no other applications are running.
Is there some hidden setting I have to change? Do other users have similar issues?
thanks.
cheers,
greg -
10 Replies
-
Hi Greg
Go check out the Motion forum, lots of reports there about loooong renders with Motion 3. I’m sitting on seven boxes of FCS 2 waiting to install them, but after reading about all of the issues, I’m hoping we’ll see a bug fix release from Apple before I upgrade.
Cheers
John Christie
-
Im one of the original posters and I have not heard of any resolutions
to the extremely long render tines of Motion 3 files embedded in FCP6. I am hopefull… -
Greg for now either render them out of motion and import them to fcp or do like i did (I use it for slates mostly as well) and just export the first frame of the slate as a .tga file and set fcp to import stills for 8 seconds.
Motion is useless right now until apple fixes it.
Everything else seems to be working quite well and improved from older versions.
-
Are you guys working with 10bit sequences? I’ve been working with new and old motion projects in 8bit sequences rendering at 8bit quality and the render times have not really changed. Try changing your render quality to 8bit and see if that helps. I know it takes you down in quality but is a way to figure out what is going on.
yo
-
No, the 2 sequences were DV NTSC and DVCPRO HD 1080i60. I did try a test by creating
an 8 bit NTSC seq ( which did not match my clips – DV NTSC) and you are right! The 8 bit
sequence with the embedded Motion file DID RENDER FAST. Im not sure what the significance
is for people who need to output other file formats, but I think this is a good thing to know! -
I will tell you that I see the same issue as everyone else has seen. My renders seem to be very long, too, with Motion 3.
As an aside item, Adobe has After Effects CS3 Beta 2 available for download. Its much faster than AE7.
_______________________________
Wayne Carey
Schazam Productions
http://www.schazamproductions.com
https://blogs.creativecow.net/waynecarey -
So LasVideo,
Were your DVNTSC and DVCPROHD sequences set to 10bit render? Is that how you normally work, because I think they are set to 8bit render by default.
yo
-
Hi Greg
What codec are you working in? As a test I put a 2700 X 1800 jpg still in a motion project, added a layer of text and rendered it out as DVCPro HD 720. There was a move on both the still and the text layer. A 240 frame clip took 1:32 to export out as a QT movie. Then I imported the motion file into FCP and rendered it there. It only took 1:10 to render inside FCP.
Cheers
John Christie
-
I’m onlining in AJA Kona 10 bit uncompressed on my Intel quad. I don’t think I’ll ever work in 10 bit again, the benefits are seriously out weighed by problems like render times, out of memory errors and crashes.
Not to mention that after hours of rendering I have opened my project the next day to see it lit up like a Christmas tree and have to render all over again. I was able to restore my project to the last autosave and that has worked a couple time to recover the renders.
Another bug is that the sequence looks rendered but when you play you hit the odd blue screen “unrendered” in the canvas window.
cheers,
greg -
Yojimbo, they were set in FCP6 to whatever was appro for the clips (I didnt see any options for 8 bit). In Motion 3 they were set to whatever the default setting is (I also think that is 8 bit).
Reply to this Discussion! Login or Sign Up