Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Available RAM in System Settings Incorrect…?

  • Available RAM in System Settings Incorrect…?

    Posted by Judy Singh on December 2, 2009 at 3:18 pm

    Hello,

    I’ve installed some new RAM a while back to bring my system up to 6.5GB. (see below for system specs) The system profiler shows the installed RAM and so does the activity monitor, however, I’ve notice FCP hasn’t seemed to be running any differently. When I look in the system settings it shows 100% of the application’s memory usage allocation to be only 2560 MB – what it was before we added the new RAM.

    I’ve read several discussions surrounding RAM, vram and how to monitor their allocations but I have yet to find anything that addresses RAM being recognized by the O/S but not an application.

    For the record, I checked in Photoshop and After Effects as well and both show only 2.5GB of RAM available as well.

    Anyone know why this is happening and how to fix it?

    Thanks!
    Judy

    Power Mac G5 Quad 2.5 Ghz (11.2) (Pre-Intel)
    6.5 GB RAM
    OS X 10.4.11
    FCP 5.1.4
    Episode 5.1.1
    DVDSP 4.0.3

    — experience is tough teacher
    she gives the test first
    and the lesson afterwards

    Matt Lyon replied 16 years, 5 months ago 4 Members · 4 Replies
  • 4 Replies
  • Mark Maness

    December 2, 2009 at 3:26 pm

    [Judy Singh] “When I look in the system settings it shows 100% of the application’s memory usage allocation to be only 2560 MB – what it was before we added the new RAM. “

    This is correct. Most apps on a Mac will only use up to a maximum of 2560 MB, including Final Cut Pro. There is nothing wrong with you system. More RAM will allow you to run more programs at the same time.

    [Judy Singh] “Anyone know why this is happening and how to fix it? “

    There is no fix for this as of yet, or is there a need to fix this. Hopefully when Apple releases a fully 64-bit OS, this may be addressed but for now, it works just fine.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Judy Singh

    December 2, 2009 at 3:45 pm

    Wow! Really?? Who knew?! I certainly thought adding more RAM would help my applications run faster in ADDITION to my system – which also doesn’t seem to be running any faster either incidentally….

    I often get the “preparing video for display” msg when there really isn’t anything complicated going on and after reading more about that, I thought it was definitely a RAM issue.

    Ok, well thanks so much for your prompt response.

    Power Mac G5 Quad 2.5 Ghz (11.2) (Pre-Intel)
    6.5 GB RAM
    OS X 10.4.11
    FCP 5.1.4
    Episode 5.1.1
    DVDSP 4.0.3

    — experience is tough teacher
    she gives the test first
    and the lesson afterwards

  • Zane Barker

    December 2, 2009 at 4:26 pm

    [Wayne Carey] “Hopefully when Apple releases a fully 64-bit OS, this may be addressed but for now, it works just fine. “

    Its not the OS Apple already has a 64 Bit OS (Snow Leopard). Its the fact that FCP is NOT 64Bit it is still 32 Bit.

    There are no “technical solutions” to your “artistic problems”.
    Don’t let technology get in the way of your creativity!

  • Matt Lyon

    December 2, 2009 at 6:16 pm

    Do you have lots of still images in your timeline? Final Cut will give the “preparing video…” progress bar when it is caching your stills into RAM for realtime playback. You can actually stop this by setting the “still frame” cache to 0 … but then you’ll have to render all your still frames (which may be less annoying, depending on your workflow).

    I deal with this every day when I’m assembling animatics … it can be super frustrating! Especially because it doesn’t take much to cause FCP to want to re-cache the whole timeline.

    Matt Lyon
    Editor
    Toronto

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy