- This topic has 9 replies, 5 voices, and was last updated 12 years, 2 months ago by .
-
Posts
-
Hi,
I have a :60 NTSC 1800 frames. Multiple phone # versions. One batch for all supers, very straight forward, white supers fading up over the letterbox, maybe 5, fade up fade down. This is a REV coming from another operator, I have loaded up their setups and library, same 2009 flame version.
Okay…
So when I hit process with only one batch tree set to process, wait wait wait wait, wait for it, 5 mins of waiting, and then it processes at the excpected speed. the system is locked during this time.
Is this normal?
If you need more info let me know.
-rand.
I wonder if you batch is just so big that you are running into problems? I have never seen this but I can imagine if you had 50 phone #’s copied your batch 50 times it might do this?
What I did last time I had to do phone super versions was build my batch and made sure I had keyframes at frame 1 and 1800, then I switched animation mode to loop (or is it called cycle – not at machine today). Then I made a clip that was the phone # repeated for 1800 frames, then the next phone #, etc. Ran this one batch when I left at night and then used the cut mode where you specify cut every 1800 frames to get my finished clips.
Jeff
hmmm…
nope, I actually only had one tree for one version at the time.
action>action>output
(supers)>(end animation)>outputI have a feeling it’s a software glitch of some sort. I have done lots of these kind of things and it instantly starts rendering 1-1800 no problems. Only the last two projects it has been funny like this, both phone # versions and both from another machine.
Totally strange. Thanks for the advice on the approach, maybe I’ll give it a round next time round.
-rand.
Maybe it is a “one frame optimization” thing. Remember for one frame media, if it is not animated, an action node calculates CC, blur, key, only for the first frame. Do you have lots of single frame media in your action nodes? If it is like that, all action nodes would cache all media processing for the first frame, and then the next frames will go a lot faster. But 5 min. for an initial start seems to be a huge delay. However it might be possible if you have a huge setup with lots of action nodes, and media processing…
what version of flame is this and what hardware is it running on ?
It’s Flame 2009 – Running on an HP Workstation, quad core AMD, 8G of RAM.
The Batch is very simple. Two Action files and an output node, very simple. Should not be taking this long.
My MaxLibrarySize keeps expanding each time I access the library as well. it’s currently sitting at 124mb
Is there a service pack for 2009 now?
-rand
I would go through support because something is obviously wrong.
Jeff
124mb ? … are there other boxes running projects off this one as well ? sharing the stones ?
nah just one stone per box.
so….
discreet/autodesk seems to think that it’s history on the clips that’s bogging everything down. I agreed.
does that sound right to anyone?
-rand
yes..that could be a possibility
- You must be logged in to reply to this topic.