Premiere Pro CC 2014 encoding issues due to graphic opacity settings?

Our marketing team has been working on some instructional video content in Premiere Pro CC 2014 and have encountered issues with encoding the completed sequences. Our output format is HD video with the H.264 codec, 1920 x 1080, 30 FPS.
The symptom of the problem is that the encoding process cannot proceed beyond 50%, and in some cases, does not start at all. Simply put, we can't encode any videos to completion.
We think we have isolated the issue, which we initially believed was due to video format differences between the two cameras used to shoot the footage. An EPS logo was present throughout the video with reduced opacity (80%). When we removed the logo, the videos began encoding properly, and to completion. When the EPS logo was included at 100% opacity, the videos also encoded properly and to completion.
Has anyone else been encountering similar issues in Premiere Pro or After Effects CC 2014? If so, what was the resolution? Is there a known issue with the opacity of graphic assets in video encoding?

I've occasionally seen problems with say multiple masks & final render-out/exporting, but I've not seen one here on a graphic's opacity causing a problem. It's a very common part of the tool-kit, of course, for most pro/semi-pro editing. Even a lot of amateur stuff.
Which leads me to wonder what would happen if you created a fresh graphic of some sort, applied it a partial & full opacity, on a SHORT clip ... just to test things. Trying to establish if it's graphic opacity in general as your problem, or this specific graphic and/or its settings.
Neil

Similar Messages

Premiere pro cc 2014 is crashing due to after effects plugins being installed in the mediacore. Is there a solution to this issue?

The title honestly says it all. I recently purchased CC 2014 and have been updating and transferring plugins from prior versions of adobe after effects. When installing those plugins as I did in previous versions of after effects none of the plugins were recognized/loaded. I eventually found a solution to this issue by simply installing the plugins into the media core. They have all successfully loaded, but due to their presence in the media core premiere pro is now crashing upon start up. Does anyone know a work around for this?
Image showing crash:
Specs:
OS: Windows 8.1
RAM: 8GB
CPU: Intel 5 4670k
GPU: GTX 980 sc
Premiere Pro CC 2014 and After Effects CC 2014 are both updated to their most recent versions

First ... have you checked that these are all updated to work with the CC versions? I'd check with the makers of each plugin, the software has MANY differences.
Next ... if say you removed all but one, do any of them work? It might be worthwhile to remove them from the folder, then add one by one until you find one that is crashing things. That would at least get you part way forward.
And ... you might list which ones you have, in what versions. Folks around here might be able to help just seeing that.
Neil

Premiere Pro CC 2014 Playback Issue / Crash Mac Pro 2011

Hi,
I've been having a big crash issue on Premiere Pro CC 2014, since the 2014.1 update.
2014.0 has been working fine this year but the update has crashed some of my biggest current projects.
Programs just starts fine, workspace responds, but anything related to playback just crashes or freezes Premiere.
My config:
Mac Pro Mid 2010
Processor : 2x2,93 6-core Xeon
Ram : 24Go 1333
2x ATI Radeon HD 5770.
I've been reading all major topics on this, this i did :
- disable Mercury Transmission
- Flushes Premiere cache
- Reinstall premiere
- Updated to Mavericks (issue happened both in 10.9 and 10.10 - thought updating drivers+opencl would help, then again no)
- Repaired permissions
- Tried with another user session
… and so on.
Nothing yet has solved my issue, anyone to help me on this major trouble ?
Thanks in advance, best regards !
Paul

Hi Paul,
Try the following:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Remove plug-ins
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
Disable App Nap
Reboot
I placed the chief culprits in bold.
Report back if anything here worked for you.
Thanks,
Kevin

Premiere Pro CC 2014 RAM issues, audio dropouts and export failures

