Graham Jones
Forum Replies Created
-
Hi,
Thanks for your post and comments. it’s all about memory… Rosetta gobbles an indordinate amount of it, and you don’t always know how much it’s taking. Universal apps use memory too, but they are slimmer and it is more obvious how much memory they are using.
So… just because you kill all the PowerPC processes, doesn’t mean you can have 25 Intel apps open and not run into issues. However, I wouldn’t worry about small stuff like Dashboard, as long as you’ve killed the PowerPC processes and don’t have too many other things open.
– Graham Jones.
-
Hi,
have you followed the thread and tried everything? Workspaces? Prefs? Permissions? Offending Quicktime components?
Keep in mind that at best this is a workaround and unsupported solution. You obviously spent a lot on this system… I hope you did not try to set up a production system based on an unsupported software configuration…? You can’t curse a system that is not supposed to run at all on your system. Try that with Avid…
AE 8, on the other hand, which is designed from the ground up to be compatible with Intel Macs and PPC, will be out soon. Until then, you may need to get a Gridiron plugin for previews and/or do your renders on a PPC system.
Good luck,
Graham Jones. -
Hi,
Thanks for your detailed response. I suspect you have a little more flexibility with the RAM because of having 4GB installed. It seems 3GB and less really cramp the headroom on Rosetta apps, but 4GB and above give more flexibility. I’m not sure it’s proportional… there may be more at work behind the scenes.
– Graham Jones.
-
Hi abondanzieri,
ha ha, too bad, I could have used another Mac Pro!
A great piano player can play an old piano and still sound great… he quickly learns which keys are the bad ones and figures out a way to adapt and play the same song with different keys.
I’d take notes on which filters are causing the issues (posting here wouldn’t hurt). Even on a G5 I wouldn’t touch the Ripple filter with a 10 foot pole, for example. My bet is that you can work your way around the bad ones until AE 8 gets here.
Cheers,
Graham. -
Hi,
If you used Migration Assistant, I recommend something you probably won’t want to hear— format the entire drive, then re-install the system from the system disks, and your apps from their original DVDs.
I tried the migration assistant, and learned the hard way — really, it should be intuitive, but especially for pro apps there are a lot of little tiny files written all over the place, which relate to a particular hardware’s architecture. A Migration Assistant works for a consumer with modest needs, when the CPU type is the same. However, if you are moving from one type of hardware to another… I would not recommend it. Nor would Apple— they were the ones who told me not to do it and why. I’m not sure why they don’t make this more explicit in their documentation.
Your memory settings will not affect the app launching. Once you get the app launched successfully, I suggest you try AE’s excellent online help for how to adjust the memory settings.
Hope this helps… Please post back with your results.
Thanks,
Graham Jones. -
Hi,
I’m just curious, did you migrate the system’s files from an older Mac? I made the boo-boo of using Apple’s “handy” Migration Assistant when I got my new Mac Pro, and had problems with lots of apps. I finally had to format the drive and do a fresh install.
If anything came from an older Mac, you may wish to delete everything Adobe-related and re-install. Wouldn’t hurt to do regular maintenance stuff like repairing permissions, deleting system caches (try Tiger Cache Cleaner), etc. Also, don’t rule out bad RAM, or another hardware conflict.
Also, have you checked the Console log? This is available in your Applications/Utilities folder. When a program crashes, information relating to the crash is written to this log. Try clearing the Console, and then running AE— see what pops up.
Please check back in with more detail, especially the Console information.
Hope this helps,
Graham Jones. -
Hi,
Sorry, I meant that past post for “abondanzieri”, not “djackson”, but I realize it may not be clear depending on your thread view prefeerences who that was addressed to.
For djackson… have you tried rendering with certain filters on or off, and checking the other things like Quicktime components and workspaces?
Hope this helps,
Gaham Jones. -
Hi,
Have you read the resources thoroughly? It’s not a guaranteed solution, and there may still be some factors (like a certain filter that may cause crashes on Intel Macs despite the workarounds). However, I am happily using a Quad 2.66 Mac Pro with 3GB RAM for production use of AE 7. So far, my Intel-native apps are crashing far more than AE. I wouldn’t characterize it as slow… it is faster than the Dual G5/2.5 with 4.5 GB RAM that I use at my main client’s suite.
I would suggest you read all of the resources mentioned here very thoroughly, and take the time to do some testing. And if you’re really dissatisfied with your Mac Pro 3.0 I’d gladly take it off your hands… 😉
Hope this helps,
Graham Jones. -
Hi,
make sure you also follow the advice at the top of the thread regarding looking for offending Quicktime components, workspaces, permissions, corrupted prefs, etc. Then I would do a test where you force quit all PowerPC processes, set your AE memory settings to 15%, and see if you still get the crashes.
At that point, I would check to see what filters you are using… in AE 6.5 I had nothing but crashes with the Ripple filter, for example. It might be one particular filter (or combination) that is causing crashes.
Please report back on what you find.
Hope this helps,
Graham Jones. -
Hi,
Thanks for your post. I’m a little confused… what are the render times if you set the secret pref to 1? I gather from your finished renders that you don’t experience crashes with your memory set to 30 or 40%? And have you tried lower memory settings like 10% or 20%? Are you watching Activity Monitor to see what’s going on while you render?
Thanks,
Graham Jones.