-
fastest workflow for renders?
firstly – sorry for caps lock..time is precious!
(yes it is, but so is the time of the admin team that is having to edit this mountain of visual mess — next time please use all lower-case if you are in a hurry as it looks far less crappy…)
quick one..if i’m using a still (4000×3500 pixel jpeg for instance) to do a rostrum type move on – i.e: an ease out from very cu to reveal full image – should i have that source pic reside on my video raid drive, or is it going to be ‘accessed’ just as fast on my media drive?
————————————
my general ae workflow entails:-
– apps on system drive
– projects / psds / stills on standard sata media drive
– source footage / renders on raid-0 drive————————————
i ask because it’s taking 15 mins to render an avi of a still with a simple move on (and a little interlace flicker reduction to stop thin lines jittering). it’s only a 10 second comp and i ask because when i look at the render info it seems to be taking the same amount of time to ‘retrieve the frame’ as it does to apply the blur effect. does that sound right?
what are other ppl’s workflows?
thanks guys.
*production studio premium cs2 / *combustion 3 / mocha v1
————————————-
win xp pro sp2 / intel p4 3ghz / 2gb ram / geforce fx5200 / decklink pro / roland ds-5 monitors / sony bvm-20g1e / dvs sdi clipstation / wacom intuos 3 a4 / 110gb boot/80gb media/600gb raid-0 -
3 Replies
-
Jimmy, if you minimize AE, I think there’s no need to use Caps Lock …?
———–
I suppose it depends on whether the JPEG is split over multiple disks. Sounds like it’s time for a test. 🙂
———–
15 minutes for 10 seconds with such a big still doesn’t sound too bad. Is the drive defragged? If it is, then the time might be taken in AE’s ingesting the still and making sense of it …?
-
Caps lock – do you know what..I hadn’t even thought of that! I guess it can’t redraw the window if it’s not displaying it. Is that the same if you just Tab the renders window to fill screen so you can’t see the comp window?
JPEG on several drives – it’s just one image on a standard 80GB SATA drive currently, so no it’s not split over several drives..if it was on my RAID-0 then it’d be split over 2 drives, but ideally I only want to keep stuff on there that can be either re-captured from tape or re-rendered..due to the safety (or lack of) on a RAID-0.
All drives constantly de-fragged with Diskeeper Pro – so maybe it is cos it’s such a big still? Maybe the reduce interlace blur? Seems like a long time when all the client wants is a simple move that doesn’t chatter! Hey ho.
Any other tips guys?
*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0 -
you can also close the comp window before you start a render.
Reply to this Discussion! Login or Sign Up