Adobe Premiere Pro CC 2015 Audio and Video out-of-sync after upgrading from cc 2014

[TBogard77]

Hello everybody

After upgrading to Premiere Pro CC 2015 I'm getting all my video projects locked out with a yellow box (Adobe Player) that says "Audio and video clock out-of-sync at xx:xx:xx.xxx", and all my sequences presents the same issue

Any reason WHY? IT WAS WORKING PEARLS IN CC 2014!!!!

any help is very appreciated.

[Charles VW]

Not every issue was listed on the blog post.  I was just speaking with a coworker that the mute button issue wasn't listed, even though it is definitely fixed.

[Vinay Dwivedi]

Hi Grant,

Were you able to reproduce any scenario where you got any error?

So far we haven't received any query and Audio/Video sync issue(s) and is fixed.

//Vinay

[suncloud333]

Vinay:

No, I have no problems so far with the 2015 PPro upgrade . . . I just wanted to hear a technical explanation of what you did to fix the video/audio sync issue. I.E. did you re-write the "audio device class" driver?  Since all of us here on this forum have been closely contributing our feedback with you (Adobe), I just thought we could receive some "real" news on what what you did to fix the video/audio sync issue . . . (kind of like a "reward" for our contributions, time, and trouble ?? !!)

[suncloud333]

And Vinay, if you don't have this technical information, can you ask your "Premiere specialists /  engineers" ???

[Charles VW]

suncloud333 wrote:

And Vinay, if you don't have this technical information, can you ask your "Premiere specialists /  engineers" ???

Pro Tip: If you look in the about box for Premiere Pro, you should be able to see when one of the engineers is responding on the forums.

suncloud333 wrote:

No, I have no problems so far with the 2015 PPro upgrade . . . I just wanted to hear a technical explanation of what you did to fix the video/audio sync issue. I.E. did you re-write the "audio device class" driver?  Since all of us here on this forum have been closely contributing our feedback with you (Adobe), I just thought we could receive some "real" news on what what you did to fix the video/audio sync issue . . . (kind of like a "reward" for our contributions, time, and trouble ?? !!)

How technical would you like to get?  There was A LOT done in the past month between the 9.0 release (CC 2015) and the 9.0.1 patch. This was basically an all-hands on deck (however it should be noted that the deck isn't necessarily the forums for most of the team members). I'll highlight a few things, but the list is not exhaustive:

• We added the ability for a No Input option for MME (Win) and CoreAudio (Mac).  This was technically available in the WDM implementation of PPRo 8.2 (CC 2014.2) and before.  Moreover, it was the default for many cases with WDM.  So even if the issues were there, most people wouldn't ever see it since it wasn't the default settings.  So there was a very low probability that anyone with PPro 8.2 and before would have run into a situation where they upgrade, launch the app for the first time and they can't playback.
• We fixed the latency calculation as reported by the device driver when used with Premiere Pro's playback engine.  This didn't get wired up correctly when the audio device engine was ported from Audition.  Now fixed.  When the latency calculation was wrong, drift can occur in the player, and then compensation happens and a bunch of unhappy messages.
• There were a number of fixes when using MME and there was a low latency setting used.  Basically this has to do with the processing block size (buffer size) used when talking to the audio device driver to reduce jitter (or irregularity in the timing) of the buffers.  This also helps the player to stay within our sync thresholds.

There's more to it than those, and there's still situations where you can force the player to go out of sync, but those aren't new to CC 2015 or the 9.0.1 patch.  For example, if you load up a ton of heavy VST plug-in effects and your computer can't keep up to supply the audio card with a buffer of audio in the time designated, you can still get some messages.

[suncloud333]

Charles VW:

Thank you for taking time to list what you did . . . I appreciate it. It's good to know what all of you have done . . .

[FocusPulling.com]

Charles VW wrote:

• We added the ability for a No Input option for MME (Win) and CoreAudio (Mac).  This was technically available in the WDM implementation of PPRo 8.2 (CC 2014.2) and before.  Moreover, it was the default for many cases with WDM.  So even if the issues were there, most people wouldn't ever see it since it wasn't the default settings.  So there was a very low probability that anyone with PPro 8.2 and before would have run into a situation where they upgrade, launch the app for the first time and they can't playback.
• We fixed the latency calculation as reported by the device driver when used with Premiere Pro's playback engine.  This didn't get wired up correctly when the audio device engine was ported from Audition.  Now fixed.  When the latency calculation was wrong, drift can occur in the player, and then compensation happens and a bunch of unhappy messages.
• There were a number of fixes when using MME and there was a low latency setting used.  Basically this has to do with the processing block size (buffer size) used when talking to the audio device driver to reduce jitter (or irregularity in the timing) of the buffers.  This also helps the player to stay within our sync thresholds.

There's more to it than those, and there's still situations where you can force the player to go out of sync, but those aren't new to CC 2015 or the 9.0.1 patch.  For example, if you load up a ton of heavy VST plug-in effects and your computer can't keep up to supply the audio card with a buffer of audio in the time designated, you can still get some messages.

What is definitely new to 2015 and the subsequent patch is a severe deterioration of the ability to accurately scrub down to the frame-by-frame level; now, you might move a frame forward and backward and find sometimes it does tick the next noise event, while sometimes it doesn't (less than 50% success).  This is incredibly important for nailing, say, sibilance during an interview for fluid cuts.  Again, my system is identical as before, no change to anything but this upgrade and then the patch, and Adobe's bug created a problem for the first time ever.

Adobe certainly cannot say their work is done on this.  And it's not a matter of feature improvements, or something that always existed, it's actually a matter of restoring how well it worked before.

[johnb62742937]

I upgraded to this and am still having problems when using MME.  When I switch to use MME the video plays too fast and the audio bunches up to compensate.  It sounds like a DAT or CD on fast forward.  Changing the audio card's out sample rate to match the audio in Premiere as suggested earlier on (which I really don't want to have to do), doesn't change it.  Audio settings are the same as before, but using MME instead.

