Will AME 6.0.1 ever be fixed?

Question

So my computer just wasted the better part of the last 72 hours of its life.  I've tried multiple times to export an AECS6 composition under different settings, and keep getting encoding failures at random places.  And I'm seeing a lot of this same thread, "AME CS6 fails encoding."  It seems this has been a problem ever since the 6.0.1 update back in May (http://forums.adobe.com/thread/1004823?start=0&tstart=0); fast forward three and a half months and Adobe still hasn't fixed these problems (http://forums.adobe.com/community/ame?view=discussions).
I'm having the same problems everyone else is; AME will render for a bit, and then the same "dead goat"/sheep bleating will alert me it failed.  In my case, I'm trying to render out an AECS6 composition; I tried using the Vimeo HD1080 23.974 present, the YouTube HD1080 23.974 preset, and I even set up my own custom preset for 1080p 60fps.  All failed to encode.  And on top of it, AME doesn't even give me an error log!  I just get the goat/sheep and a grayed out object in my AME render list.  How am I supposed to know what's wrong (and tell Adobe Support what's wrong) when I don't get an error log?
And to make matters really worse, I don't even get a file.  While rendering, I see the temp files AME is making in my output folder; then the goat dies and the files disappear.  You know what?  AMECS5 really had something going: if an error occured—or even if the user just stopped the encode—at least there was a file that had everything encoded up until the error/stop.  But AMECS6 is like, "Oh, this rendering process had ended, so now I'm gonna eat everything I did!  Ha, ha, ha!"  Why do this?  I even had one encode at 99% completion before AME failed!  I could've worked with a 99% completed render!  But no, for some reason, the programmers decided to remove a good working feature from CS5.  Did they think this was smart?  Or maybe they thought it would be fun, knowing people would be screaming and pulling their hair out whenever stupid crap like 99% completion failures happened.
I don't care about updates to SpeedGrade; I can color correct stuff myself.  What good is an update to SpeedGrade when I can't even output the results?  Give us updates for the programs that matter.
Thanks a lot for helping me miss a deadline, AME programmers.

Answer 1

Please add me to the list of people having this issue, AME is not reliable for rendering. This is an ongoing issue that I was not aware until now, it's a hit and miss, please read the following article from Adobe support and their solution: IT'S A JOKE !!! are you serious?    Remove and reinstall all versions of all Adobe Premiere Pro components, and all versions of all Adobe Creative Suite components  ?  That was one of the solutions, and then what? purchase something else?  I already done that for other problems I had, not related to AME.  http://helpx.adobe.com/premiere-pro/kb/error-encoding-failed-could-read.html What about creative cloud cs6 ?, it could be a bad frame in the timeline, how do I inspect each frame BEFORE exporting the whole sequence for rendering? any suggestions? Am I missing something here? Thanks