-
Why is there a thin black stroke around .png images in Premiere / Encoder exported videos?
I have a thin grey stroke that is showing up around all the image .pngs in my output files. The stroke doesn’t show up when the video is viewed in Premiere. I am using .png files to cover specific parts of the video track, and I want them to blend into the background (it is a screen capture with some info that needs to be covered up).
I cross posted this on an existing thread in the Adobe Community forum. Someone else has the same issue. Here is a link to that forum, which includes screen shots:
https://forums.adobe.com/message/5427456
Any help would be great.
Thanks in advance.
-Eric
-
9 Replies
-
Try trimming the edges with the Crop effect.
-
Okay, I am going to try this and send an export to the Queue. Will let you know what happens.
-
I recommend using a direct export from Premiere instead of the AME queue.
-
I used the Crop Tool on the PSD file before exporting a .png, then replaced the .png in the Premiere timeline, and viola! It worked. Not sure why… but I will take it!
I encoded using AME and it still did okay, just out of curiosity, why did you recommend against AME? I use this all the time…
You can see a more detailed discussion of this issue (border around .pngs) on this thread at Adobe Communities.
https://forums.adobe.com/message/5456455#5456455
-
[Eric McCarthy] “just out of curiosity, why did you recommend against AME? I use this all the time…”
It helps with troubleshooting to eliminate potential contributing factors. In addition, if the output is being rescaled upon export then sending a job to the AME queue can degrade image quality, as discussed in this post.
-
also sending it to que typically adds A LOT more export time.
I had a video that exported directly out of premiere took 15 minutes.
that same sequence exported through the queuing in ame wanted an hour! -
Sometimes the queue is slower and sometimes it is faster. In a test of 40 rendering jobs it was 30 seconds slower on average. When transcoding from a master file the queue was 2.4 minutes slower per file. The main advantages are background processing and the ability to queue multiple jobs in succession.
-
Thanks guys,
I am always ping-pong-ing back and forth between projects, so I have to use the AME to keep Premiere open for work. Sometimes, if I am also doing AE work I will set the AME up on a separate machine (accessing the timelines from our RAID), but I am usually more concerned with the processor hit to the current program working than to the encoding process in the BG… Still good info to be aware of.
-Eric
-
I hear that.
If I have a bunch of sequences to get exported and have time or
running overnight I do que them.Exporting H.264 takes WAY longer though compared to codecs like ProRes
via que in my experience.
Reply to this Discussion! Login or Sign Up