Are you guys on the new version of Premiere Pro 2014? Just curious if that new version still has this issue? I haven't upgraded yet as I was waiting for the first bug release/update which just came out to make sure all the "kinks" were out. Hopefully. The bizarre thing about this bug is that it never occured for the first 1.5 years of me using Premiere Pro and for months into the last version of PrPro. In that time I had many projects with no issues at all. Then, suddenly, the error hit on projects that were NO different than previous ones, and I ended up having to always export with "Software Only" on both the timeline and in AME for it to not have the issue. We use hundreds of warp stabilizers on each project and it didn't seem to have any obvious effect on this error. I miss the days of faster exports. Software Only is SOOO slow. Although having no error is definitely worth it.
↧