Version number shown in about is 9.0.1 (36) Build

Edit:  switched input to "no input" and the problem went away.  I don't really need an input for now, so it's basically working.  Might be good for you to know, though.

[Charles VW]

johnb62742937 wrote:

Edit:  switched input to "no input" and the problem went away.  I don't really need an input for now, so it's basically working.  Might be good for you to know, though.

Out of curiosity, what was the input that was shown before that was still showing issues?

[johnb62742937]

Unfortunately I didn't look, sorry.  I think it was set to S/PDIF, which is where it was before I switched back to CC 2014.  Otherwise it'd be the current system default, Aux.  I switch between these two depending upon what I'm doing.  If it matters, both are set to 96 kHz 24 bit.  Sorry I can't be more precise, it just didn't occur to me to look.

Edit: Just tried the input settings.  S/PDIF is the only one that causes the issue.

[KeyStudio]

I don't see any mention of the Render options. Will the update be able to use my NVidia card?

[ScubaBadger]

Er... firstly - no need to chill - I am cool with it and they may well moderate everyone - but never before this morning have I received emails saying my content had been moderated and frankly I do feel it's a waste of time and money - just an observation - not a rant...

[pwillener]

The moderation thing is a temporary anti-spam measure; legitimate posts should be approved by staff or mods within the shortest possible time.

But I fully agree with you regarding the "waste of time and money"; you won't believe how much time mods spend examining and approving every new post!

[filmermike]

Unbelievable Adobe. I had a very simple easy to edit video - should have taken one hour maximum. Now has become a huge problem and time investment trying to fix the audio sync issues. Went ahead an uploaded to YouTube as is. None of "solutions" in this thread worked for me. (The ones I tried anyway).

Enough incompetence Adobe FIX YOUR SOFTWARE please. Unbelievable - how could they have released this version? So many people are complaining...

Funny even YouTube warned me there were audio sync issues. They recommended using a program such as Windows Movie Maker to fix them. Maybe I'll switch editing platforms....?! Yes you can tell I'm not happy. I even mentioned in my youtube description about my displeasure with Adobe.

Here is the short beer drinking video in case anyone wants to see the audio sync issues that happen at the end when the owner of beer company speaks about his beer. Beer festival in Richmond Hill, Ontario - YouTube

[TomGruber]

This has become a nightmare.  2015.0.1 has not resolved the audio issues for me.  My setup using a Lexicon Alpha USB used to work swimmingly.

Audio is delayed or drops out depending on if ASIO or MME is selected in audio hardware preferences.

I have tried various combinations of all the following to no avail:

ASIO, MME, ASIO4ALL, virtual audio cable, latency adjustments, buffer adjustments, sample rate adjustments, new project with XML import, media cache deletions, crossing my fingers, reboots, default input: no input,  default input: Lexicon Input/Output.

Is there a solution I've overlooked?  Or is Adobe aware of ongoing issues for some users?

[FocusPulling.com]

TomGruber wrote:

This has become a nightmare.  2015.0.1 has not resolved the audio issues for me.  My setup using a Lexicon Alpha USB used to work swimmingly.

Audio is delayed or drops out depending on if ASIO or MME is selected in audio hardware preferences.

