This content has been marked as final. Show 13 replies
How about providing some specific information about your footage, installed codecs, workflow, hardware, etc???
Lotsa dvsd footage. PAL, I got all the codecs I need, that's definitely not why it crashed. I have windows xp sp3 installed on a macbook pro and umm... 2gb ram ddr2 I guess.
Hope that helps
>I got all the codecs I need, that's definitely not why it crashed
Is it possible you have too many codecs, with some possibly causing a conflict?
What format and codec are you using for export?
When, exactly, does the crash occur - just when the AME opens, after the sequence is queued, after you start the queue - when?
Which app is crashing? Premiere? AME? Both?
Do you get any error messages after the crash? What do they say?
I don't think I have too many, I only have those necessary for my work.
I always export with a lossless. Lagarith or Huffyuv, in this case Lagarith. And it is AME that crashes when it is loading up, and no error message that gives me any information. Just that it has crashed.
Try launching the AME by itself (with Pr closed). What happens? If it works, load your Pr sequence through the File menu.
If it doesn't, try creating a temporary new administrator account. Log on to the new account and try first launching the AME, and if successful, Pr. Then try exporting again.
And if all else fails render your project in After Effects.
may i ask why you are running windows on mac? you may have more joy with the mac ver of cs4.
thanks for all the replies, you guys really saved my skin now^^
I launched AME, not via APP, and that worked. I can't believe I have been so idiotic not to try that.
I tried exporting it via AE, but my laptop crashed and I got this really fancy blue screen, but I found out that exporting with AE has a 75% change of failing. So if I keep trying, eventually it will work.
I have used windows all my life, I know how to use it so well and I have so many programs for encoding and demuxing inside XP that I don't think is available for macs. I feel more comfortable using XP SP3, but I will eventually start using OSX more when I get a hold of some more software. I have always loved Color, Shake, Motion and FCp. ^^
Thanks again. Seems that I will meet the deadline after all
I had regular crashes with AME too when launching it. I tried lots of things but uninstalling QuickTime (even though it was up to date) and reinstalling it seemed to help the most. It doesn't crash nearly as much now. :-)
Something else to check is to make sure that there are no 3rd party plugins installed for AME. Check the path at C:\program Files\Common Files\Plug-ins\MediaCore to (A.) see if this path exists, and (B.) if there's anything residing there.
If the path exists at all it means that some 3rd party installer added it to put a renderer in for AME. Pull out whatever plug-ins might be in there and try launching again. RapiHD created a plug-in that was compatible with 4.0, but crashed with 4.01. This is now fixed, but there may be others out there that have the same problem.
Just something else for your bag o' tricks
>RapiHD created a plug-in that was compatible with 4.0, but crashed with 4.01. This is now fixed
How is this fixed if the last update was 4.0.1?
they changed the plug-in to work with the Adobe update. In was in the update read me they posted on this forum.