Premiere Pro CC 2014 Stalls Midway Through Render

I've recently added the CC 2014 suite to my computer, and for the most part it's good and solid.  However, whenever I try to output a file from Premiere Pro CC 2014, either as a direct export or via Media Encoder, the program simply stops rendering midway through the process.  It doesn't actually freeze up or fail to respond, as I can easily stop the render altogether without having to resort to task manager.  It simply stops as any random point and then the estimated render time begins to climb, and it doesn't stop climbing.  It doesn't matter what settings I use, custom or preset, MOV, MP4, AVI...h.264, mpeg...codec or container does not matter.  The results are the same.  I even tried changing the Preview File Format, nothing different there either.  Tried a complete uninstall/re-install (made sure to use the cleaner tool).  No luck.
As someone who relies pretty heavily on NLE's to cover his freelance work, this is pretty disconcerting.  For now, my only fix was to step back to the previous version of CC, but I don't view that as a long term solution.  Anyone have any ideas?
For clarity, here are my system specs:
Motherboard: Asus Z97-Pro
CPU:  Intel i7 4790k (with Corsair H110 Liquid Cooler)
RAM: G.Skill Ares series 1866 - 32GB
GPU: EVGA GTX 780 - 3GB
Primary Drive: Intel 335 Series SSD - 240GB

You say it stops at random points every time. Are they really random, or is it at the same general area on your timeline? There may be a piece of media there that is preventing it from finishing. This has happened to us several times throughout our editing process for our documentary and it is almost always a image file that causes this issue. Generally replacing it or converting it to another format will help in our case.

