Activity › Forums › Adobe After Effects › Quad Intel and 7.0
-
Quad Intel and 7.0
Posted by Joshua Ferg on February 21, 2007 at 9:13 pmWe just dropped 9 grand on a new G5, Quad Intel 3.0 with 8 GB Ram, Boris and Nucleo Pro plug ins. Running with 7.0 and have had nothing but trouble – in fact it’s effectively inoperable. Crashing on RAM previews – with or without Nucleo Pro enabled or Boris. Read about the RAM issues and Rosetta – have dropped memory down so Memory and RAM combined are taking up only 700 MB and run AE without any other app in the background. All to no avail. Adobe’s been helpfull but claim they haven’t had similar issues -?????
Have fully researched all over to find a solution to the issue but still looking for a fix.
Any input appreciated.
Best,
JoshJoshua Ferg replied 19 years, 2 months ago 6 Members · 10 Replies -
10 Replies
-
Steve Forde
February 21, 2007 at 9:35 pmWhen you get a crash- is it just AE that hangs or do you see a kernel panic? Kernel panics happen when the whole screen goes a dim grey or black, and you see white text spitting out gibberish on either the right or left side of the screen. Only way to recover is to power cycle the machine by holding the reset etc.
IF so – then that is bad RAM.
IF not – please email us at support@gridironsoftware.com, and we can get you a diagnostic tool to help sort this out.
Steve
GridIron Software Inc. -
Joshua Ferg
February 21, 2007 at 9:41 pmSteve – Thanks for the response. It’s not the Memory – just the spinning beach ball of eternal happiness. Emailing now.
-
Morebo
February 21, 2007 at 10:01 pmI had a similar problem on a new Windows system going from SCSI disks to SATA disks. Don’t know if that might be the case for you, but going back to SCSI solved it for me. Seems to me that your problem is hardware related. Incompability between different hardware maybe? Graphics card, RAM or harddrives.
Do you experience the same kind of problem with other apps that require rendering?
morebo -
Joshua Ferg
February 21, 2007 at 10:03 pmWe don’t have a SCSI – Fiber Channeled to the RAID.
Don’t know where the confict would be on the hardware end – everything is out of the box from Apple as we’re not bringing the box on line with the Lhe Card until next week.
-
Nicholas Toth
February 22, 2007 at 2:50 pmWe have the same machine (3.0ghz…6 gigs of ram…some cool video card with a video game chick on it…), but we installed XP pro and are running nucleo pro on that end, with AFX 7 off a Raptor. Stability wise, it has its problems, but when it renders it is outputting renders that were taking 12 hours on my Core Duo laptop running XP pro in a mere 3ish hours. HUGE PERFORMANCE LEAP.
I’d run the windows end until AE comes out in binary. I’m kicking bootcamp to the curb as soon as that happens.
Nicholas Toth
Freelance Animator
nicholastoth.com -
Powerglove
February 22, 2007 at 2:56 pmI have the same problem on a MacPro 2.66 with 3gigs of ram.
I found a kind of solution. The problem comes when I rich the ram limit that I put on the preferences.
The Ram is not purge automaticly. The only way I found to solve this problem is to access to the secret menu. When you click preference hold down ctrl + shift and you will find the secret menu in the preference list.
In this menu change the purge refresh to 10 frames and this will be fine.
I don’t find any other solution for the moment, it’s a problem with after 7 and macpro.
Wait for after 8.
Regards
PowerGlove -
Joshua Ferg
February 22, 2007 at 3:36 pmGood advice – I heard that preview and exports should be sent through Nucleo Pro if availale.
I sent the purge frames option down to 1 but will push up as reccomended and see if that has any impact.
I think the real solution is dependent on Adobe getting 7.5 Intel native.
-
Kevin Camp
February 22, 2007 at 4:45 pmi experience frequent issues on a macpro (2x3ghz core duo, 6gb ram, 1tb sata raid), but i have traced almost all issues to cycore effects.
i have reached the ram limits on projects, and set the purge to around every 5 frames to remedy it. but when the ram limit was hit, i just got an error message, not a crash or freeze. so the spinning beach ball of death may be related to something else, and i might suspect the ram.
have you ran the hardware test from the osx install disc?
also, have you tried disabling opengl rendering in ae?
-
Kevin Camp
February 22, 2007 at 5:56 pmi just read about someone reporting an issue (on http://www.xlr8yourmac.com) with having both an ati and nvidia card installed in their macpro. they suspect there is a conflict between the drivers.
i actually still have the original nvidia 7300 card in my macpro, along with the ati x1900 xt… there is no display connected to the 7300, i just thought it was a safe place to keep the card (maybe connect an old crt at some point). but i think i’ll pull it and see what happens — i had disabled opengl in ae months ago when i started experiencing some issues, maybe it was a driver conflict…
which graphics card do you have?
-
Joshua Ferg
February 22, 2007 at 6:20 pmyeah – disabled Open GL and even attempted removing the GL Extension to no avail.
Per your post – I’m pretty sure the issue is with Boris Continuum Effects – psrobobly all non-native effects within AE. They’re more intensive and weather it’s a case of the effect pushing the Memory or processing limit to it’s limit on Intel machines faster or not, I don’t know.
Running the Radeon for graphics – don’t think it’s a hardware conflict. Just think it’s the architecture in teh application having to run through Rosetta to process.
Very hopefull that 7.5 will address the issue and re-engineer the application to be intel Native.
The reccomendation to run the Windows version via bootcamp is looking increaingly attractive….
Reply to this Discussion! Login or Sign Up