[Peter Berthet]

unfortunately thats the method id recommend going with too,
on large projects ive often had to selectively edit small amounts of media rather than bring everthing in (which i prefer) and doing it all at once

it (CS4) just seems to hit a brick wall when you have loads of media and sequences in one project 🙁

~Peter Berthet
Sydney, Australia

[Peter Berthet]

i think Pat probably saw the same presentation i did, they definately mentioned it was forthcoming, but i dont recall any date

~Peter Berthet
Sydney, Australia

[Peter Berthet]

its not related to CS4, its a problem with windows

from a windows tech support forum:

Here’s how to fix it:

Start -> All Programs -> Accessories -> right-click Command Prompt -> Run as administrator -> you copy and paste this:

net stop winmgmt
DEL C:WindowsSystem32wbemRepository*.* del c:WindowsSystem32WBEMRepository*.*

Restart the PC and let the system idle for several minutes.
There will still WMI warnings in the event log.
Restart once again and the error message and warning will be gone.

~Peter Berthet
Sydney, Australia

[Peter Berthet]

no problems 🙂

i think your correct on apple dragging their feet, the comments i read from adobes dev kinda hinted that apple werent necessarily enthused about the whole idea

~Peter Berthet
Sydney, Australia

[Peter Berthet]

i read something about adobe having to wait on apple to supply them with the backend for final cut before they could do this,

alternatively you can quite easily export an EDL from Premiere and import it into FCP then reconnect all your media

you will lose filters and the ilk, but all your cut points and transitions will be retained

~Peter Berthet
Sydney, Australia

[Peter Berthet]

sounds like there may be a problem loading your project file into AME, it may be corrupt.

try and open the project in premiere and save it as a backup project FIRST (make sure to name it something different because your about to become destructive!),
then delete any additional timelines and media that are unnecessary to the export (remove unused media)

once that is done make sure that the timeline you want to export is unharmed by the project trim, assuming everything is good. save the project and then try and export the timeline again

there are cases where large projects have problems loading in premiere and AME, by cleaning up your project and removing unused media it makes the project file smaller and less complex, thus lessening the chance that AME will take issue with it

hopefully that will give you some joy

~Peter Berthet
Sydney, Australia

[Peter Berthet]

before you go and blitz your installation try loading a backup of your project, its entirely possible that the project file is corrupt and simply wont load

~Peter Berthet
Sydney, Australia

[Peter Berthet]

PPRO appears to be more stable on mac as far as im concerned, we run it on a mac pro here and most of the suite works better under OSX

However id recommend leaning a little further towards FCP, and perhaps jumping in the pool.

Its got some kinks of its own, but it far outweighs CS4 in terms of comfort and stability

~Peter Berthet
Sydney, Australia

[Peter Berthet]

how large are your projects getting ?

if your doing stuff in HD are any of the problems similar to those described here : https://forums.creativecow.net/readpost/3/894260

its not uncommon that large projects = poorer stability , so i wouldnt write off your system too quickly

although i wouldnt disagree that a nice Mac Pro will lead to a happier and less stressful editing environment! 🙂

~Peter Berthet
Sydney, Australia

[Peter Berthet]

our project was a mix of DV and HDV, the media alone exceeded 600gig comprised of several hundred clips and about 12 sequences, the project file alone got to about 60mb in size

we ended up moving the media and an edl out of premiere and into final cut pro, where it loaded in about 2 minutes and never crashed (keep in mind the mac we used FCP on wasnt even close to half as fast as the PC we were using PPRO on)

your unfortunate in that some of your files were corrupt, on top of that CS4 seems to hate large complex projects, and the long load times seem to be associated with its need to index everything on initial project load (more media = longer load times)

as far as i can see adobe believe the software is working as intended, but i dont believe for one second theyve actually tested it under the sorts of conditions that you have described, in my experience it simply does not perform to a decent standard.

~Peter Berthet
Sydney, Australia