I have tried various combinations of all the following to no avail:

ASIO, MME, ASIO4ALL, virtual audio cable, latency adjustments, buffer adjustments, sample rate adjustments, new project with XML import, media cache deletions, crossing my fingers, reboots, default input: no input,  default input: Lexicon Input/Output.

Is there a solution I've overlooked?  Or is Adobe aware of ongoing issues for some users?

Adobe fixed the sync issue for most, and lots of hurrahs ensued, but basically the problems with dropouts and weird scrubbing behavior persist.  Instead of reverting to the prior sound engine that would have fixed all the new problems (with no performance benefits), they stuck with the new Audition-native backbone.

[Suspended Moments]

Same here... the CC 2015 update fixed many issues and I no longer get the out of sync warnings...

Now, only during editing and preview, the playback is fast and choppy/stuttery audio and video... after rendering and exporting, the exported segments are fine, the problem exists during editing only.

clicky choppy stuttery and faster than it should be...  (before the update, it was slow, choppy, stuttery and would not render correctly, so we're headed in the right direction)

I hope another generation of fixes is on the way.

Windows 7 pro, Nvidia Quadro K4000 video card, 32 gigs RAM, i7 3.4ghz, 64 bit processor

more fixes needed for Adobe Premiere Pro CC 2015

[ScubaBadger]

Mike, I sent a message to you last month offering to put this right for you, the offer is still there.

Get in touch - all I need is the project folder - I can make space for you in a google drive folder if you wish.

I know it's not the true answer you want (PP working properly) but at least you'd have a working version of your video in sync to get on with...

Dave

[RaymondoSA]

I can't believe it. I thought it was just me and my computer. I crap you not I even went out and bought a new set of radio mics because I thought the audio was off because of me. Never thought it would be the new cc2015 I had. Damn I'm pissed now, royally pissed. Busy downloading this update, it better work. Strange though because it felt like I only went to cc2015 very recently.

[Kosmos]

I am getting serious audio synchronization issues within PP 2015, I am currently installing PP 2014.

The problem is that despite working with Constant Framerate Video source files Premiere Pro 2015 is inserting Synchronisation issues into the media. The issues are visible and can be encountered during editing. Rendering the video results in the introduction of the synchronization problem into the resultant complete project. Seriously there is little more I can actually do to attempt to correct this issue.

The problems generally manifest in long files, Typically if a source video is longer than 1 hr and 12 minutes Premiere Pro 2015 will insert an audio synchronisation problem that will occur within the next 10 minutes and correct itself in the closing 5 minutes of the output video. I fail to see anything particularly 'professional' about this problem. Additionally I am working with source files that have a fixed Frame rate in order to eliminate Frame rate synchronization issues, the issue is still present regardless.

With respect to my system hardware, I am using an Nvidia 980Ti GPU, and a Creative Labs ZxR PCIe sound car the sound card is configured for ASIO operation.

[Kosmos]

Confirmed, there is an issue in Premiere Pro 2015 in particular as it relates to the encoding of long HD video files. After installing Premiere Pro 2014, the problem with Audio Synchronization issues being inserted into videos of more than an hour and 10 minutes is gone, at least from the editor within the application. I am currently awaiting a complete render of a long project to ensure that issues do not creep in as a result of rendering.

[Kosmos]

I have finished the render of my Video Project, and it was successful with no synchronization error introduced when rendered with Premiere Pro 2014. Clearly an issue exists in the 2015 release that introduces synchronization problems even when using Constant frame rate source material. This is unacceptable in any product labelling itself as 'Professional' 'two-bit' may be a more apt monicker for the 2015 edition of Premiere.

[FocusPulling.com]

I agree with these assessments, finding that long projects (only in CC2015) go out of sync in an extremely obvious and disruptive way.  In this example, it's a classical music concert where the conductor eventually appears to be conducting a totally different orchestra.

Adobe has certainly not "fixed" the problem.

[Kosmos]

Thank you for the response. It is validating to here from another person experiencing a similar problem, though just as frustrating because it isn't just me. At least my current project is just frivolous but useful for testing purposes if nothing else. I can only entertain the slow boil fury that such issues cause and cost to individuals relying on this software for their careers. I can only hope that Adobe will actually correct this flaw.

[Zakkaru]

Having the same issue as Kosmos. Constant Framerate h264/x264 (w/ aac audio) files are out of sync in PP2015.

The weird thing is, if you let PP2014 conform the file, then use the media cache generated by PP2014 in PP2015 - the file plays fine without any sync issues.

Seems like Premiere Pro 2015 does not conform files properly.