[Michael Ron]

Do you have any plug-ins installed?
Is this an updated version of Premiere or a clean-install?

If it’s an update and you’re using the same cache-database location as with previous versions of PP, it might be worthwhile to delete all media-cache and cache database and see if that makes any difference.
(I know it sounds like it shouldn’t, but a lot of users have reported weird audio-related bugs being solved by clearing media cache, so it’s worth a shot).

I will try to get my hands on a microphone and test this later today, will let you know if it works for me.

[Michael Ron]

As others have said above, you can keep your currently installed CS version and install CC from scratch without removing your existing software.

As far as the current project, personally I would recommend to hold off on migrating to CC until you finished all your current work. You can try migrating the project into CC, but that would most likely cause bugs and crushing, especially if your migrating from CS directly to CC2015 (that would be a three-software-versions jump).
You can always try to install CC and open the current project to see how it works, but keep in mind that after you have done some work in CC you won’t be able to re-open the project with older versions of CS.. So that might be risky if you start running into issues after doing major work on your project.

[Michael Ron]

Haven’t heard of this before, but I have seen similar issues with missing frames in exports done via media encoder. I would try to trash render files and clear the media cache database and see if that helps at all.
Another thing that might help is trashing AME’s preferences (you can just delete the entire AME folder inside your Documents folder – it will be recreated next time you launch AME).
Obviously if you have anything in the preferences you might need, make a backup of it first.

If after trying all the above the problem persists, more info on your issue might be helpful – Is this only happening with a specific project or is it a system-wide problem? What export settings are you using?
Do you see this issue when say, converting a file through AME, or is it just an issue with sending to queue through Premiere?

[Michael Ron]

What happens once you render the second time? Does the audio stop at the exact same point in time, or does it vary from one export to the other?
Is your music on its own separate audio channel (as compared to other audio clips that you are able to hear in the exported video file)? If it is, I would try moving the music to a different track, and re-exporting to see what happens.
How many audio tracks does your project have?

As Jordan said, it might also be worthwhile to try other projects and see if this is a project-specific issue or not.. If you are seeing this problem on more than one project, can you please post a screenshot of your export settings?

[Michael Ron]

Premiere has some strict autosave restrictions – it will only autosave if you have unsaved changes in your project. So if you have your autosave interval set to 20 minutes, and 20 minutes have passed since the last autosave but you manually saved your work a minute ago, Premiere will skip the autosave and try again in 20 minutes.
The software will also skip autosaving while playback is running in full screen mode.

I would suggest you re-set your autosave interval for around 5 minutes, work for a while without saving manually, and check to see that it is actually autosaving.

[Michael Ron]

PP CC doesn’t have a plug-in, but can natively create DCPs.
If you never installed the 30-day trial of CC, I would suggest you try that and use Premiere CC for exporting the DCP.

Good luck 🙂

[Michael Ron]

So no one but us is having this issue?
(Or is tape-capture is even more dead than I imagined?)

[Michael Ron]

That’s interesting, our footage is also mostly interlaced (for broadcast in Israel), so I guess this could be the issue.. I will run some tests with progressive footage and see how that works.
However I would still think Premiere would have a way of overcoming this issue, since many people work with interlaced footage.. If my sequence settings match the footage and are set to interlace, I would still expect no extra frames to be added.

I submitted a bug report to Adobe – I would love for people who also have this issue to do the same, and maybe this can be solved in a future update.

If anyone has any other info or workaround ideas, I would love to hear them.
Thanks! 🙂

[Michael Ron]

If creating a new user worked, and removing and re-installing Premiere didn’t – it might be a matter of a stuck or corrupt p-list file.
try navigating to:
Users/(your username)/Library/Preferences
and delete all the files that have to do with adobe, especially this one “com.Adobe.Premiere Pro.8.0.plist”.
If you already re-launched Premiere since deleting user preferences, I would recommend you also delete those again (feel free to delete your entire profile folder under Documents/Adobe/Premiere Pro/8.0/Profile-username).

I can’t promise it will work, but since all of these files should be recreated on the next launch, it can’t make things any worse.
After deleting the files I would try to restart the machine and relaunch Premiere. If you have multiple users on this machine and the user that’s having the issue is not an admin user, it might also be worthwhile to do a permissions repair via disk utility (if that is the case I can explain how you can do that if you need me to).

[Michael Ron]

OK, so the issue must be the audio only from an A/V clip.. We tend to do that a lot, using syncs from certain clips without necessarily using the video.
But thanks for the answer, and hopefully this will be solved soon in a future update.

I’d also like to know for future reference, is there a place where users can view all currently known issues with Adobe softwares?
It will help deal with the editors frustration, as well as our own (IT team), since every update we have to pretty much guess what the issues are, consuming valuable editing-time from our video editors and AE artists.