This content has been marked as final. Show 6 replies
is your HDD FAT or NTFS formatted?
try using PNG codec, Foto-Jpeg or Motion Jpeg at 100%
PNG is uncompressed and handles alpha as well.
the two last Jpeg codecs leave you with a more reasonable file size and you won't see a difference in quality compared to animation codec which uses much more ressources for ENcoding and DEcoding.
Also i recommend buying a license for sheer video codec http://www.bitjazz.com/en/products/sheervideo/index.php
it's an amazing algorhytm they use for ENcoding video.
but, as for any software, it could be a bug in media encoder.
by the way: as you're running vista 64Bit with 4Gig of RAM read the comment at the end of this Livedocs, may it will increase your render power.
AME is twitchy on Macs and PCs. Beyond that platform wars are pointless (which you can quote me on to your friends). PCs can just be as easy to use and reliable. Specific to your problem you may simply run out of RAM. Unlike AE, AME is fully multithreaded and in addition loads large chunks into RAM to do its analysis for compression, sometimes it attempts to load the entire file. I would assume that this frame lookup makes it go *poof*. Whether this can be considered a bug is an open question, it certainly is not always desirable. In your case you may be able to get better behavior by adjusting the processor affinity in your task manager to tone down the "aggressiveness". short of that I'm not aware of any other workarounds, AME does not provide any performance tweaking itself.
Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
This being said, it scratches out most of the RAM overload thoughts with AME.
The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
Quite possible that it isn't handling the PAR stuff correctly. Since I almost always use squarified output, I guess it never occurred to me that this could be a problem... Sorry for the inconvenience, we really should have tested this more. Would be nice if you could file your findings to the bug report form, so it gets added to the internal development databases.
Hi Mylenium, thanks for follow up. Will test a little more and confirm but from there will post info to the bug report. 2 quick questions if you don't mind:
1. Where would I post this info in the bug report. The bug report, like the forums for support here at Adobe, don't seem to include a pull down for the Media Encoder.
2. Question for the process you use for squarifying Quicktimes out of AE. I have had a couple projects come up where the output will be played on a (what would I guess now be called a "classic" standard def) widescreen monitor with a 1.21 pixel aspect ratio. Because of this, I like to work in the Widescreen aspect ratio comp setting in AE. It's helpfull to use the preview toggle to jump between what I will actually output, versus how the widescreen monitor will display it.
So ultimately I'll export a 720x480 Quicktime. This is displayed as square PAR on my comp screen when played back in QT, as it should. Going to the Movie info within quicktime does not reveal any PAR metedata. But when I take that exported file and input it into AE, it interprests that file as having a PAR of 1.21. AE is correct in this, somehow there must be some metadata in the file that AE leaves in it.
But the point of me saying all this is how can I export a Quicktime (this also occurs with No Compression AVI's) without having that PAR data attached to it?
Thanks for your help,
Can I jump in here with an AME problem (I think) - I have tried using it to render out an After effects project, setting H264 but the AE comp has an alpha channel which when rendered out of AME is black (background in AE project comp set to white) any advice please Regards Roger