[Marco Cogumelo]

I’m having the same problem… 59gb of “RAM” being used for premiere….
Are you using warp stabilizer on your footage?
I’m thinking maybe my problem would be related to warp stabilizer’s data that premiere creates on the analysing process, I don’t know, in this project I’m trying to stabilize a lot of footage to speed up the stabilize footage…
I’ve created pro res files from the original MTS from camera, I realize that warp stabilizer doesn’t like non editable formats… if I use it too much on mts or mp4 files it constantly crash the project…
That’s why I guess that maybe a bug with warp stabilizer plugin would eat a lot of memory… just a guess, I really don’t know!

[Marco Cogumelo]

https://vimeo.com/80187743

or

https://www.beachfrontbroll.com/2013/06/dealing-with-light-flicker-while.html

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Marco Cogumelo]

Hi Kevin!

Thank you for replying this thread.

Here are my software specs:
CS3: 8.0.2.27 Intel based, not Rosetta enabled;
Keylight was 15v5, now 15v8;

I copied the folder 8.0 to my desktop and then all AE settings were reset, so I tried to render it again; but it failed. I had to change the settings for the following: 35% Max RAM cache size, disk cache disable and multiprocessing enabled, and set 6 active cores in the prefs.txt (eventhough I have 22GB of RAM, which is enough to run 8 cores, i would be happy with those 6 hehehe).

I always used the Animation codec, there is a plenty of space in  the hard drives so I opt to have uncompressed files when possible (my psycho always tells me to do this way hehe).

Here are the facts: last night I ran a render test with the settings above without the Keylight v8 (just updated from v5 to v8, so i haven’t tried it yet but I don’t think this could be the problem, because in this 50h render, believe it or not, only the virtual set was on the queue, chromas were not being rendered out because their medias were already rendered in a Animation mov, in a kind of proxy process).

This test had ran for 11h with no errors with the disk cache disabled until I interrupted it this morning. 1300 frames had been rendered at that time in a total of aproximately 19000 frames.

In summary, disabling disk cache, 22GB of RAM, new VGA (ATi 4870) and 4TB Raid didn’t improved the render process and now it seems to be worse than before the upgrade! I don’t know what is going wrong and what to do to fix it.

I have chosen another disk to the outputs (overflow volumes) instead of the RAID (without it the render fails too), so it’s not being used for now, the disk cache even being disabled is set to the mac HD, and the final rendered file is being saved on another internal hard drive.

Checking the activity monitor, I noticed that only 1 aeselflink keeps opened after a while and this one doesn’t stress so much the processor and memory, while the AE app leeches aproximately 300% of processor. The strangest thing is that the 8-6 cores can be used in simple test project; would it be a plugin issue?!

Same plugins used in this project:
Magic Bullet Looks
Trapcode
Proanimator
Primatte Keyer Pro
Datamator
Red Giant Plugins…

I just instaled CS4, so I’m going to make some tests in it and I hope it goes better than CS3, but before migrating to CS4 need to check all plugins so this could take a while.

This thread even targets for Qmaster in AE and Render Engine in the same machine suggestions. Any help is welcome!

Thanks in advance.

Marco
BRAZIL

[Marco Cogumelo]

Hi Dave, thanks for replying and your help.

This video is for internet purposes and that’s why i’d misunderstood about the 30fps question.
I already knew that the NTSC is always at 29.97, and had even seen that sony EX software and final cut indicate the footages captured in 30p are playbacked in 29.97, so i just changed again to 29.97 and adjusted few keyframes and now they work correctly.

So now i would like to ask you another thing; something really awful that occurs sometimes (this project included). In my last render last night, when i set a render queue of another render using mov animation @ any resolution quality, the rendered file gets really strange. Some medias blink, some frames blink with color bars, as if they were offline, like 1 frame has been rendered correctly and the following one rendered an offline media. I noticed that this usually happens to mov files, which is awkward because i queue the same comp to render twice, and i get this in one of the renders, so this could exclude an offline media mistake.

If i didn’t make myself clear explaining this, i can upload a short piece of it.

Can you guys help me again? Is it possible to be another framerate or AE problem? Maybe I’m skipping a step that causes this hehe…

Thanks in advance!

[Marco Cogumelo]

Hello guys!
Thanks for all advises.
The problem was solved decreasing the Ram Cache Size to 55% and increasing the Max Memory usage to 120% and 18GB of disk cache….
Rendering performance is very slow, but it works.
I hope i dont have further problems with HD comps.

[Marco Cogumelo]

Hi RoRK thanks for answering…
I’m trying the following..
using the plugin KeyCorret Pro 1.0 and Primatte Pro 4.0.0 (but at AFX it shows as 4.2 version is that correct?), and Dearfactor, Primatte Keyer Pro 4.2, Edge Blur and Matte Feather EZ … when i try to render an ANIMATION CODEC without any effect, it works perfectly, but trying to render it using the native codec (XDCAM EX) without any effect, AFX suddenly crashes, but even with simple AFX effects like color keying or fractal noise, it crashes as well.

So, the fact is that afx can not render when any effect is applied to my comps.

The footages are .mov converted by XDCAM transfer, captured with an EX1 XD cam. The original ones are .mp4 files.