Anybody having trouble with PNG's with the new Update of Premier Pro 2018 April 3rd?

[DanielZapata]

I cant get Premier to read PNG's, I make them in Photoshop and export them as PNG's but when they come in Premier is all the weird crap.

I already clear the cache, re installed, re exported, started  new project, I cant get it t work! WHAT THE CRAP IS HAPPENING!!!

This are two pictures of PNG's it is one title, but Premier is merging all the PNGS in to one picture, same with the one below, it suppose to say TIPS on crussing, not all that weird color and reverse shadow going on.... this is totally wrong!!

[willaemmm]

wow, this is nuts. how was this not picked up in testing?

[mikeirvingmedia]

@Adobe where is the patch to fix this? Extremely aggravating that you can't export for clients and it's been since APRIL 3RD!!!!!!!

Switching to Avid if this bullshit continues. Costing me time and money.

[indianag28205267]

argh. I'm having the same problem and it's April 11th now.... what is adobe doing about this please?

[mitup11072355]

I was on chat support with them today and the representative said the patch is coming next week but no specifics on what day.

[GabUBS]

This is horrible.  I didn't bother to see if there were any issues with the update.  I asked everyone at work to update and all of sudden, all hell broke loose.  We had clients waiting and we couldn't figure out why we were getting all of these glitches.  So for now, we are only using PSD's or JPG's until Adobe fixes it.  Hope they will do it soon.  This bug really affected us. 

[alexl45094283]

Same problem!!!

This was so annoying. I had to go back to the old version. But in one project I already made so much progress that i had to finish it in this new stupid update.

The solution i found is to export all the png's in tiffs keeping transparency and then in Premiere "replace footage." Even the option replace footage is not working properly so you have to replace the footage "twice" for every png, because the first time when you replace clicking "okay", it seems to get freeze and nothing happens so you have to select the .png and replace again and the second time it gets replaced by the tiff...

Of course replacing more than 100 pngs was terrible.

No brownie points for premiere... very bad issue guys...

[esteban_zissou]

Same issue here on my iMac and MacBook Pro. Both running High Sierra (10.13.4). Nvidia GPU's in both. Latest web drivers.

Not only do the PNG's look a little crazy but the rest of my timeline picks up weird artefacts in both my viewer and renders.

I thought my GPU had died at first but it appears to be an issue on both machines.

Combine this with the new lack of codec support.. pretty frustrating, I have absolutely zero issues with Resolve and I pay absolutely zero £'s for that.

[vitorlmartins]

This is so frustrating, we have deadlines Adobe! It cannot took so long to fix it. Who is gonna say to my client that i'm behind the schedule because of a stupid PNG!

[saberune]

I'm having the exact same problem in PP, on good Mac running 10.13.4. Issue has popped up in two different projects. One of them is a template I've been using weekly for a year. It's a weekly news bite that has a countdown timer in the corner. The timer is a .png sequence. It's been especially fun since it took me most of the week to actually identify the problem, so yay, more lost productivity.

I also use a win10 pc, but I haven't updated it yet (whew!), so I can't say how the problem looks there.

Seriously, how do you break a png? There's money on the line here. Get that patch out.

[Padres Brendan]

IDK if anyone posted this but I turned my PNG into a Quicktime animation with alpha in Ae and seems to be at least a work around.

[Ville Honkonen]

I am a TV news editor and i update the premiere and use today 6 HOURS(!!!) with this problem.

We use a PNG elements for interview people and this is a BIG problem because i didn't know that here is a bug. It looks in timeline that everything is ok, but when you push the export button first:

- The exported mp4 file with png image goes totally blue / pink

- When you return to premiere, the timeline is broken (there is random in+out footage)

- The library png files is broken, you need to rename png and export again

- Image is shaking, and it is pink (in the position of png file).

I update old premiere version and it work's now, but i need to edit 4min TV news story again..

Maybe 1-2 months payment refunding should be ok adobe?

[stevec42714152]

Encountering the exact same problem, after updating yesterday.

I found that re-encoding a new identical png bought me some time, but the issue reverted back shortly after.

Can't say this is helping me make any bloody deadlines, also disconcerting to see this problem has been identified for nearly two weeks with no fix in place.

Adobe, get on this man!

[lehestro]

I'm having this same problem too. Will file a bug report when I have time and am not freaking out about getting out to client. MAJOR f- up on Adobe's part with this one. Good heavens. 2018 has been a disaster for me thus far.

[ztjones]

Same problem here. WTF adobe. going back to Avid

[louisea68611754]

After having this problem with the png's I decided to uninstall the latest update and go back to the previous version.  The png's work fine now, but most of my videos on the timeline are corrupt.  I'm having to replace almost all the videos on my 60 minute film.  And if I right click and "replace footage". it's still corrupt.  I have to bring in the video file and line it up again.  I have so many video files in this project.  I'm caught between a rock and a hard place trying to figure out if I spend the time replacing all the videos with previous version, or waiting for latest version fix and reinstalling that to see if then both my png's and videos work as they did before this nightmare of an install.  Did anyone else have this problem when they went back to previous version?

[andreal8946667]

I did something similar. I was working in a master file with multiple sequences of short videos (2-5 minutes each) when I did the update. It created a new version of the project so when I had problems with the update, I installed the previous version to back to what I was working on and went back to the previous version of my project that was compatible with that version of Premier. My video wasn't corrupt but it was SUPER glitchy, whereas it was perfectly fine to begin with if it didn't have a PNG. I couldn't fix the jittering it so I just updated again to the 12.1 and kept moving forward by re-building PNGs as PSDs after finding that solution was working for people. Not sure if that helps.

[louisea68611754]

Thanks!  That's likely what I'll have to do.  I really want to install the latest version for all the great new features, so I might just have to change all the png's to psd and hope the video is back to normal when I update.  Good times!

[Rameez_Khan]

Hi all,

We have identified this as a bug and are working on a fix.

Appreciate your patience!

Thanks,
Rameez

[37patrick37]

HI,

When and where are we going to be notified that the issue has been fixed?

Thanks

[Ville Honkonen]

RameezKhan  kirjoitti

Hi all,

We have identified this as a bug and are working on a fix.

Appreciate your patience!

Thanks,
Rameez

is there any refunding? i lost 8 hours my work and i need send all footage to my client without any graphics.. also i can't use this month premiere because all my projects are in new version updated.. so i just need to wait the patch.

This is SO big bug, so i think it is ok to give something back.. i am thinking to move back to final cut pro X right now..

[temp124323]

Fyi, I had built my png files in Illustrator. Importing the .ai file also seems to work as a work around for now.

[Ramnaider]

I'm having the same problem and I have SO many transparent PNGs, it is a HUGE inconvenience and delay on our deadline! Adobe please fix immediately, release the patch already. It is URGENT.

Thanks

[jdevnani]

Same problem.  I've downgraded to 12.0.0 but am still having the issue!  Media cache is cleared. Must be something to do with leftover files from 12.1? Anyone else downgrade and experiencing this?

[jdevnani]

Nevermind, solved, forgot to downgrade Media Encoder as well

[meylorod]

I saved out as PSD and it fixed the problem. But still, I shouldn't have had to do that.

-M