[Scot Mccann]

Weeellllllllll……..

I’ve just had a guy tell me that his soundtrack won’t breach copyright because it was recorded in the Vatican in the mid 1600’s.

I wonder if the audio engineer was also infallible?

[Scot Mccann]

Guys, blame Adobe. And Microsoft! I have had every problem ever listed on one of these forums since going to Vista64 and Premiere CS4. And my system is a dual Xeon HP XW8200 with 16gb RAM and Matrox AXIO HD installed, connected to a SAN via fibre. And the system was integrated by a Matrox/ Adobe certified reseller to their specs. In other words, a professional broadcast suite.
Nonetheless, you just can’t win. My best advice is enable PAE mode to map as much hardware above 4gb as you can, assign Premiere realtime RAM priority, and keep your projects as small as possible.

And then pray. Or move to Avid 😉

[Scot Mccann]

For anyone having this issue on CS4, I’ve just been through it and it’s a pain.
Basically, Premiere tries to use RAM from the system addressing space- the same as every hardware board & windows app on the machine.
It’s especially confronting when on a 64 bit platform. Essentially, the bigger the premiere project file, the more likely this problem is to surface. HD footage compounds the problem by not only making the project file size bigger, but by taking more CPU & RAM allocation when playing out & rendering.
I have recently had this problem with a 24Mb project running on Vista64 with a Matrox AXIO HD installed. When running XP Pro I would encounter the error on standard def projects 6Mb and larger.
Best workaround was to turn off as many processes as possible in task manager, and assign Premiere realtime access to RAM. And then reduce the project size!
I also enabled memory remapping so that some devices could load above the 4GB addressing area, as I’m running 16GB RAM with Vista 64.
These links might be handy-
https://www.pcstats.com/articleview.cfm?articleid=2238&page=21
https://www.pcstats.com/articleview.cfm?articleid=2238&page=21

Hope that helps someone.