[Peter Berthet]

good to hear actually, were looking at building a new core i7 based machine in our office soon

the old AMD quad core is gettin a bit ..well.. old

~Peter Berthet
Sydney, Australia

[Peter Berthet]

Apparently i missed the part where there was no point to rendering my timeline… Sigh.

Hidden away in the export window theres a tiny little button that says “Use Preview Files”

This tiny little button is by default set to NO!

So i clicked on it and made it YES

Suddenly instead of re-rendering my entire timeline on export AME is now using my (already rendered) timeline and just exporting it to the hard drive like it should’ve in the first place! In 20 minutes.

Why something that can have such a huge impact on the users time is hidden away and kept a secret is beyond me.

Why the option is even there is a bit weird.

One would think that AME would load the project and go “ooooh look here are some render files, i can save lots of time if i use those instead of doing the job twice!”

..Over it.

~Peter Berthet
Sydney, Australia

[Peter Berthet]

the system drive is generally your C: Drive
(the drive where your OS is located)

its also not a very good place to put things other than program installations, as the drive is constantly being read and written to
so corruption of data blocks can occur

its good practice to keep your media and projects on separate drives to your OS (

~Peter Berthet
Sydney, Australia

[Peter Berthet]

True that,

as i understand it EFI-x dont condone the installation of OSX on PCs, yet they enable it .

Oh well 🙂

On a little fun note, the wording of the EULA for leopard states that OSX cannot be installed on “non-apple BRANDED” hardware

you know those apple stickers you get with macbooks ?

…if you catch my drift 😉

~Peter Berthet
Sydney, Australia

[Peter Berthet]

i had the same problem and had to reload an autosaved version of the project because the working version had become corrupted

could be that your system drive is faulty or in need of a defrag if its happening a lot?

~Peter Berthet
Sydney, Australia

[Peter Berthet]

Something you should take note of, while hackintosh installations are fun. Theres nothing about them that is legal.

Its a breach of the Leopard EULA to install it on non-Apple hardware.

~Peter Berthet
Sydney, Australia

[Peter Berthet]

i actually got the warning a few days ago when rendering a 7 minute 1080i timeline.

i believe their definition of ‘memory’ in this case is available hard drive space rather than RAM

instead of changing the optimization to memory, i changed the scratch discs to an empty external SATA drive and it happily rendered away.

it was running out of ‘memory’ because it was trying to render using an (almost) full system drive

~Peter Berthet
Sydney, Australia

[Peter Berthet]

thought id follow this up with some hard numbers for anyone thats interested.
currently doing a 10 minute render on premiere using 8gb of RAM on a core 2 machine

premiere is sitting on 1.4Gb
After FX 977Mb
Importerprocessserver 1.04Gb

essentially its sitting just under 4Gb of RAM in use despite there being another 4 it can take advantage of.

The default settings under Vista 64 allow 32bit apps to address a maximum of 2Gb
They are however assigned 4Gb of Virtual Memory (paging) but 32 bit apps often dont know what to do with the extra space
so in theory i can fire up 4 heavy 32 bit apps and use all 8gb of RAM

but the performance gains for using one app at a time (premiere) are rather limited due to the fact that they are only 32 bit

~Peter Berthet
Sydney, Australia

[Peter Berthet]

essentially what vista 64 does, … cause its an evil resource whore
is it will take more and more RAM depending on how much you feed into it.. essentially dynamically increasing its background footprint based on the resources available

after testing for a few hours last night i found that i could run multiple adobe packages at once, and 64 bit allowed me to give each of them up to 4Gb of RAM (same as 32 bit)

the exception was photoshop, which due to it being true 64 bit, managed to eat up to 7gb after i loaded a bunch of huge .psd files into it and started running multiple filters at once

the information you have bob, is correct.

the benefits will arise when your doing things like dynamically linking between multiple adobe apps, and each of them can take a piece of the pie
but premiere alone wont gain any extra performance from the excess ram (above 4Gb) because it cant address ALL of it on its own.

the real benefit is that the other 4Gb of RAM is left aside for Vista to run background processes, also the other adobe aps such as processserver and the background loaders can address this 4Gb independantly, so loading premiere has less of a performance hit on your entire system.

As far as all the tests ive been doing, i strongly believe that RAM is not the magic solution to faster editing with premiere, although it does help to have 8gb running on a 64 bit system (especially quad cores. 4×2 =8Gb the magic number, 2Gb per core!)
A faster CPU and Quicker harddrives will make your programs and editing work faster in my opinion.

The next purchase i make is going to be a solid state hard drive (for the OS and apps) and a newer core i7 system.

So essentially.. RAM helps to a point, but until CS4 is true 64 bit, your going to see more direct performances increases by having a super fast drive to load your apps from, and a big quick RAID for your media, backed up by a quad core CPU and THEN some ram to compliment your CPU.

The performance difference with that sort of gear is quite significant.

~Peter Berthet
Sydney, Australia

[Peter Berthet]

ill have to disagree, the only program in the CS4 package that supports full 64 bit operation is photoshop

the only other benefit to running under 64 bit is, as vince said support for larger amounts of ram

as far as premiere goes, ive been testing this week and didnt see a noticable difference between 4G and 8G in premiere, however adobe media encoder does perform faster with larger amounts of ram

ill say again though, ALL adobe software with the exception of photoshop are 32 bit applications, all they support is multithreading under a 64 bit OS

you will not see true benefits of a 64 bit environment in any package except photoshop 64

~Peter Berthet
Sydney, Australia