Flickering footage in Premiere Pro CC 2014 but not in Premiere Pro CC 2013

New Here ,
Aug 14, 2014

Copy link to clipboard

Copied

Hi guys,

I've been having repeated issues with Premiere Pro CC 2014 on Windows. Basically my footage has a weird strobe/flicker when in the suite and when rendered off even although the footage looks fine, unaltered out of the camera. I rendered off the same footage in the 2013 edition of the software and there is no flicker/strobing going on. I've included one of the worst effected shots in CC 2014 and CC 2013 for comparison.I also experience graphical glitches occasionally when rendering. Please watch below:

Premiere Pro CC 2014 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)

YouTube

Premiere Pro CC 2013 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)

Premiere Pro CC 2013 - no flickering - YouTube

The footage was shot on a Nikon D3200 at 1080p 25fps, aperture 3.5, shutter 1/50, ISO 400.

Editing on a

Dell Optiplex 9020

Intel i5-4570 3.2 Ghz

4 gb Ram

Intel HD Graphics 4600

Windows 7


Has anyone else experienced this issue? My suspicion is an issue with either my graphics card or insufficient RAM.

Views

50.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Engaged ,
Mar 25, 2015

Copy link to clipboard

Copied

i had same problem,   only solution i could find was reverting to older version of PP

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Mar 26, 2015

Copy link to clipboard

Copied

I can't believe this thread has been going on for so long and there's no fix. I'm not here to unjustly whine...but seriously Adobe, when we hired a third person and upgraded to CC we find out that with the latest versions we can barely render client work. I have read SO many of these threads, it's seems platform independent, video card independent and so on...it seems the only consistency is that it's Adobe software.

So rather than go into a long list of what I have tried, my system specs, what the possible fixes I could try are (when none of them work - obviously why this thread still exists) and keeping fingers crossed after spending hours trying to beta test what it supposed to be working version - so we can render on deadline and NOT lose a client - how about a serious effort to fix this? I mean for real. It's great that Adobe responds with the intention of help, but there's a lot of people paying for flawed software and there seems to be no end to this.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Mar 28, 2015

Copy link to clipboard

Copied

^^This.  Seriously, is this going anywhere?  The workaround I've found is to manually re-conform the entire project in After Effects and export from there, which is obviously not a real solution.  I have to update a project from last month, and I was sure there would be a fix by now!  Imagine my surprise. 

This is an all-graphics project, meaning there is no camera footage to blame, no color correction, etc.. I'm using a brand new factory spec MacBook Pro, so hardly a unique hardware setup.

The inability export any video from Premiere makes it completely useless as a video editing tool, professional or otherwise. Oh god, do I have to give FCP7 another chance??

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Employee ,
Mar 29, 2015

Copy link to clipboard

Copied

Hi John,

I can't believe this thread has been going on for so long and there's no fix. I'm not here to unjustly whine...but seriously Adobe

It's hard to reproduce. You have to have the right system, the right effects, apply them in a certain way, etc. We do finally have a project that reproduces the issue and it's been added to the bug.

It's on my list of top issues and engineering is focusing on a fix.

So rather than go into a long list of what I have tried, my system specs, what the possible fixes I could try are (when none of them work - obviously why this thread still exists) and keeping fingers crossed after spending hours trying to beta test what it supposed to be working version - so we can render on deadline and NOT lose a client.

There are a number of workarounds people have found. The biggest one is to avoid adding color correction effects on adjustment layers. Have you tried that?

how about a serious effort to fix this?

I mentioned that we do have a project showing the behavior, so engineering has something to test. That's a good thing. My participation on this thread, I hope, shows good faith in that we are not avoiding the issue. We have been collecting information and trying to find a fix all along.

I mean for real. It's great that Adobe responds with the intention of help, but there's a lot of people paying for flawed software and there seems to be no end to this.

Have you filed a bug report yet? Even though it is a top issue for me, the more bug reports that are submitted by users, the more likely an issue will get priority for a fix. If everyone on this thread took the time to do so, it would help immensely.

Thanks,

Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Mar 29, 2015

Copy link to clipboard

Copied

Thanks Kevin,

