[Adam Kawecki]

So, Quadros are like diesel or something?:D

[Adam Kawecki]

Dear Walter,

Thank you for your response. For synchronization based on the audio we use the most recent PluralEyes version.
The issue with the timecode sync in Premiere is that when you select x clips from camera 1 and x clips from camera 2, plus some audio files, Premiere creates a “bad” sequence – with as many tracks as there are clips, and they’re not synchronized. This is an extremely painful bug and impossible to work with. And you shouldn’t have to synchronize by audio when your footage comes with a perfectly synced TC. Also, what was pointed out so many times before by other users, you don’t always get good audio from your camera to synchronize it with something else (sometimes there’s no audio at all, only timecode).

I was hoping that maybe someone found a workaround, or can confirm that this actually works if you do something differently, like change metadata or something.
I am not entirely sure that this is the case for all camera types or maybe Premiere doesn’t support metadata from some cameras, as I’ve only worked with several Sony’s and Canon’s cams. But even if there’s support for some superb cams that doesn’t help an average TV editor like myself, because you get all types of footage every day, and all I want to do is to save some time and money.
Adobe seems to ignore this very basic function for a couple of years now, and I’ve tried their forums – there’s only promises for future releases.

[Adam Kawecki]

To buy an earlier version of Premiere, you would need to install a trial from a third party website (I couldn’t find any legacy downloads at Adobe’s website). I think that when the trial of an old version ends, you will still have an option to buy the software.
As of why Adobe still didn’t repair the flickering, I don’t know. I must say that I didn’t follow the threads on their forums recently because I use earlier versions and I won’t use the newest version until it’s proven bulletproof.
Some people reported the bug, I also tried reasoning with Adobe staff at their forums… I hope they’re working on it since so many people complain. I can only guess that the problem doesn’t occur on high-end hardware and graphics, as everyone who experienced the bug has an average priced hardware, like nvidia cards from 5- 6- and 7-series.

[Adam Kawecki]

Dear David,
Since my last post I didn’t find a solution other than returning to CC2013 or earlier version. If it’s really bad and you don’t want to recreate your project from scratch, I’d recommend:
1. Exporting xml from cc2014 and importing it into an earlier version of Premiere;
2. Using After Effect to export a project into it and then back to previous version of Premiere (I’ve heard it works for some, I don’t know how to do it though)
3. Nesting every single clip on the timeline that shows the issue, and then adding all the effects that you had on the original by copying them and pasting on the nested clip, or adding them again which may be more effective. This one worked for me in most cases. For adjustment layers, if you have only one track with them, you might want to consider nesting entire sequence and adding the effects from the adjustment layers on the nested sequence.

[Adam Kawecki]

Dear John,

We also have this problem, working on 1080p 25fps footage, from various cameras. Happens almost every time when there are two or more effects affecting a clip. Most notably adding a couple of simple effects like levels or color correctors on an adjustment layer will cause random flickering on the footage below.
I thought it was a problem with CUDA as we’ve got a range of nvidia cards in the studio, but turning it off doesn’t change a thing. Absolutely nothing helps with that issue, except maybe reducing the amount of effects on a clip or layer.
I believe that there are many people with this problem but they just try to get back from CC 2014 to 2013 in their workflows. As hard as it may be after upgrading a project and finding out there’s no easy way back.
I saw reports on that on Adobe forums recently but I didn’t see any solution at the moment.
I wonder why this bug still exists, being so critical and all; doesn’t everyone have it? I’ve tested this on very different machines and it appears every time.

Edit:
Recently, I had to work on a huge project that was cut in CC 2014, and when I added a couple of simple effects the flickering appeared. I found something on Adobe forums; It seems that nesting a single or multiple clips and then adding the effects on the nested sequence is almost always flicker free. This solution doesn’t always work though – flickering is still awful in simple a combo of
levels+luma curve+color balance+three way color corrector+stabilizer+rolling shutter repair.
In the future I plan on never using the newest versions of Premiere for any effects until it’s proven bulletproof (or flickerproof).