Here is another puzzling issue with this project... I just tried to export several sequences by dragging the sequenced from Premiere to AME. None of these seqs had any renders from AE, just b-roll shot with the same camera on a second video layer. All of these seqs encoded the base V1 track. It didn't encode any of the b-roll or JPG still on the second V2 track.
It is like AME is encoding the seqs as they were before I added the b-roll footage.
I tried a re-install of PP and AME, moving all assets to another machine and encoding, enabling and disabling "Import sees natively" in AME, enabling and disabling Mercury in PP and AME, and I got the same result. AME fails encoding with a "error compiling movie" error. Same result when I tried to export from PP.
The only thing that worked was re-rendering all the clips that I created in AE using a different codec (was MOV PhotoJPEG and I re-rendered to Lagarith AVI). This seemed to work. When it would fail in AME it would hang on a frame for several minutes before giving me the sheep sound. The original MOV PhotoJPEG clips from PP played fine in the sequences and in media players. No drama, no glitches.
Not sure why AME wan't updating the sequences from PP. The fix for that was launching AME with Shift held down to clear preferences. Also I made sure I saved in PP before I dragged over to AME for encoding.
Hopefully this will help someone else along their journey. Thanks for looking!
Thanks for reporting the solution. This gives us a good foundation from which to launch an investigation.
This sounds similar to an issue I'm having. Any export from Premiere to AME works fine the first time (upon a fresh launch of AME triggered by the export from Premiere)... but with AME then open, any change made to the Premiere sequence is ignored by any subsequent export to AME. Exports of the changed sequence result in a file with the original version of the Premiere sequence... before any changes were made.
The problem is only solved by quitting AME and exporting from Premiere again such that it triggers a fresh launch of AME.
Running Adobe CC on a Retina 5k imac, Yosemite 10.10.1