I appreciate the response and I mostly wanted to highlight the severity of this problem by my message (I was surprised I was caught by this bug - and how much was already documented about it - as well the frequent crashes of any CC application upon initial start up.

As far as the flicker issue, until I figured a workaround my rendering was basically crippled. My workaround (short of crash coursing myself in DaVinci which is still on the table if my current solution fails) was to crash course myself in Speedgrade - learning literally on deadline since the flicker issue came out of nowhere.

So it seems like if I don't apply any effects in Premiere, and then do the color work in Speedgrade, I can render with no issues (so far that solution has worked for about 80 minutes of footage which is a good as sign as to workaround).

For me the this may be a permanent workflow since the Premiere color work degraded the final image quality quite a bit when compared to working in Speedgrade. It's something I didn't realize (the degradation) until I started working in SG and saw the results.

But it still is necessary to have a quick color/effect solution for review copies that can be accomplished in Premiere.

As far as my fixes, I have tried pretty much everything that has been written as suggestions - and having adjustment layers (or not) didn't affect the outcome. Any correction, even if applied directly to the clip randomly caused the flicker.

Something I did notice was by clicking the FX disabling it and then re-enabling sometimes helped clear the flicker. But it was also a random and couldn't be repeated. Not sure if that helps but it's something I noticed.

Where exactly do I file a bug report? I'll gladly contribute info due to the severity of this problem.

John

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Mar 29, 2015

Copy link to clipboard

Copied

I have found that I can successfully export my whole timeline as a .png sequence, export the audio separately, then put it all back together in After Effects and render a Quicktime without the flickering.  It's a ridiculous workaround and a huge pain in the neck, but hopefully it helps if you're in a jam with a client or a deadline.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Apr 01, 2015

Copy link to clipboard

Copied

What's the status update on this guys... Seriously this is a huge issue and because i can't get my project backwards exported to older versions i'm stuck at this point. My suggestion would be to tell your dev teams to drop all new features until they fix this problem. I want to send adobe a bill for the time its taken me to spend jacking around with this issue.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Apr 02, 2015

Copy link to clipboard

Copied

CrossHatchFlashing.jpg

I too have a strange flashing when I render a video. I am not sure how hard it is to see here, but it seems like a criss-cross flashing on my video. Seriously frustrating, especially when I need to render this film for a short film competition that begins in three days. Can you please help us understand what's with the flickering please?

System Specs:
GeForce GTX 970

Intel Core I7 - 920@ 2.67Ghz

2 - Samsung SSD Evo 1 TB Hard Drives running OS and Adobe Products

Windows 7 Ultimate

Current Geforce Driver Nvidia: 347.88

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Employee ,
Apr 02, 2015

Copy link to clipboard

Copied

Hi Jeremy,

Did you add any effects to that clip? If so, which ones? Are you using Adjustment Layers?

Thanks,

Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Apr 05, 2015

Copy link to clipboard

Copied

I have a few effects on my clip, not in adjustment layers though. Fast Color Corrector, RGB Curves, Lumetri, Film Convert Pro 2.1 (For Film Grain), and Tint. I disabled the Film Convert Pro 2.1 and it fixed it.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Apr 06, 2015

Copy link to clipboard

Copied

Jeremy, is this new for you?

It was for me until recently.

The workaround I found was to use either DaVinci (or learn Speedgrade) for color since Premiere is crippled as this point.

I've found it's random and appears with any effect, even applied directly to a clip.

JW

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Apr 06, 2015

Copy link to clipboard

Copied

John I've found that most of the time anything that requires rendering has been the culprit for me, ie when the bar turns red above the footage (Mercury Enabled is shown in yellow).  So if I avoid those pitfalls I have not been having issues. Well that is until I get into Speedgrade and it says my GPU is low on memory. You know, with a brand new GTX 970, clearly I'd not have enough memory to run color...(Sigh)  It's been a frustrating thing dealing with these programs lately, and its cost me a shot at putting my film into the film festival I was aiming for. I'm seriously upset with the software right now. I've been a CC member since it came out, and I'm really starting to think about Sony Vegas...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Apr 06, 2015

Copy link to clipboard

Copied

I agree Jeremy and why this thread needs to be kept active (in my case since it almost cost us a deadline job). So below is going off topic slightly about the actual problem (since there are no solutions in sight) but does address the problem in general as a product.

The problem for me is that the 2 others in my company are Mac based and we decided to upgrade to CC.

I like Vegas a lot (having used it before Premiere came back into the spotlight a few years ago )and would switch to it for sure at this point if it wasn't for the company being on one software platform.

The benefits of tight integration with other Adobe products aren't of any use if we can't get a clean render.

Did you see the beginning date of this thread?

It goes back to August...no excuses for it to exist for so long while we continue to wait and shell out $$ every month.

JW

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Apr 06, 2015

Copy link to clipboard

Copied

Agreed John - My issue is that there doesn't seem to be any transparency on actively working the problem. I'm in software development so I know these things should be handled. From what I can tell the issue is COMPLETELY random when ANY effect is applied to ANY footage. This tells me the problem is pretty foundational to the software. I mean - troubleshooting this can't be that hard. It wasn't an issue in CC - its now an issue in CC 2014. Check what changed. Pretty sure that's where the problem is.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Employee ,
Apr 06, 2015

Copy link to clipboard

Copied

Hi Jeremy,

Well that is until I get into Speedgrade and it says my GPU is low on memory. You know, with a brand new GTX 970, clearly I'd not have enough memory to run color...

Can you try running SpeedGrade on its own and not via Direct Link? You can simply open the Premiere Project you are working on from SpeedGrade and you should get better performance.

BTW, we do have a bug logged for this issue and are working on it right now.

Thanks,

Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Employee ,
Apr 06, 2015

Copy link to clipboard

Copied

Hi Pmarshry,

Agreed John - My issue is that there doesn't seem to be any transparency on actively working the problem. I'm in software development so I know these things should be handled.

We have a bug logged with a reproducible project from a customer.

From what I can tell the issue is COMPLETELY random when ANY effect is applied to ANY footage. This tells me the problem is pretty foundational to the software. I mean - troubleshooting this can't be that hard. It wasn't an issue in CC - its now an issue in CC 2014. Check what changed. Pretty sure that's where the problem is.

It only happens to certain customers with certain systems. It is not a global issue if that's your impression. Regardless, as I said, we do have a bug filed so we are working on a fix as we speak.

Thanks,

Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Engaged ,
Apr 08, 2015

Copy link to clipboard

Copied

Kevin-Monahan wrote:

It only happens to certain customers with certain systems. It is not a global issue if that's your impression. Regardless, as I said, we do have a bug filed so we are working on a fix as we speak.

In fairness kevin,  Adobe need to be less vague than that.... what customers what systems does adobe think it is at this point?  I would have bought a new laptop based on that but without knowing I cannot......

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...