[Graham Jones]

Hi,

see my article for a possible fix:
https://forums.creativecow.net/cgi-bin/new_page_wrapper.cgi?forumid=%3CFORUMID%3E&page=https://www.creativecow.net/articles/jones_graham/AE7_on_Intel_MacPro/index.html

Hope this helps,
Graham Jones.

[Graham Jones]

Hi Steve,

Thanks for your detailed and informative comments. It’s great to understand a little better why my theory is proving successful, and that people have further options available with Nucleo. I actually would have bought it first, but cash is tight, so was driven to find a free solution. I hope you sell a lot of copies now that people know that there are sound reasons that it helps the issue.

Hey, I think it would be a great idea for you to solicit a test group of some kind, to quantify and test to what extent Nucleo can help, and also what are the ideal memory settings for the best performance. In your experience, is Nucleo working in all areas with AE7 on Intel Macs? I know you wouldn’t want to say “we are the official solution” when even Adobe is shying away from supporting the boatloads of people who want to make this work. However, unofficial solutions are great to have!

Just a thought,
Graham Jones.

[Graham Jones]

Hi Greg,

Thanks for responding— that’s great news. Who of us would have thought that reducing memory would bring faster renders? 😉

Cheers,
Graham Jones.

[Graham Jones]

Hi Greg,

how did it go?

And has anyone else tried this? I’d be curious to know your results. If we pool our resources, I think it’s pretty likely we’ll get AE7 working 100% on Intel — just don’t tell Adobe!

Incidentally, if this doesn’t do it for you, I gather from some web research that most reasons for AE7 not working on Intel stem around memory issues, except for a couple of Quicktime conflicts I have seen (Popwire WMV components and some Avid components may need to be removed from /Library/Quicktime).

Hope this helps,
Graham Jones.

[Graham Jones]

Hi Greg,

If my theories are correct, you may want to set your percentage even lower… the key is to not break the 1.5GB barrier, and allow for a little headroom. For me, 50% of 3GB (1.5) did NOT work, but 30% of 3GB (0.9GB) DID work… so for your 4GB, you may want to try starting with 25%.

Of course my theory may be off, so you may want to experiment a little, and please make sure to post back with your results.

Also, don’t forget to open Activity Monitor and quit any non-Intel processes you don’t need.

Hope this helps,
Graham Jones.

[Graham Jones]

Hi,

I don’t think more RAM over about 3GB would make much difference, as it seems Rosetta hits a memory ceiling at around 1.5GB.

NEWS FLASH:
I just finished rendering the same comp on my Dual G5/2.5 at work, now with AE 7.0. My Mac Pro renders it 40% faster, despite having less memory, and the memory settings severely limited! Here is the full set of banchmarks:

AE 6.5, Dual G5 2.5/4.5GB RAM: 53 min, 34 sec.
AE 6.5, Mac Pro Quad 2.66/3GB RAM: 54 min, 44 sec.

AE 7.0, Dual G5 2.5GHz/4.5GB RAM: 39 min, 36 sec. (AE memory set at 100%)
AE 7.0, Mac Pro Quad 2.66/3GB RAM: 24 min, 21 sec. (AE memory set at 30%)

Yippee!

Just remember: THIS IS NOT A GUARANTEE THAT IT WILL WORK FOR YOU. It is an UNSUPPORTED solution.

Hope this helps,
Graham Jones.

[Graham Jones]

Hi Charles,

Thanks for responding.

A thread from early this year said that Flip4Mac was working with Iodata on this… I guess I’ll follow up with them, as I just dropped $150 on their HD Studio for the sole purpose of encoding for the LinkPlayer, and it’s wasted cash for me if it doesn’t work!

Thanks,
Graham.

[Graham Jones]

Hi Charles,

Thanks for responding. Oh well, that’s about what I thought. Just thought I’d check.

– Graham.

[Graham Jones]

Hi guys,

I just got a Linkplayer, and am having the same issues with Flip4Mac HD content— I have tried all of the setting options in Flip4Mac, and none of them play in my Linkplayer whether over the network or off a DVD-ROM.

Did anyone figure this out yet?

Thanks,
Graham Jones.