ProRes Render time issue

I hear a lot about the benefits of ProRes so I decided to change my workflow from HDV to ProRes.
I am trying to Render 1 hour footage and its saying its going to take 6 days!!! whats going on? I am running a MacBook Pro 2GB Ram and connected to a Firewire 800 external drive.
FCP 6.0.5
am I doing something wrong?

Hello,
reading and writing from the same disk will slow down the export. Try exporting to the local disk instead or a second external disk.
Apart from that I recommend trying to restating the export process several times. With me it sometimes tells me 6h for a 10min clip and the 5th time round 6 minutes. Sometimes I even restart if the machine has been running and rendering for a few days.
Hope that helps...

Similar Messages

  • Render time Issues with 5.0 project in CC 12.1

    This is actually a copy of a post I had in a different discussion entitled "render time" but this now
    I did some extensive testing to try and see why my render times in CC were so much slower that 5.5 and I found some very interesting results.
    The original project was created in 5.0 and opened in 5.5 and rendered, it contained video footage and graphics. When it was render in 5.5 it rendered in 4:27. When I opened it in 12.1 and rendered it was 18:00. I then started turning off layers and my render times shot up. basically layer 12 had two animated masks on colored solid. With this off it took 8:30
    I then imported the project into 12.1 and saved it, reopened it and with layer 12 off it took 5:11. So importing and saving the project made a difference. Now I recreated layer 12 in 12.1 from scratch and turned it on and my rendered time was 6:50.
    So there is something going on with projects being converted from earlier versions - Now to really test this theory I would need to recreate the project from scratch and compare to the 5.5 times.
    To further test this we did the same sort of testing with a different comp and found similar results - the render times were different if it was imported vs. just opened. But the big thing we found with this comp was a layer where we were moving large stills with some z space. It looks like the 3d from 5.0 was causing a major slow down in CC on layers that has AE 3d applied.
    I think the major take away is if your comp was created in 5.0 and you need to modify it, then make changes in 5.5 or 5.0 or be prepared to recreate any layers with more than simple key frames.
    Just to also answer some other questions - in rendering to prores vs. animation or dvcprohd the times were almost the same. The animation was slightly longer but that makes sense cause the file was much bigger.
    I also found that with 32 gigs of ram my magic number was 11 reserved for other apps ...
    Hope someone can jump in and add some light to this
    This was all done on a 2010 mac pro 2.66 w 12 cores 36 megs ram running 10.8.4 - I have 5.5 and CC and the 12. 1 updates are installed and the video card is an NVidia 575. Mulit threading was on and in 5.5 - 9 Megs is reserved and in 12.1 - 10 is reserved

    I've experienced similar problem with Java Web Start twice.
    Also using JRE version 1.5.0_06 Java HotSpot(TM) Client VM and Browser Internet Explorer 6.0.2800.1106 on Windows XP (Problem was the same with Java 1.4.2)
    My application was signed and launched via JNLP. The security warning popup was shown in the windows taskbar, but it was hidden. Using maximize in the taskmanager, I was able to see the dialog but it was blank. The problem was persistent, although I did not try as many times as 20-30 :-)
    On both occations the problem occured on multi (3) screen systems, which I suspected to be the problem (Java has historically had some issues regarding multi screen systems), but now I'm not so sure.
    Did you find a solution / cause?

  • ProRes render times vs 8-bit Uncompressed

    We have a project being brought in to us with the footage as Pro Res 422
    Our editor thinks that perhaps it may be beneficial to media manage to 8-bit Uncompressed and do the edit and then re-link to the original Pro Res material because she thinks that it may save rendering time.
    There will be quite a bit of colour grading, vignettes, masks and multi-layers etc, that will almost certainly give us red render bars.
    Final delivery will be to SD and HD and as it happens the originator of the material can supply us media managed 8-bit Uncompressed clips anyway so we don't have to worry about wasted time there.
    It's really to discover which codec is most efficient with respect to rendering.
    I'd initially thought about the data rates that each requires and thought perhaps that might give a clue - but then the whole HDV issues of long render times made me re-think.
    I'd love to do tests but the client will be there from day one and I'd love to be able to suggest a work flow straight away. (Searches on the forum havn't come up with a comparison - hence this request...)
    We're using G-Raid drives that seem to handle both codecs quite happily.
    Oodles of thanks for your collective wisdom.
    LEE

    ProRes is not a long GOP structure (it is not HDV). It is an all "i" frame with compression while maintaining a 4:2:2 color space. Its getting very good reviews including it's ability to work in Color and other grading/finishing options.
    Just for your own piece of mind, why not get a segment in both formats and do some testing. That's the only way you'll know for sure the best workflow for your interests.
    Good luck,
    x

  • Exporting HD in FCX - massive render times issues

    Hello,
    Reading the FCP X Help topics etc I think I have a good understanding of import/export criteria. However, I have it from some peers that I could do much better with regard to reducing the massive render times I am experiencing.
    Currently the render time for an 8minute clip is 26 hours using Compressor 4 using preset 'HD 1080 Video Sharing (H2.64) - AAC
    BACKGROUND:
    OS X 10.8.3 (12D78)
    17-inch, Late 2008 MacBookPro
    2.5 GHz Intel Core 2 Duo
    4 GB 667 MHz DDR2 SDRAM
    FCX 10.0.8
    Raw footage is 1920 - 1080 from Canon D7 card -  copied to an external HD.
    Import settings: both proxy and optimised - both with huge export times as above.
    Destination to Movei folder or desktop
    The 8 minute sequence includes filters which I know will increase processing time, but by this much is pretty horrendous. (a 'preset' colour correction + sharpen + manual colour correction)
    My understanding is that if I import - or later convert all footage - into optimised files - these become ProRes222 files which will give me much faster render and export times. But this does not seem to be happening.
    It simply is not efficient or practical to myself or any clients to have 25 - 30 hour export times for 8 minute sequences
    My impression is that this computer is simply not up to  faster rendering/export processing - but my peers tell me my currrent render/export times are rediculously long.
    Can any one advise please.
    Thank you.

    This is the Final Cut Studio forum.
    You need to ask your questions here: Final Cut Pro X

  • Render Times on FCP Not Accurate?

    Hi, <- My casual Greeting
    Hopefully there are a few video editors out there on the forum... cause this one is program specific....
    So I have been an avid Final Cut Pro guy for the last 4 years. I love the program.... I can work very easily in it but recently I got a new job in which I have been using both FCP and Adobe Premier.
    Here is my issue... I have been using files that come in as MPEG 2 and have been using MPEG Streamclip to convert them over to a ProRes file for FCP. From FCP I have had to export them into 3 formats
    1. Mpeg 4 (the file format our website takes)
    2. FLV (Format for online video sites)
    3. QuickTime (XDCAM) for our tricaster
    The last week I have been using FCP and my render times have been (for a 5 min clip)
    1. Mpeg 1 hour+
    2. FLV 20 min+
    3. QuickTime (XDCAM) 1 hour +
    Yesterday I was told to use Premier as my boss uses Premier on a regualr basis and I assured him that the times would be the same as FCP is a Mac native program and that Premier was made to work on a mac but is essentially a PC program (I am eating my words now)...
    I redid the renders on the same file...
    On premier the render times were
    1. Mpeg 30+ min
    2. FLV 12 min
    3. QuickTime (XDCAM) 40 min
    Why is this? Do I just have something really messed up in my settings that FCP is not rendering quickly and Premier is? I would hate to have to hop over to Premier... I enjoy using FCP way to much.
    The other question I have is why are FCP render times not accurate...
    The renders will start saying 5 min then 10 then an hour etc.... and the time will not be accurate. If it says 5 min it may go for an hour... or if it says an hour it may just complete while still telling me I have an hour to wait.
    Adobe Premier, right off the bat, will tell me the frame it is on and the percent and time left... almost to the T.
    If possible... please help me get my fcp back on the right track.
    Tim

    Rendering can be much faster if you have a multi core intel Mac and you use Qmaster with Quick Clusters.
    Here's how.
    Set up Quick Clusters in Qmaster. (A description of how to do this is in the manual and also can be found in the Qmaster forum here in the Apple discussions as well as out on the web.)
    Export your sequence from FCP using "current settings". (Do NOT use Quicktime Conversion!)
    Open up Compressor and submit your file. Add the three output elements.
    Submit the file and click "use unmanaged services"
    Go have a cup of coffee while all the cores chug away at things. I guarantee it will be faster than the way you are currently exporting (if you aren't using clusters)
    x

  • Slow render times with large jpegs - complete system lag

    In a project i'm working on I have two large jpegs with a small zoom scaling effect. Going from 100 to 103 percent.
    I've noticed that both Adobe Media Encoder and Premiere Pro experience a heavy slow down in render time as soon as the jpegs have to be rendered.
    Not only does the render speed almost come to a halt, the complete system lags very heavy, even the mouse cursor won't respond well.
    This happens when i have GPU acceleration enabled and when i do a 2 pass H264 encoding.
    When I have the GPU acceleration disabled the render goes very smooth, and doesn't seem to slow down...
    The jpeg is 4023  x 2677, and 6,97 MB large.
    Scaling the jpeg down to about 1920x1080 in Photoshop and put that one in the timeline made the render go a lot faster.
    I understand that a large picture takes a bit more time to be rendered, but we're talking about a 10minute render whit the large jpeg file and  a 2 minute render with the jpeg resized.
    The total time of the two jpegs in the video is 5 seconds in a 3 minutes video.
    So, that made me think that the render times are exponentially long.
    In the timeline everything runs really smooth.
    Is this considered normal, I can't remember having such big differences in CS5. It's not a major thing, but I wanted to share anyway.
    My system:
    Premiere Pro CC (latest)
    i7 4930K
    32 GB RAM
    2xGTX480
    Footage and project on a Raid0 disk
    Previews/Cache on a Raid0 disk
    System and Premiere on SSD
    Render to a single 7200 rpm drive.

    >wanted to share
    Yes... known issue... I think some of the below is about P-Elements, but the same ideas
    Photo Scaling for Video http://forums.adobe.com/thread/450798
    -HiRes Pictures to DVD http://forums.adobe.com/thread/1187937?tstart=0
    -PPro Crash http://forums.adobe.com/thread/879967

  • Looong render times with motion templates

    I've been a big advocate for FCPX as there are a lot of great features but there are some things that are just killing me, no.1 render time.
    I'm working on some simple presentation edits using motion templates I have built in motion 5 and published to fcpx. The templates all consist of a single dropbox for video with a type field for test messages next to it. These are against a flat white rectangle used to reflect (similar to the coverflow but against a white background) and a subtle camera sweep has been added so it slowly turns from one side to the other by 30 degrees. Each of these is 10 seconds long.
    I chop up my imported movie on the timeline (untouched by grade/fx/retiming) and add the template to each of the chopped clips. I then select each applied template in the timeline and use the video well to select the clip below it for the dropzone. I add my text. That's all good. I now have a timeline approx 3 minutes long consisting of these motion graphics templates.
    Now, if I chose to either render or export a QT with timeline settings, estimated time is 8 - 9 hrs (I have tried both) I left a 3:30 project exporting last night at 11:45. It finished at 9:00AM.
    That is just unacceptable. It is irritating because the functionality of building the sequences in FCPX far outweighs what FCP 7 is capable of but the so-called "renderless" abilities of FCPX
    are making life ****.
    I use Event Manager X to turn off everything I am not using except the individual project. I have reset preferences in Preference Manager to see if that helps. I have purged using terminal. I have my clips on an external firewire 800 HD. I have no other software running. I accept I need a more powerful Mac - I'm using a 2009 3 Ghz Intel Core Duo iMac with 6gig ram using Lion 10.7.2 and FCPX 10.0.2 but 9 hours for a 3:30 clip?
    Any suggestions for where I can cut down on render time are appreciated. The source clip for the video for the dropzones and the final exported presentation movie are HD ProRes.
    Cheers

    The situation you describe does not seem normal. It should not take nearly that long to render and export your 3:30 movie. Considering that your mac is not one of the most recent vintage, and your are editing in full HD, one could expect it to take a bit of time, but nothing like this.
    In the way of troubleshooting, you could try and export just one of these 10 second segments.
    I have no way of knowing for sure, but I guess that it might export in a much more reasonable amount of time.
    I suspect that memory may be running scarce, which, as has been repeatedly mentioned in these fora, is a problem affecting many of us using FCP X under Lion. You mentioned you used "purge" in the Terminal, but in such a long render you might have had to do it repeatedly...

  • Render time in HD

    What is the standard time to render and export a quicktime movie in HD format. My format is DVCPRO HD1080i50. PC Specification is quadcore dual intel xeon mac pro with 6gb of ram. I need approx 8 min to render a 3 min video. Plz help. I am using fcp7 in OSX Lion.

    What HD format?  There are many.  Full resolution DVCPRO HD? ProRes? H.264? For YouTube? Vimeo? BluRay?
    What plugins/filters do you have on the footage? Render times will vary based on that.

  • Premiere-After Effects Dynamic Link render times vary wildly after minimal composition changes

    Here is something strange that happens a lot to me.
    I'll have a sequence in Premiere Pro CC 2014 that is entirely or largely an AE comp that I have dynamically linked.  I'll use a specific case as an example, but it's happened with various projects.
    In this most recent one the visual (but not audio) of my Premiere sequence is one AE dynamically linked comp of about 90 seconds.  It's more or less a fancy slide show- some photos with moves, some text, motion blur, masking, maybe a few filters.  Fairly basic stuff as far as After Effects goes.
    Anyhow, I like to render the sequence in Premiere and then watch it down with music to see if the timing works and make adjustments from there.  That's my usual workflow.  The strange thing is that when I render, the render times can vary tremendously.  With this particular project, one time rendered in about 2 minutes in Premiere.  I watched it down and I noticed a spelling error, which I fixed.  Just changing one word of text in AE.  This, of course, causes the entire linked comp to need to be rendered again in Premiere.  This time when I go to render, it took about 20 minutes and it only got about  70% of the way through.  A huge difference and all I changed was a couple letters, which shouldn't impact how intensive of a render is needed.  What I usually do is cancel the render when it takes that long, then quit Premiere, reopen, and render right away after I open.  When I do this, after the application restart, the sequence will then render in the faster approximately 2 minute duration.  Almost invariably this is true.
    So I end up quitting and restarting Premiere a lot to get the faster render times.  But of course that's annoying.
    What is going on here?
    I know that some might have critiques of the workflow and watching in Premiere and the fact that one letter change forces the entire sequence re-render.  I know I could break it up and there are ways around that.  But I am not interested in such critiques.  My work flow actually is quite efficient when the 2 minute render time happens.  Just not when it takes 10x more than that for the same thing.  Why are there these huge render time swings?
    My guess is that some cache gets filled up, so when the application is just started, and the cache is empty, the render works much better.  But I really do not know.
    Help please.

    There is currently a bug that causes Dynamic Link performance to be poor when the main After Effects application is running. (The underlying issue is that the main After Effects application is sending many more messages during Dynamic Link than it needs to.)
    The easy workaround is to quit the main After Effects application when using Premiere Pro to process a dynamically linked After Effects composition.
    This bug is fixed in an update due to be released in less than two weeks.

  • Help with configuring Qmaster for optimal render times.

    I have a 6 machine Qmaster cluster. All machines in the cluster are PowerPC based and I have set up the cluster manually through Qadministrator. I personally like to have everything set up manually so no changes can be made for any reason to this cluster. I have processed a 2.5GB video in the cluster and in an Intel based Mac Pro.
    Using Compressor, my output for the file is H.264 for iPod video and iPhone 640x480. The source was placed on an external Firewire 800 drive and destination is to the local disk on the Intel machine.
    For the cluster, the source, also from the external Firewire 800 drive, is connected to the cluster controller, which has full read write access to all nodes in the cluster and is not a node in the cluster itself, just set to be the cluster controller. ( I saw this setup on a Qmaster setup page here, http://www.eventdv.net/Articles/News/Feature/Distributed-Network-Encoding-with-A pple-Compressor-37923.htm ) Also, I am using the same output settings, H.264 for iPod video and iPhone 640x480, and output is being written to the cluster controller local disk.
    Once the batch is completed, it takes 23 minutes to render the video in the cluster as opposed to 25 minutes on the Intel machine. Not the difference in render time that I hoped for.
    Here are the specs for the machines,
    Cluster nodes:
    1.6 Ghz Powerpc g5 1.25 GB
    1.8 Ghz PowerPC G5 4GB
    Quad 2.5 Ghz PowerPC G5 2.5 GB RAM
    Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
    Dual 2.0 Ghz PowerPC G5 6 GB RAM
    Dual 2.7 Ghz PowerPC G5 2.5 GB RAM
    Cluster Controller:
    Dual 2.0 Ghz PowerPC G5 2.5 GB RAM
    Intel Machine:
    2 x 2.26 quad core Intel Xeon 6GB RAM
    Now I know these machines in the cluster are old but all machines, except for the cluster controller, have gotten fresh installs of Leopard 10.5.8, all relevant updates applied and fresh installs of FCP6, Qmaster and Compressor. I still cannot figure out how to speed up rendering. Is there something in this setup that I am doing wrong or is it the limitations of the old hardware. In theory, it should break up this video into segments across all machines in the cluster but it doesn't. The chunk of segments are sent to the Quad G5 and yes I have enabled multiple cores in the Qmaster prefs pane. So I figured i'd only enable 2 instances on the quad core machine and then it started to send segments to other machines but render time is still slow.
    Also, even though all machines had read/write access to each other, I would scroll through the log files and see that it could not read the segment from the source media, but I could clearly see the activity light flickering.
    After all of this trial and error, I still cant get the render time under 23 mins for this video.
    If there's anyone out there with some advice, it would be much appreciated. Also, I forgot to save a copy of the log file, so my fault on that one but I will post once I get a chance to get back to working on that cluster.
    Thanks.

    Update:
    So I have been able to get the cluster working. I've used Compressor and have the source media located in the shared folder that the controller mounts as cluster storage on all of the machines. The problem that I can't figure out now is why the cluster won't read the source media from any other location. I've read through Qmaster documentation and the permissions are supposed to be bypassed when you are using Qmaster.
    I have both the mac HD and clusterstorage drives mounted for each machine, on each machine. Still, the cluster won't transcode the file unless I drop the media into the shared folder first. Every sharing option I could think of has been enabled. I have enabled file sharing, appletalk, set read & write permissions for each drive in each machine for all users and It still won't work any other way.
    It just seems impractical to have to first copy the source media to the shared folder mounted by the controller since all locations on each machine have been totally opened up.
    If anyone has some advice about this issue, it would be greatly appreciated.

  • Rendering Hundreds of Audio Previews Upon Export, Long Render Times

    Hi everyone,
    I have an assembly cut of a feature, with footage and a timeline at 422 ProRes HQ, 24 fps, 96kHz audio.
    When I try to export any length of a clip, I get exorbitant render times and hundreds of audio previews to render.
    Video alone is rendered almost instantaneously.
    There are some audio files on the timeline (music and SFX) at 48k sample rate.
    Any ideas what the problem is?
    Thanks.
    Premiere CC 2014
    OSX Mavericks
    2 X 2.66 Quad Core Xeon
    32 GB memory
    NVIDIA Quadro 4000 w/ CUDA
    3 tB 7200 RPM - RAID 0

    Thanks, Ann. I'm thinking that may be a factor because this is the first time I've had to work with audio recorded at 96 and I've never had this problem.
    Can anyone else elaborate more?

  • CS5 on mac 10.6.4 slows system to a crawl, render times really long

    We recently upgraded our towers to 10.6.4 and all productivity has slowed to a snails pace using After Effects. On 10.5 the speed was almost TOO fast on our renders...it was awesome. Now I'm looking to get that speed back.
    I have a few very simple comps. 1920 x 1080, 23.98fps, 5 layers (4 QT renders from final cut XDCAM and Animation codec, 1 adjustment layer with levels and hue/saturation for color correction). Approx 40 seconds long each.
    I've followed the Adobe advice of turning the multiprocessing on and using the following settings from here http://forums.adobe.com/thread/543440
    leave 4gb for other apps, set minimum 3gb per processor = 33min render
    setting it back to what WAS screaming fast on 10.5:
    leave 3gb for other apps, set minimum 0.75gb per processor = 19min render
    turning multiprocessing off = 5min render
    same project on 10.5 system with multiprocessing turned ON with the above mentioned settings = 2min render
    what is going on here? is there a compatibility problem with CS5/10.6 and Animation codec files? that seems to be the bulk of the slowdown, but still over twice as slow?
    additionally, when AE is rendering the rest of the system becomes unusable...every action, even dragging a finder window around, results in beachballs and a 30 - 40 second lag in response. this happens with or without multiprocessing.
    I just want to get back to work...any ideas on how i can configure this beast to get back to my former speeds?
    8 core mac Pro
    OS 10.6.4
    12gb RAM
    many thanks in advance. i'm willing to send beer for a winning fix.

    Good to know, thanks for the update. 10.6.x does manage memory differently, but our testing for performance has shown a slight improvement in the newer OS. So I am guessing that the OS update is not the issue. I just ran another test on a Mac with your configuration and saw a 4% improvement on 10.6.4 over 10.5.8.
    It's uncertain what state the system memory was in when you started your tests. That's why I asked for a restart of the computer. The times reported seemed like there was a possibility that the OS was swapping. XDCAM footage places a high demand on system resources.  But it's hard to say without being there.
    What I was seeing with the initial post was that the two extremes of allocation per background cpu were tried, but not the middle ground. To better see this, launch the Activity Monitor utility or look at the last line of the MP preference. With the 4GB reserved and the 3GB/ bkgnd cpu setting you weren't getting any extra processes spawned for multiprocessing. You can see this in the preferences multiprocessing section as "Actual CPUs that will be used = 0". Then, by setting the pref to .75GB/bkgnd the app launched 8 bkgnd processes, but for the task at hand, I am guessing that they were starved for memory and sometimes failed to render. This was faster than the first test, but still slow. By setting the pref to 1.5GB/bkgnd cpu you were now getting 4 new processes spawned for multiprocessing. The background processes had enough memory to succeed so that made it render faster still.
    Now, try setting it to 1GB/bkgnd cpu. That will launch 6 processes which should render faster as long as that is enough memory for the task. If  the Memory pref for Reserve RAM for other apps is set back to 3GB, it will allow the spawning of 7 bkgnd processes. If that is a successful balance for this project then it will be the fastest render time. But, our testing shows it will be at the risk of starving the OS for memory, thus the more conservative 4GB recommendation for a 12GB system.
    It's a fine line and why we are recommending that one give up a little speed by reserving more memory for other apps. True, there will be less processes spawned for multiprocessing, but there will also be less chance for the OS to start swapping to disk which greatly slows down performance for all tasks. If that compromise is not acceptible, then the alternative is to buy more ram so that all 8 processes can adequately receive enough memory for the job, and yet still maintain adequate reserves for the OS and other apps.

  • EX cam footage render time?

    I have EX1 footage captured as EDcamEX.
    I placed it in a pro res time as recommended for faster renders.
    The footage was an event- low light. The gain was high.
    I applied a BCC Denoise filter.
    The filter cleaned it up nice but,
    The timeline is about 90 minutes and The render out is taking 11 hours (?)
    Is this render time correct for this type of filter on this length timeline?

    Hi -
    Couple of things:
    1) When dealing with XDCam and Ex footage, I routinely get very long estimates for renders that rapidly drop as the render progresses.
    2) I am not sure what advantage you got by editing the Sequence with the Codec set differently from the source. I routinely edit Ex footage on sequences that have the same codec (XDCAM EX 1080p30) and the renders, while not zippy, are not outrageously long. If you think about it, now FCP has to convert all the footage used in the sequence to Pro Res as well as rendering any effects or transitions. This is probably quite CPU intensive.
    Don't know if you want to consider this, but you might want to create a new sequence that has the same codec and frame size and frame rate as you source material, and copy all the clips from your ProRes Sequence and paste them to the new sequence and try a render there.
    Hope this helps.

  • Render time has INCREASED!

    I'm running FCP 6.0.4 on a Quad 3GHZ Mac Pro with 8GB of RAM. I am working with Sony XDCAM HD 1080i (35MBS, VBR) footage.
    I edit a 28:30 local TV program and have produced over 20 episodes so far. Its a fairly simple format and most of the shows are relatively the same, so I had grown accustomed to consistent render times. The main element that needs rendering on every show is a small animated logo in the lower right frame. It is on-screen for 95% of the program. For the first 20 episodes, even with some select clips having multiple layers of graphics and color effects, to render the entire show, it would take 2-4 hours at the most. Again, these render times were consistent for the first 20 shows or so.
    However, for the last few shows, I am experiencing extremely long render times for the same format I've been working with for over a year. It now takes 8-12 hours to render the entire show. I have four internal 750GB hard drives. I do not store any footage on the OS drive and I always make sure I have more than 30% free space on my source disk.
    Would anyone have any idea why render times would have drastically increased?? Was there a recent
    software update or something that may have caused this, either with Leopard or FCS?
    Any suggestions would be appreciated.

    Run, don't walk, to the Aja site and download a copy of their Kona System Test utility. It's PowerPC, which is a little annoying because it takes a long time to launch. But it's a great tool to test disk I/O performance. (Also, despite the name it is not in any way related to the various Kona I/O boards. I haven't received by LHe yet, and I've been using the System Test tool for ages to keep an eye on my framestore bandwidth.)
    For comparison's sake, I get on the order of 160 MB/s reads and writes on my framestore. It's a very humble configuration, just two internal 750 GB SATA drives striped using Disk Utility. If you're getting less than that, something ain't right.
    How exactly are you setting up your projects? Are your timelines using the XDCAM compressor, or are you using ProRes? If you're using an XDCAM timeline, do you have ProRes rendering turned on? Do you send your finished shows back out to XDCAM, or do you go out in some other format? I ask this part because it's possible — though since you've been doing these shows for a while you almost certainly already know this — that you don't actually need to stay in the XDCAM format at all, unless you're going back out to XDCAM media. If you're laying off to some other mastering format, or going out with a Quicktime master, you can skip rendering back to XDCAM entirely, which may save you hours and hours.

  • FCP 7.01 Render times 5-6 times longer than FCP 6

    I just upgraded to 7.01. I am doing the same job I was doing last week. Exactly the same. The week with 7.01 render times are approximately 5-6 times longer. How can that be possible? I have FC Studio, can I go back to version 6 just for FCP? I'm amazed because FCP 7 has been out for months. Isn't everyone else seeing the same problem??
    I work to complete the same day. So render times increasing means that I can't work with FCP 7! Does anyone know if Apple are going to solve this problem asap?
    The sequence is Prores 422, various media in the sequence: H.264, Prores, graphics.. but the point is that last week with FCP 6 it was 5-6 times faster! I've been working with FCP fro years. There is no doubt in my mind that the render jobs are exactly the same but FCP 7 is rendering them 5-6 times slower..

    I have not had a similar experience but I do always follow these two rules whenever I upgrade.
    1) Do not upgrade during the middle of a project.
    2) Do a clean install, don't just upgrade the software.
    I presume you have double checked that your sequence settings are correct? It could be a corrupt file and you should be able to determine if one particular file is the problem. You may have to render sections or single clips in your sequence to do this.
    You may also want to consider that H.264 is not a recommended edit format. It is a deliverable format. I realize more cameras are shooting it and many people claim success while editing with it but there are numerous posts on Creative Cow and other sites that do not recommend doing it. They recommend converting it to ProRes or some other format.

Maybe you are looking for