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

Similar Messages

  • 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...

  • DV PAL vs 8 Bit UNCOMPRESSED

    I'm currently editing a TV show thats shot on DVCAM and is being ingest SDI via a KONJA card as 8 Bit Uncompressed in FCP.
    What i'd like to know is if I instead ingested the DVCAM tapes in its native format DV, will there be a quality difference as opposed to ingesting them as 8 Bit uncompressed?
    The show is Real Estate so its simple cuts with minor graphics, Name straps, Summery of the property & price & agents usually give me photos that I add, and I add a little motion to spice them up. The only time FCP need to render is any graphics added to the sequence.
    I understand 8 Bit Uncmpressed is 20 mb/s and DV is only something like 4 mb/s. If my native footage is DVCAM then wouldn't it make sense to keep it DV and then just mastter the final to DigiBETA?

    Steve is absolutely, 100-percent right, but there's still going to be a layer of loss in going from computer graphics to video. I only mention it because it just hit a client of mine yesterday.
    Client wanted large title cards on black, with screen-filling red type. No problem, right? Well lo and behold, the titles ended up looking jaggy +even though+ they were going into a ProRes 422 HQ 1920x1080 timeline.
    Why? Because of the conversion from 4:4:4 to 4:2:2. Video (with a few exceptions) only uses half as much horizontal color resolution as black-and-white resolution. So bright red type on a solid black background will end up looking like it's low-res, even though it's not. It's actually the perfect resolution +for video.+
    A television is not a computer screen. There are limits to what you can do, limits that depend on technology choices made decades ago. The reason we all get paid the big bucks is because we've developed the patience to live within those limits.

  • 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...

  • Worth the effort? 8 bit AVCHD 1080p 4:2:0 versus 1080i 10 bit uncompressed

    Hello,
    I am i homing in on a final MacBook Pro versus Mac Pro decision to enable both real-time capture (argues for portable) and final cut - color - motion work flow.
    i have a new sony HXR 5NU that provides me with 25 Mbps 1080p AVCHD 8 bit 4:2:0 from the camera or 10 bit uncompressed 1080i 4:2:2 via SDI or HDMI. The latter would involve a MacBook (not lugging a 45 pound Mac Pro around on the set) and an external MOTU HD Express HDMI or or a Matrox O2 LE.
    The key question is if the extra information is significant in terms of final look, constructing quality masks, etc. I believe the answer is yes as it relates to simply comparing 8 bit 4:2:0 versus 10 bit uncompressed 4:2:2. Seems the answer is murkier with the trade-off of 1080i (the uncompressed signal) versus 1080p from AVCHD.
    I do not know the internal workings of the camera, it is possible that it is 1080i off of the sensor electronics and a pull down is happening with the avchd encoder which means that it is not really a trade-off.
    Any opinions?
    Otherwise I just focus on getting the best out of my camcorder's avchd output using a waveform monitor and go for a Mac Pro in Post.
    Any thoughts on this?
    Wayne
    Portland

    Thoughts or opinions? Remember, you asked for it.
    You haven't done the math.
    You do seem to realize there might be some kind of quality difference between 4:2:0 AVC and 10 bit uncompressed, which is a good thing, but haven't dealt with the larger issues.
    First off, while FCP might deal with AVC without too much fuss, it is not an approved codec for use with COLOR, and you will be dealing with a transcode at some point.
    If you are dealing with some kind of sub-cinema format camera, which is producing AVC, then the practical reality is that its sensors are indulging in a serious amount of voodoo, and if your project is going to involve anything like a lot of greenscreen, then you are also buying yourself a certain amount of downstream pain, since the bandwidth that an actual 10-bit 4:4:4 camera produces is what you might really want. But that brings us to the real math.
    Your first paragraph contains the phrase:
    MacBook Pro versus Mac Pro decision to enable both real-time capture
    Uh.... I guess you'd also be looking for some other kind of AJA/Io or whatever interface to work with the MacBook Pro, since it only supports USB and FireWire natively, neither of which will support 10-bit Uncompressed, or some other kind of slot34 device. I expect you really meant "on-set" capture, rather than real-time, since the only other way into a MacBook would be a P2-type card interface. In addition, real time Uncompressed 1920x1080 is very demanding no matter whether it is 24/30 frame, 8- or 10-bit. I'd be surprised if any Mac laptop could hack it. Its harder to do than HDV.
    If you are recording on tape, then you can bet that the recorded format is segmented, which is a special, non-temporally related form of interlace, that allows a progressive frame to be recorded on a format that is maxed out at 1080i. Pull down is a term reserved for use with generating redundant frames to bridge a rate difference -- most notably "24" fps to "30" fps, which you don't mention. But which would be another significant hurdle.
    I used to have this handy-dandy chart that listed all the bitrates and storage requirements for uncompressed formats SD, HD, 2K, etc., but it isn't in my field of view at the moment. 10-bit Uncompressed 1920x1080 at 29.97 takes up about a TeraByte per hour... do you have that much storage for field work? It isn't RED. It also requires a transfer rate in the Gigabit range, so in a practical sense it really requires a fibre-channel interface.
    I'm kind of thinking you will eventually wind up with a ProRes workflow. You could get away with a laptop and AJA interface doing that.
    jPo

  • Exporting SD 4:3 to 8 bit uncompressed for DigiBeta

    I need to deliver an 8 bit uncompressed file 1920 X1080 of an SD 4:3 18 minute video to a lab for transfer to DigiBeta. The film includes titles, still images, SD and HD video. The DigiBeta will then be delivered to TV station, where they'll take care of readying for broadcast, captioning, etc.  I've only done this once before with trial and error, but for Digi Beta theater projection. I had to fiddle with settings to lose some artifacting (cost a couple trips to lab).  I thought I took good notes, but not sure if thorough enough.
    First, Sequence Settings: NTSC DV/DVCPRO 720X 480   Field Dominance set to "None" (this was the last change the last time that fixed the artifacts that I thought deinterlacing would take care of)
    Render YUV
    Setting when exporting:
    Uncompressed 8-bit, Quality medium (no other option)  1920 x 1080 HD, letterbox checked "preserve aspect ratio, checked deinterlace.
    Sound Linear PCM 48 kHz 24 bit stereo, Little Endian checked.
    IMac OS 10.5.8  2.4 gHz  4 GB Ram  Final Cut Academic 6.0
    Need any more information?
    I'd like to get this right the first time.
    Am I on the right track? 
    Thanks in advance,
    Dennis

    Broadcast is about bit-depth and Digibeta is a 10bit 4:2:2 format and supports high bit rate audio. HDcam also has a 10bit 4:2:2 hence why they asked for that too. In lamens terms it means it holds a huge amount of colour information. Imagine a stripe, one side is black and the other pure white and in the middle is grey scale- with 10bit the scale is really smooth, whereas 8bit is noticably chunky in comparison- espeically near the blacks.
    DVD is a compressed format and to make the file size fit onto a DVD they basically (in lames terms) strip away parts of the grey/colour scale so that is perceptually like the original, when in fact it is missing lots of the colour/grey range. But the audience won't know, unless they are viewing it on a screen capable of showing the range / resolution. You'll notice the lack of shadow detail in DVD's and if a broadcaster were to use it, it would be extremely blocky, grany saturated etc, because the broadcasters will encode/compress it too so they need the best quality.

  • FCPro Render times - much longer with different Sequence?

    Has anyone else noticed this? For many years I have worked with just a few Sequences in FCPro, and the render times seem to be similar in them all - at least that I've noticed. When I slow motion scenes, or render simple graphics - I kind of have a feel for how long I have to wait for various things. Both with my MacBook Pro (2010) and Mac Tower (2 years old). I've always found render times, not excessive. Usually I've worked with DVCProHD.
    BUT NOW . . . I'm noticing I'm waiting 2 to 3 times longer for any render. By NOW, I mean since I bought the XF300 and am natively importing 50mbs 12x720 footage into FCPro. (I overcrank a lot, so I tend to stay with 720.) It can now be done after the firmware upgrade a few months back. I love how much faster "native" import is, and I love it using 50mbs as it should, not 70mbs, which it did using ProRez import.
    BUT I'm noticing much longer times to render in the XDCAM 422 720p30. Render screen says "conforming edited MPEG-2." Of course, this takes away some of the excitement, and is downright annoying! Has anyone else noticed this, or is it just me? Can render times change significantly, depending simply on the timeline Sequence setting? If they do, I'll just live with it - but I need reassuring that it's normal to take much 2 or 3 times the time - or I'm kinda hoping I'm doing something wrong!
    Thanks,
    Larry

    OK Shane, I've done a bit of work here - this might surprise you?  Maybe you'll learn something, we'll find out.  But you've certainly been helpful to me!
    OK, I took a 5 minute Sequence, shot with the Canon XF300, imported natively into FCPro.  The test here is to now render in XDCAN vs. render in Prorez.  I LOVE Logging & Transferring in NATIVE as the files are 30% smaller (50mbs vs. 70mbs - and that goes for the ProRez exports as Self Contained movies, too - 70 vs. 50mbs.)
    So now it gets interesting . . . to render the 5 minute movie using XDCAM HD rendering (same codec) as importing footage = 5 minutes to render the timeline. Not much rendering was needed.  Coincidentally, 5:00 even to render about a 5 minute movie.  The total render "space" it used was 932meg.
    Now . . . I did the same render (after I deleted all renders) but this time I had it render in ProRez instead.  It took 3:30.  Soooo, it saved 1:30 in the rendering process.  GOOD!  So we "learned" FCPro renders faster in ProRez as compared with XDCAM, which is exactly what you said!    Oh, it ony used 832 meg for the ProRez renders, which means not only is ProRez faster to render, but it uses about 10% less space to actually "do"it.
    But here's the GLITCH I can't explain.  I then exported to self contained movie (which we normally do in our workflow, master to a self contained movie to save).  In the XDCAM render sequence, it takes 1:35 to export to self contained movie, about normal for a 5 minute movie.  But the ProRez render took almost 6 minutes to export!!
    WHY would it take over 3 times longer to export the ProRez sequence compared to the XDCAM sequence?  This is what didn't make sense to me.  (I'm wondering maybe in the export process, FCPro doesn't "see" the (ProRez) renders and has to rerender it just to export it? And that's why the export time is so much longer with ProRez?  What do you think?
    So to sum up, NATIVE import is faster and smaller files.  Then ProRez render is faster and smaller files.  So I'll do that!  BUT then it takes longer to export the "ProRez" rendered Sequence   You just can't win!!!  If you have a 60 minute timeline, it's seriously longer!
    Do your findings parallel mine?  Anyway, thanks for your time, and if you can't tinker with this, I certainly understand.  I'm just trying to setup a workflow here.  I've tested this 3 times, my results are consistent.
    Thanks again,
    Larry

  • Render Times Slow on iMac Core i7 Quad

    Is there any way to speed up export and render times in FCP? Right now only 30% of my processor gets used.
    I have a cluster made for encoding via Compressor, but wasn't sure if there was a way to get the most out of my processor while in FCP.
    On a side note, can't wait for the 64-bit version.

    I understand that this post was answered over a month ago, but the way that I understand to speed up FinalCut Pro is when you render with compressor, you have to setup multiple instances of Compressor using Qmaster. Look at this guide for more help: http://www.digitalrebellion.com/blog/posts/usingcompressor_with_multiplecores.html
    However, with Final Cut Express Compressor isn't available, so you can render out in to ProRes 422 or Apple Intermediate Codec to create your "master" file, then use a utility that is multiple processor aware such as MpegStreamClip to re-compress out to your final format. This process actually works pretty well using Final Cut Pro, Studio and Express, so this is the method that I use most of the time.

  • Outlandish render times!

    I have an assistant and she's gone for the day so I don't know if something she changed caused this slowdown but it sure seems odd. Anyway, she digitized 5 hour tapes of HDV footage and edited it into 5 separate sequences, one for each reel. We need to send out TC window DVDs to the client so I asked her to add the Time Code Reader and start rendering.
    Now, all the sequences will play easily in real time but the first render she set up said it would require 2 hours of rendering. That seemed excessive but I let it go. She got a second hour finished (again 2 hours of rendering) and took off for the day. Just now I started the third hour rendering and now it's saying it'll take 6 hours to render the next hour of footage! I checked to see if the parameters of the footage matched the sequence settings and every thing's correct. I looked to see if she was rendering in 10 bit or something odd and there doesn't seem to be anything amiss. I restarted and the same thing again.
    Since we're delivering on SD I tried laying everything into a DV timeline, hoping to output a DV movie and just go back and add the timecode filter in a second timeline. Same render times.
    Any thoughts?
    BTW, she's working on a 2.16 GHz Intel Core Duo Mac Book Pro with 2G RAM, FCP 6.0.2

    I understand that this post was answered over a month ago, but the way that I understand to speed up FinalCut Pro is when you render with compressor, you have to setup multiple instances of Compressor using Qmaster. Look at this guide for more help: http://www.digitalrebellion.com/blog/posts/usingcompressor_with_multiplecores.html
    However, with Final Cut Express Compressor isn't available, so you can render out in to ProRes 422 or Apple Intermediate Codec to create your "master" file, then use a utility that is multiple processor aware such as MpegStreamClip to re-compress out to your final format. This process actually works pretty well using Final Cut Pro, Studio and Express, so this is the method that I use most of the time.

  • 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

  • Gamma Shift After Rendering 8 Bit Uncompressed

    I'm getting a really bad black level shift after I render in Final Cut 5. I'm using the final cut 8 bit uncompressed codec, which is what the footage was captured at. Before I render, the preview quality looks fine, but once I render it out, it looks awful, the blacks get a lot brighter, to the point where there's no detail at all. I've changed all my video output settings in the render settings to all the settings possible, and nothing works. I use an AJA iola for video output/capture, but I know it's not that becuase I hooked my sysem up through a normal firewire setup and it does the same thing. It seems to do it everytime I render, and it doesn't matter what kind of fiter or change I'm making to the video. Any help would be greatly appreciated. Thanks.
    2gig dual core G5, OS X 10.4.5, Final Cut Pro 5, AJA iola

    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

  • 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?

  • 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.

  • Slow render times in Premiere when linking After Effects media

    I'm an Avid Media Composer editor but I just switched to Premiere for a special project that needs to have non-interlaced output. I've been pretty impressed until I integrated an After Effects project into my timeline. My render times have now increased exponentially, despite the fact that the After Effects effects are quite simple - single layers of video with very simple moves. Can anyone else chime in with their experience integrating After Effects projects into Premiere? This just seems too horrible to be true.

    I've found that the time to render out of After Effects versus the time to render a Dynamic Link comp in PPro is roughly identical. In fact, in many cases it's a bit quicker.
    For heavy duty comps, I'd expect to see PPro struggle a little bit more, but definitely not with the basic work you seem to be talking about.

  • Help - Getting slower render times with AE CS6

    Hi everyone
    Wonder if anyone else is getting as described?
    I have a 3m37s project which is predomnantly motion graphics using live shot footage (.MXF files), Illustrator and a few JPGs.
    In CS5 AE I get render times which average around 45mins, so I thought I'd see how quickly CS6 could crank it out by - as you can see I'm getting times which are in excess of 2 almost 3hours!
    The project contains a few 2.5D moves as well as tiny bit of Trapcode 3D Stroke
    I have mentioned on this forum that I'm having the Error 5070 problems with start up and Ray Trace is unavailable but these times seem seriously wrong to me.
    Mac Pro 3,1 (2x 2.8GHZ)
    20GB RAM
    OS 10.7.4
    NVIDIA GeForce GT8800
    NVIDIA Quadro 4000 both on GPU Driver 207.00.00.f06
    CUDA Driver 4.2.10
    All files are on a 2TB drive (7200rpm)
    Rendering to a 1TB drive (7200rpm)
    Corsair SSD 60gb Cache drive
    As an observation when I watch the frames counter ticking over, CS5 seems to steadily work it's way through the render at around less than a frame a second, CS6 seems to crank out 2-6 frames then hold for 30secs before working on another batch. It crawls to a halt near the end.
    Can anyone offer any help or advice?
    So far I'm not having a great time with my CS6 transition
    Thanks
    Rob
    Message was edited by: Bokeh Creative Ltd
    because of a Typo

    Thanks Rick - Yes what confused me was that it only took 45mins in CS5 even with MP 'on'
    Still having no joy with Ray Tracing though, even though I have a Quadro 4000 card, I get the 5070 error on start up. Any ideas?

Maybe you are looking for