Forum Replies Created

Page 1 of 2
  • Ben Piercey

    August 9, 2007 at 7:15 pm in reply to: CS3 Multiprocessor rendering problems

    Are you asking in the context of AE CS3 Multiprocessing or NP2? If it’s CS3 then I’m afraid any response I give would be mostly speculation. It’s probably best that someone from Adobe address these concerns.

    That said, I’m not aware of any egregious lag issues with NP2’s preview so I will assume you are referring to AE CS3. If indeed NP2 is suffering from this, I’d like to get my hands on a sample project and have the problem fixed as soon as possible. Please let me know.

    > Also, is it possible to disable the function of auto-saving
    > before each RAM preview? That adds an interminable amount
    > of time to how long it takes to look at anything.

    In NP2 the project must be saved in order to ensure that background processes are providing valid frames. Imagine getting back preview results that didn’t jive with the layers and animation defined in your comp. That would certainly cause head-scratching and possibly fits of rage.

    Saving the project is a necessary artifact of the multiprocessing approach. I’d guess that AE’s MP would likely suffer from this also – but there I go … speculating… 😉

    Ben
    GridIron Software, Inc.

  • Ben Piercey

    August 9, 2007 at 12:43 pm in reply to: CS3 Multiprocessor rendering problems

    Hey Mike,

    The issue with intermittent color bars when referencing QT footage is a known problem with MP in AE CS3. Adobe is working on a fix. We have seen this happen with NP2 from time-to-time in CS3 also but we have put in measures to minimize its occurrence.

    Hang tight, the AE team is on top of it.

    Ben

  • Ben Piercey

    July 31, 2007 at 12:41 am in reply to: Crashing on Renders CS3 and AE7

    If you are not using multi-processing (either from Nucleo or AE CS3), I’d suggest that you tweak your memory prefs in AE.

    The default setting for image caches is 60% of physical RAM. It sometimes happens that your renders hit a point in the comp where the frame size is huge or the amount of cached data peaks to some crazy level where the default limits get exceeded.

    I’d try bumping that 60% number up to say 90% and see if your renders get any further. (you don’t need to change the one that’s set to 120% – just leave it)

    Even if this works, I’d still recommend dropping it back down to the default once you get through this crunch.

    If you ARE using multi-processing – forget everything I just said ’cause the rule change in that case :).

    Hope this helps,

    Ben Piercey
    GridIron Software

  • Ben Piercey

    July 30, 2007 at 4:39 pm in reply to: Nucleo Pro 2 is now available

    True, CS3 can give you improved performance for previews/renders, it does not allow you to do background or speculative previews/renders.

    Having peaked processors is nice, but being able to go back to work while you’re rendering, that’s where the real power is. That’s the message we get from our users.

    Ben
    GridIron Software

  • Ben Piercey

    April 11, 2007 at 7:56 pm in reply to: Nucleo & Blackmagic

    I wish I had an answer for you. Could you please send this question to our support team (support@gridironsoftware.com) and we’ll have look to see what’s going on.

    I assume you’re at 29.97 fps, no fields/pulldowns?

    Anyway – I’ll be sure to post the resolution once we find it.

    Ben
    GridIron Software

  • Ben Piercey

    April 10, 2007 at 2:36 am in reply to: Can AE utilize MAC PRO 8 core system?

    Yeah, my first suspicion was that it was fear-mongering, planting a seed of doubt in would be do-it-yourselfers. No way to know for sure but try it. It won’t be me though.

    Ben.

  • Ben Piercey

    April 10, 2007 at 1:56 am in reply to: Possible to have too much Memory?

    Actually,

    It will depend on whether you’re running a 32 or 64 bit OS. If you’re running 32bit XP for instance, the OS will be able to recognize up to 4GB total (minus some for OS function and PCI express “blackhole”). AE 7 alone on a 32 bit OS can recognize up to 3GB (with some persuasion. i.e. using the /3GB switch in the boot.ini)

    On a 64 bit OS the skies the limit if you are using Nucleo/NucleoPro or AE CS3. Both force AE to run multiple instances with each instance able to access its maximum memory(which I think is 3GB on both 64Win and OSX).

    If you’ve got multiple cores and a 64bit OS – go nuts on the RAM.

    Ben Piercey
    GridIron Software Inc.

  • Ben Piercey

    April 10, 2007 at 1:49 am in reply to: Can AE utilize MAC PRO 8 core system?

    This link might be of interest. It basically says the memory and drives for your quad might not work when attempting to upgrade to 8 cores.

    https://www.macfixit.com/article.php?story=20070409103051875

    Ben Piercey
    GridIron Software Inc.

  • Ben Piercey

    September 22, 2006 at 8:02 pm in reply to: [OT] Nucleo Pro discounted until Sept 30, 2006

    Oh yeah, some links might be helpful.

    Product information:
    https://www.gridironsoftware.com/NucleoPro

    Online Store:
    https://www.gridironsoftware.com/Purchase

    Ben

  • Ben Piercey

    March 30, 2006 at 2:02 pm in reply to: Purge All = instant CRASH. Was working last week…

    I’ve seen Trapcode Echospace cause that. I think they have a patch available for it.

Page 1 of 2

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