Similar Messages

  • 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.

  • After upgrading to Premiere Pro CC 2014, I can't change the render preview location

    Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive.  It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?

    Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!

  • 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

  • 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.

  • 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

  • Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

    After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
    Believe me, there's hardly a thing I haven't tried.
    It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
    Also I know I'm not the only one who's having these problems.
    My specs are:
    OS X Yosemite 10.10.1
    MacBook Pro (Retina, Mid 2012)
    2,3 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    NVIDIA GeForce GT 650M 1024 MB

    Hi JJ,
    JJ Millen wrote:
    It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
    One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
    Now that we have that sorted out...
    JJ Millen wrote:
    I checked that and it says 8.2.0. (65) build.
    Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
    JJ Millen wrote:
    Here are all the checkpoints mentioned in that thread, applicable to my project:
    - Version 8.2.0;
    - My Creative Cloud says Premiere Pro is up-to-date;
    - Operating system is OS X Yosemite version 10.10.1 (14B25);
    Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
    JJ Millen wrote:
    Type: MPEG Movie
    File Size: 4,0 GB
    Image Size: 1920 x 1080
    Frame Rate: 25,00
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:12:35:16
    Pixel Aspect Ratio: 1,0;
    So is this H.264? What is the camera that you are working with? DSLR?
    JJ Millen wrote:
    - I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
    What kind of drives are the media files stored on?
    Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
    Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
    JJ Millen wrote:
    - The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
    When you import clips, are you using File > Import, or are you importing via the Media Browser?
    JJ Millen wrote:
    - Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
    Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
    JJ Millen wrote:
    - The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
    - I currently have no third-part effects or codecs installed in Premiere;
    - I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
    - The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
    I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
    Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
    JJ Millen wrote:
    Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
    So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
    JJ Millen wrote:
    Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
    I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
    For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
    Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
    It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 playback freezing and crashing with new iMac i7

    Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
    Here are the specs:
    iMac i7 4.0GHz 5k Retina
    32 GB Ram
    AMD Radeon R9 M295X 4GB graphics card
    512GB Solid State Drive
    I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
    So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
    Thanks,
    Jason

    Hi All,
    Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe preference files are set to read/write
    Delete media cache
    Remove plug-ins
    If you have AMD GPUs, make sure CUDA is not installed
    Repair permissions
    In Sequence Settings > Video Previews, change the codec to one that matches your footage
    Disconnect any third party hardware
    If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
    Disable App Nap
    Reboot
    Best,
    Peter Garaway
    Adobe
    Premiere Pro

  • Premiere Pro CC 2014 renders are painfully slow.

    Running CC 2014 on a brand new iMac: 3.5 GHz Intel Core i7, 32 GB RAM, NVIDIA GeForce GTX 780M 4096 MB.
    I have a 2.5 minute timeline with many dynamic link clips back to simple After Effects CC 2014 comps. Rendering in this timeline is MIND-BOGGLINGLY slow. 
    Video Rendering and Playback Renderer is set to Mercury Playback Engine GPU Accelerated (CUDA)
    And in Preferences > Memory> I have optimized rendering for "Performance".
    My Sequence is using Apple Pro Res 422 as my video preview codec with Maximum Bit Depth and Render Quality selected.
    Renders should be screaming.
    Is anyone else experiencing this? Have I done something stupid in my set up?

    Hi Kevin.  Thanks for response.  Yes, acceleration is enabled.  Not CUDA as I'm running on a ATI Radeon HD 5870.  See screenshot below. 
    Also have a thread specific to my issue here: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
    If you get a chance to look through it, I'd appreciate it very much.
    Thanks!
    Martin

  • Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    It can occur even in the parts without filters !!! But no all time.
    ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
    ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
    ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
    MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
    When waiting for fixes this bug?

    Hi Aleksey,
    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
    Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
    Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
    When waiting for fixes this bug?
    If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug.  If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Why does Premiere Pro CC 2014 renders incredibly slow?

    Dear Premiere Pro experts
    I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
    The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
    Here are some facts that might help to isolate the problem:
    Project:
    Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
    Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
    Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
    Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
    Hardware / Software:
    i7-3770K @3.5 GHZ (Quadcore)
    16 GB RAM
    NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
    Windows 8.1
    SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
    Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
    There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
    I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
    Can someone help me with any of these problems?
    Thank you,
    Martin

    I did some additional research and found out, that the slow rendering happens with this combination:
    - Auto-Color using Temporal Smoothing
    - Render 3D Intermediate
    Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
    Might this be a problem in the codec or in Premiere?

  • 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.

  • Re-interpreted footage metadata is lost when moving Premiere Pro CC 2014 project file to different computer

    Hi guys,
    I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
    My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
    Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
    We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
    Looking forward to a resolution to this problem.
    Daniel Lichtenberg
    [ad/link removed by moderator]

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Premiere Pro CC 2014.2 crashes when "locating media"

    The problem;
    Premiere Pro CC 2014.2 crashes when "locating media".  I am working on a project that has not given me any problems for the last 200 hours.   About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs.  I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail. 
    Project workflow
    - 700gb of 5d footage
    - 20 sequences under 5 minutes
    - Dynamically linked files with AE
    - Warp Stabilized about a dozen clips of under 5 sec
    - On every sequence color correction adjustment layer with  RGB Curves, Three way color corrector and sharpen filter
    - I kept old versions of the sequences (I was in version 5 before the crash)
    What I have tried;
    - Unsuccessfully tried to open auto-save files for this project.
    - Successfully opened other older non relevant project
    - Removed Mercury playback engine in the project settings
    - Cleaned out media cache database through pp in media Preferences
    - Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
    - Tried importing sequences into new .proj file; it would crash as a result.
    What "worked".
    I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client.  I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
    Questions.
    - What the hell happened? Why could I open it on one computer and not on the other?
    - Is there a way to fix a corrupted .proj files on a PC?
    - What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
    Windows 8.1  64bit
    Premiere 2014.2
    Intel Quadcore i7-4770    3.40GHz
    16gb Ram

    Hi,
    I would suggest the following steps:
    http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
    Run a disk permission repair on your boot drive, and
    Reset Home Folder permissions and ACLs Error | Apple Support Communities
    Thanks,
    Rameez

Maybe you are looking for

  • Contacts not shown in messages sent via PC Suite

    Hi all, OS : Windows XP SP2 Connectivity : USB CA 101 Handset : Nokia N 82 Handset details : V 30.0.019 RM-313 Issue : If i send any message from my phone, in sent folder the contact person's name will display whereas for the messages sent via pc sui

  • BI strategy for the SME

    Hi all, First of all I live in Belgium so I cant preview any of this software: http://www.microsoft.com/en-us/powerbi/default.aspx Now most of my customers are SME in the fashion industry and we are going to develop a data warehouse platform where th

  • Uploaded html code is reformatted disabling javascript functionality

    I've asked this before but not had a comprehensive resolution. This issue began when I moved from my apple powerpc running OSX 10.5.8 to an imac running 10.7.3 and for the reasons you'll see I'm sure this is connected with mac OS than dreamweaver, bu

  • Multiple movies in drop zones

    Can drop zones accept more than one movie clip? Everytime I try, I get the message, "Action not supported in iDVD". iMac G4   Mac OS X (10.4.3)  

  • Album lost in iPhone

    Hi, I have following problem with my recent update to 3.1.2. The albums in my Photos are no longer sync with my iPhone 3GS 3.1.2. For example, in my iPhoto I have 31 albums which have to sync with my iPhone thru iTunes but after synced, there are onl