So I've upgraded to PP CC 2014, it worked fine for a while. Then I've noticed that while editing audio starts to dropout (I'm getting PP system message in the low right corner). I tried to dig up some info on the subject, but the only explanation I see that after couple of hours of editing PP eats up nearly all of my RAM.
Any solutions?
My specs:
i7-2600K 3.4 GHz
Quadro 2000
32 GB RAM

Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration. Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions. The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline.

Premiere Pro CC 2014 cropping issues

I am trying to create a sequence where I have multiple shots in a single frame. Much like the multiple frames seen in the show 24. I used a combination of crop and position to achieve this effect. It worked flawlessly, that is until I rendered the sequence. Now all my cropped footage has been cropped to reveal a large black space at the bottom of the video frame, as if Premiere cropped even more than I wanted, yet when I adjust it, the unrendered portion returns itself to normal. What is going on here? This is a huge 4K film project and time is of the essence. Anyone else experience this issue? Thanks for the help!

i would do a mask crop and all would look well until rendered out
how I achieved my desired mask crop was to keep the mask crop as it was and also crop the complete image away with either the right or left 'regular' crop. That was two crops - first one Premiere called Mask (1) which I inverted and then 100% crop of the image with the crop tools below that mask.
Not sure if that is proper way, but that is how I got mine to work

My video gets pixilated after importing in Premiere pro cc 2014. I've try to change settings but nothing happens.

My video gets pixilated (specifically the text on the video) after I import it in premiere. I don't think it's because of my editing because when i'm previewing a video after importing it the video is already downgraded and the text are so pixilated. I hope someone could help me.
Thank you in advance.
God bless

Here is the sample sir. I'm editing one of our church event and this is what i encounter.
Here is the info of the video as i click the properties of it in Pr:
Type: QuickTime Movie
File Size: 18.5 GB
Image Size: 720 x 486
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 24 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:59:46:29
Pixel Aspect Ratio: 0.9091
Video:
There are 107609 frames with a duration of 1/29.97th.
Video track 1:
Duration is 0:59:46:29
Average frame rate is 29.98 fps
Video track 1 contains 2 type(s) of video data:
Video data block #1:
Frame Size = 720 x 486
Compressor = Apple ProRes 422
Quality = Most (5.00)
Video data block #2:
Frame Size = 720 x 486
Compressor = Apple ProRes 422
Quality = Most (5.00)

H.264 encoding issues with Premiere Pro CC 2014

After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
CC v7 render: Premiere Pro CC.mp4 - Google Drive
[Version numbers corrected.]
Message was edited by: Jim Simon

Mark Mapes wrote:
This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
Sorry, but thats not completely true and by far not the correct answer:
The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder.
Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
BTW
Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
... but we can track masks in premiere now ... wow!

Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Exporting to Media Encoder crashes Premiere Pro CC 2014

Greetings,
I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
Here are my system specs:
Premiere Pro CC (up to date)
Win 7 64bit (up to date)
i7 970
24GB Ram
NVIDIA 470GTX (driver up to date)
3 x 1.5TB internal
4TB internal
3TB internal
12TB RAID 5 via USB 3.0
USB 2.0 and 3.0 drives
FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
All stock video plugins with a few third party audio plugs.
This problem happens with and without third party plugs, but it happens that this project uses them.
I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
Is there anything that I am overlooking here?
Thanks for the help!

Hi
Premiere pro cc 2014 8.0.1 (21) build
Encoder CC 2014 8.0.1.48
I use CC for Teams so it updates all the time.
Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
Looks like some programers and engineers have some work to do.
Thanks
Dennis
My computer:
Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
ASUS P6x58D Premium Motherboard
Intel (R) Core i7 930 @ 2.80 Ghz
Installed Memory 12 GB
NVIDIA GeForce 9500 GT
NVIDIA GeForce GTX 580
2 Apple Monitors and a HP full HD Monitor
With a BlackMagic Intensity Pro Capture Card

Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

My recent update to Adobe CC 2014 apps has been an unmitigated disaster. Was running the 2013 version until last week and everything was just dandy. Very good performance and excellent render/encode times even for stuff with lots of filters and fx.
Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes. These exports are with the same presets I regularly use (Vimeo 720HD H.264).
I've been poking around the forums here for two days looking for answers and can't find anything that works. Tried the whole "App Nap" toggle as well as a few other tips. Didn't do squat. Looking for any hints/answers. Thanks.
Mac Pro Mid 2012
2 x 2.4 GHz 6-Core Intel Xeon
32 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5870 1024 MB
OS X 10.9.5 (13F34)
System SSD 500GB
Cache SSD 500GB
Media HD 1TB

Hi MXSw,
MXSw wrote:
All right. More experimentation has been done. Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
Premiere Pro CC 2014 renders are painfully slow.
You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
MXSw wrote:
Kicked out a 1 minute edit with some color/fx in under 10 minutes. Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor. Its barely gone over 250% in previous attempts.
That sounds a lot better.
MXSw wrote:
Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs. I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
Regards,
Kevin

Multi Cam Flicker Issue - Premiere Pro CC 2014

Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez

ICanon C100 playback issue premiere pro cc 2014

I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps). It was happening after doing a straight import and creating a sequence using "new item". Then, after reading some other threads here and elsewhere, I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help. It is even doing it when I play at 1/4 resolution. The only solution seems to be to quit and restart and reopen the project. Then it works temporarily for a little while but not long enough to actually edit. I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
My Media Cache is not going to the startup diskc(it is gong to the right place)
I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
OS X 10.8.5
10GB 1066 MHz DDR3
NVIDIA GeForce GT 120 512 MB
Please help - very frustrated. If the solution is to transcode, it sort of kills the value of premiere in many ways.

Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez

Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro

Hi all!
Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
Even after a system reboot seems to be fine at first, but it still crashes on the project.
Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
Even drop the preview playback to 1/2 and still..
files are mixed 1080p footage from Canon 5d3, 60D, T2i.
I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
All my memory setting are set for performance and i have open GL on my D700s
Im not sure if this a software issue or someone my hardware is not working right?!
Thanks in advance!

I am having the same issues.
Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
The software really slows down when using the TYPE tool and also when scrubbing through footage.
When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
If you've figured it out since then Id love to know what works.
Thanks!
G

Premiere Pro CC 2014 encoding issues due to graphic opacity settings?

Similar Messages

Maybe you are looking for