I am using the latest version of AME. When I try to convert a batch of several .m2t files to QuickTime h.264, AME just disappears. No warning, no "report a problem" box, nothing. The app just crashes. So instead of being able to load up a bunch of files for conversion overnight, I'm having to spend all week baby sitting this POS. Any ideas?
I don't seem to be able to located any resolution(s) to AME crashing, why it seems to crash so much on a variety of systems and what people are doing about it. I am using a project that was created using premiere pro 2.0 and opened into CS4, project had no problems in Pro2.0 on any machine.
So here's my dilema with as much details as I have.
So there it is in mostly a nutshell, I have three machines with varying architectures, and OSes, all of which cannot render the full sequences using AME from a Pro2.0 project. Any Ideas?
If I have neglected to post any relevant information, I will be happy to supply. Thank you in advance.
2 partions c ~100GB, d~500GB, portable drive~300GB (where movie project and data are located), main drives are raid0
Sorry, I don't understand this. Do you have ONE physical drive that is partitioned? That is a bad idea. How was the raid set up? What physical disks were involved? What is the connection/interface to the portable drive?
If you encode a 14 track timeline from an external drive to the same external drive at this resolution with TIFF's it could very well be your disk setup may be causing problems, especially if it is a USB device.
I beg your pardon for the confusion;
I have two physical disks each 320GB, in a RAID 0 configuration, then this "single disk" (at least as far as the OS sees) is partitioned into drives C:\ 100GB and D:\500GB. On the two other machines I tried to run on, they were single partitions per physical disk (for e.g. disk 1 was a 160GB wd 10,000rpm drive).
The portable drive is a SimpleTech USB 2.0 drive; it contains all the project data.
Thank you for the suggestion, I will move the project to a local disk and re-attempt the rendering. I am curious why rendering worked with Pro2.0 but CS4 AME I get errors when using an external USB drive?
Additional details from this mornings crash.
I copied the project to my local physical disk, on my D:\ drive, only to fail to complete the full sequence render again.
"PProHeadless.exe - the exception unknown software exception (0xc0000005) occured in the application location 0x02F518cd". this is what i have witnessed on three machines now.
with the details for the crash report indicating that titlecharaterfactory.dll is causing the fault.
What is titlecharaterfactory.dll? and why might it cause AME to crash?
I had forgotten; Yes, the PRO2.0 project used a legacy FONT NewsGothic - this was installed by copying font to the
I have tried to remove the font, but CS4 still seems to find it??
Is there a method for changing all titles in a project to a new font?
Just guessing here. Set your workarea bar to the first half of your timeline and try exporting that. Repeat that for the second half of your timeline. Does it fail on both halfs or is one OK? If the latter, then there is a problem with one of the TIFF's or there is maybe blank space in your timeline, causing this fault.
I have split the timeline; rendering in "halves". I had the beginning half fail, so split that and rendered the quarters, both quarters completed successfully.
I have titles that span the entire sequence, so there are no blank spaces (none at least that I have been able to see thus far).
Are there any methods to detect bad/faulty tiffs?
For locating "gaps," I find that zooming in on my Timeline and then hitting PageUP, or PageDN, steps through each Clip. Watch the CTI. It should flow in perfect increments for each Clip. If it judders, or "hiccups," you likely have a gap. If you are zoomed in to max., you *should* be able to see it, but I've found a few that I just cannot see. At that point, you can do one of several things, depending on what your Assets are, and what you want. You can extend the Tail of the previous Clip by one frame, or the Head of the next Clip by that amount. One could also add Black Video, but you'll probably want to increase the gap and add Dip-to-Black before and after it.
As for the TIFF's, I'd check their sizes first. Unless you need to pan around a zoomed out image, they do not need to be much larger than your frame size, say 720x480, or whatever. I cannot think of any way to "test" for bad TIFF's, but maybe someone else will teach us both.