Replies – Forums – Daniel Johnson

Forum Replies Created

Daniel Johnson
February 23, 2011 at 10:49 pm in reply to: Upgrade Ram = Slower Render?

Just want to follow up on this thread. Following this advice solved my problem:

top riser:
slots 1 & 2: 4gb (matched pair)
slots 3 & 4: 1gb (matched pair)

bottom riser:
slots 1 & 2: 4gb (matched pair)
slots 3 & 4: empty

Thanks for bailing me out of that one!

Dan
Daniel Johnson
February 14, 2011 at 3:48 pm in reply to: Upgrade Ram = Slower Render?

I moved the slider back to the middle, and the issue is still there.

I have been running cs4 with 10 gb of ram and have had all 8 cores and my ram being used to the max. From what I recall cs4 can use up to 4GB per core. I am only using 2.5GB. So I don’t think 64bit is the issue.

Maybe I am not understanding you. My machine was working fine with 10GB of ram. Now it barely works at all. If it is a setting problem then what is it? Hmm…
Daniel Johnson
February 14, 2011 at 3:34 pm in reply to: Upgrade Ram = Slower Render?

I just set my settings to :

ae memory: 10gb
ram for other apps: 6gb
Cpus to leave for other apps: 4

That means I have 2.5 GB for each core being used for ae correct? When does a ram preview stop? In my experience it stops when it a) hits the end of a composition b) has an error c) or it runs out of ram. I should have 10 gbs of ram to preview with and it is only using less the one GB which previews about a second or so? I am not getting any errors, and I am previewing at the beginning of my composition. It makes me think there is something wrong with the ram… any other thoughts anyone?
Daniel Johnson
February 14, 2011 at 2:50 pm in reply to: Upgrade Ram = Slower Render?

I have mini stats for my processor, hard drive, and ram and just noticed that the ram is capping out at few gigs with about 10 free! I tried a ram preview a number of times and it keeps stopping after just a few seconds (and a couple of gigs active/wired in the ram). Maybe the different branded ram is not compatible with each other?

I tried taking out the smaller 1 gig sticks. Still not using the rest of the ram. So is the lesson I am suppose to learn: don’t mix different ram brands? Or could it be something else?
Daniel Johnson
February 14, 2011 at 11:12 am in reply to: Upgrade Ram = Slower Render?

Here is how the ram is distributed:
Riser B1 1 GB
Riser B2 1 GB
Riser A1 4 GB
Riser A2 4 GB
Riser B3 empty
Riser B4 empty
Riser A3 4 GB
Riser A4 4 GB

So are my 1 GB sticks in the pair causing the problem? I would rather figure out the issue first rather then just upgrading to see if it changes anything. Thanks for the thoughts though.
Daniel Johnson
November 4, 2010 at 6:33 pm in reply to: Recommendations for Current System

Thank you so much for responding Walter.

Couple more questions:

1) Do I need to update to CS5 before or after I buy more ram? I though cs4 capped out at 4gb of ram or something?

2) I have read through that adobe page in the past. Some info though caught my eye this time around:
“Ideally, use three fast local disk drives: one for source footage files, one from which the application runs, and one for rendered output.” So does this mean I should keep my ae project file AND assets on a separate drive? I heard once that at least the project file should be on the same drive as the os. Could be wrong?

I was aware of the ram issue. I was planning on that upgrade, but wanted to make sure that was the best route. I have a heavy project I am working through and I am having to render some of the compositions separate and piece them together since it is bogging me down so much. Heres hoping I will make it through 🙂

Dan
Daniel Johnson
November 9, 2009 at 3:09 pm in reply to: AE: not enough memory to create memory for blurring.

For anyone who reads this later. Here is the finished version:
https://www.vimeo.com/7488781

I ended up re-structuring the comp so that the giant “images comp was down to a decent size (2000x2000pixels or something). I then parented a low resolution image of the rest of the photos to the logo after the zoom began. I also maxed out my imac to 3 gigs (added 1 gig). Thanks again for all the input.

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.
Daniel Johnson
November 5, 2009 at 4:31 pm in reply to: AE: not enough memory to create memory for blurring.

Okay so I am trying to render my “images” comp, and it has an estimated 5 hours which sounds pretty decent. Hopefully this is the end of my troubles on this project. Thanks Dave!
Daniel Johnson
November 5, 2009 at 4:20 pm in reply to: AE: not enough memory to create memory for blurring.

The client is a little flexible on the deadline. It may get kicked over to another machine, but I would still like to do it if I can (10 hours?).

All the stills are in one giant “images” comp with the camera and motion blur happening their. Would rendering just the image comp really save me any time?

Update: I was able to get over the hump I mentioned earlier by turning off the depth of field for the camera ( which was set to default), but the current render is currently estimated at 15 hours… and it hasn’t even hit the heavy animation portion.