Red 4k/Premiere CC 2014 Rendering Error

Hello,
So this has been an issue that has been plaguing me ever since I started working with Red Epic Dragon footage. (6k raw)
The native footage is 6k, but my sequence is 4k. So I just scale to fit. I have no issues editing the footage, or even previewing it in premiere. Even with effects applied, I'm able to watch it perfectly at 1/8 resolution, which is fine with me.
The only issue comes when I go to render out anything. I always get one out of a few error messages, and then it crashes. This has happened with every project I have done that involves the Red footage, so I don't think I have a corrupt project or whatnot. One example seen below.
Or, sometimes it just gives me the 'Premiere CC can't continue, sorry' error, and crashes.
I have tried this on two different computers, yielding the same results.
Specs on Computer 1 (Desktop)-
Alienware 17r / Windows 7 / Intel Core i7-3820 CPU @ 3.60Ghz / Nvidia GeForce GTX 660 / 16GB RAM
Specs on Computer 2 (Laptop)- Alienware 15 / Windows 7 / Intel Core i7-2670QM @ 2.20GHz / Nvidia GeForce GTX 680M (4gb) / 15GB Ram
This is frustrating because my laptop has such a powerful graphics card, and the effects I have applied are just basic RGB Curves, nothing that would require MASSIVE amounts of GPU.
Things I have tried so far, to no success.
Update drivers to latest version
Downgrade to older drivers
Upgrade PP CC 2014 to latest version
Try rendering in PP CC (not 2014)
Turn off/on 'Mercury Playback GPU Acceleration'
Clean cache
Bring entire sequence into a new sequence, and re-render
Bring entire sequence in AE Linked Comp, and render
Remove all the effects off the clips
If anyone has any tips or advice, it would be much appreciated. It's so frustrating because I have finished client video's that I need to show, but I can't.

A little more info:
This seems particularly likely to happen when I open a sequence on the timeline that has more than 5 audio tracks.
I'm using OS Mavericks 10.9.5. Video footage is .R3D. I have the crash report if that helps.

Similar Messages

  • Premiere cc 2014 renders not frame accurate?

    I'm rendering some sequences from cc 2014 (the latest October release) all are exactly 20:00:00 long, with out set on that frame exactly. However if I bring the exports into after effects, some of them are a frame longer or shorter than they should be.
    Any suggestions what might be going on? All sequences are progressive and 25 fps.

    Hi w00lf!
    A common issue is that many people do not know to use caution when marking an Out with the Premiere Pro playhead. The physical makeup of the playhead includes both the head and tail of a single frame. Placing the playhead on a desired out point and then marking Out will have the effect of marking Out one frame too late. To get the proper duration you are expecting, always move left one frame - then mark Out.
    If you zoom in to the playhead, you can see what I mean. In the screenshot, you can see the front edge of the playhead is on the cut. Marking In here is no problem. If you mark Out with the playhead (as shown), you are marking Out at the back end of the playhead, one frame too late and one frame in to the adjacent clip. When marking durations, you have to be very mindful of this behavior.
    Many editors make this mistake for quite some time before realizing the issue at hand. When I taught editing in various trade schools here in CA, I made sure all my students knew about this quirk.
    Thanks,
    Kevin

  • Premiere CC 2014 - "serious error and needs to shut down" - fix?

    After a few days of successful editing, I am now constantly encountering this error message: "a serious error has occurred that requires Adobe Premiere Pro to shut down."
    I am using a 2013 MacBook Pro. I have seen this concern raised on other threads, but they seem to be addressed to Windows users.
    Please help!
    Best,
    David Ketterer

    A little more info:
    This seems particularly likely to happen when I open a sequence on the timeline that has more than 5 audio tracks.
    I'm using OS Mavericks 10.9.5. Video footage is .R3D. I have the crash report if that helps.

  • Premiere cc 2014 crashed; error 600

    Please help

    Hi C Rad,
    Can you please add more details to your post. You can use this link for reference.
    FAQ: What information should I provide when asking a question on this forum?
    Thanks,
    Peter Garaway
    Adobe
    Premiere Pro

  • Premiere Pro 2014 MultiCam forgets cut points when rendering (Adobe please help!!)

    I have started using multi-cam and notice that almost always when using multi-cam the rendered results are incorrect - with many camera selections forgotten or flipped to exact opposite!
    Very frustrating - especially since you discover after render!!
    Many times when I select Camera A at some point and then later go to beginning of sequence - many of the selections have been reversed with reversal again at clip transitions - resulting in exact opposite of what I selected or random changes. Locking the tracks does not prevent this. It seems to be overriding my choices based on some program logic!!
    This is with latest Premiere Pro 2014.1 {8.1 build)
    Useless feature if you cannot get it to render your selections but rather random selection
    Wish there was a manual! And not just incomplete video tutorials that are teaser for some associate's paid training (of unknown value).
    Or at least quick forum / support response from Adobe representatives so I can be productive with the tooling.
    Another week of no answers and I will have to recreate in FCP X where multi cam seems to work fine.
    Not the best for brand loyalty, eh?
    Please help

    I'm thinking it might be operator error on this one.  Here's a process that works every time.
    1. Create a sequence matching the specs of your footage.
    2. Add your clips.
    3. Sync manually.
    4. Create a second sequence matching the first.
    5. Nest the first sequence into the second.
    6. Right click on that nested sequence and choose Multi-Camera>Enable
    7. Turn on the Multi-camera view in the Program Monitor.
    8. Play the sequence in real time, switch angles using keyboard shortcuts.  If you make a mistake, leave it for later.
    9. When you're done with the first pass in real time, go back to the normal view in the Program Monitor.
    10. Move through the sequence a second time, cut by cut, tweaking as necessary with the Rolling Edit tool (shortcut N).
    On a side note, 2014.2 is actually the current version.  You should update.

  • After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of

    After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of a solution."  When I used the trial I never received this message.  Now after purchasing it I receive this error each time I open PP and am unable to use. it.  Any ideas or support to fix this issue?

    What does the detailed crash report say?
    And have you updated your video card drivers from the GPU maker's website? (most crashes on launch are due to bugs in out of date video card drivers)

  • Updated to Premiere CC 2014 - Now getting Startup Error - Could not find any capable video play modules

    I have a late 2013 MacBook Pro Retina with NVIDIA GeForce GT 750M 2048 MB.
    Ever since the Premiere CC 2014 update, on launch, I get this error right after it shows "ExporterQuickTimeHost.bundle" loading (I tried removing this, but it still did it, so I don't think it has anything to do with the QuickTime plugin):
    Adobe Premiere Pro Startup  Error
    Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again.
    I never got this in the CC version. I have the latest CUDA driver: version 6.0.46  &  GPU Driver: version 8.26.21 310.40.35f08
    The computer is unusable for about 4-5 mins after this happens until it all clears up. This whole process takes up 7-8 mins!
    This same thing also happens with Prelude CC 2014.
    If anyone knows what's going on I would be very grateful.
    Thanks, Maz

    I found a solution that worked for me. Seems to be a permissions problem. Here's the solution I found (found it here: CC 2014 startup issues : Adobe Premiere Pro):
    In the finder menu click and hold on the GO menu. Hold the option button and the User library will show up. Click the User Library.
    In that folder go to preferences and find the adobe folder.
    Right click on adobe folder and click get info.
    In the Sharing & Permissions section there should be three names.
    All should say Read & Write next to them.
    Unlock the lock, switch them all to read and write.
    Then click on the little gear directly under the names or to to the left of the lock and in the pulldown click on "apply to enclosed items.
    Then lock the lock again.
    Now go to your OS Hardrive and click on Users, your user name, Documents.
    Find the adobe folder there.
    Right click on adobe folder and click get info.
    In the Sharing & Permissions section there should be three names.
    All should say Read & Write next to them.
    Unlock the lock, switch them all to read and write.
    Then click on the little gear directly under the names or to to the left of the lock and in the pulldown click on "apply to enclosed items.
    The lock the lock again.
    Wait 1 minute. Then launch Premiere.
    This fixed it for me.

  • Missing renderer error in Premiere CS6 plus three more errors

    I just tried to open a saved project and now get a Missing renderer error in Premiere CS6;
    "This project was last used with Mercury Playback Engine GPU Acceleration (CUDA), which is not available on this system. Mercury Playback Engine Software Only will be used"
    I then click OK and get a new errror:
    The preset used by one or more sequneces in this project requires third party components that could not be located. These sequences will be modified to use a custom sequence setting instead ...."
    I then click OK and get the error:
    "Adobe Preniere Pro CS6 has stopped working"
    This is the same computer thta created the project and nothing physical has cahnged. I reboot try to create a new project and get the error:
    "Sorry a serious error has occurred that requires Adobe Premier Pro to shut down. We will attempt to save your current project"
    I cant do anything with premiere CS6 at all.
    HELP!

    The first two can be solved pretty easy, but won't help much in light of the third.  We need to solve that one first.  Once you get PP to open and remain open with a new project and new sequence, then we can fix the first two.  So...
    FAQ: What information should I provide when asking a question on this forum?

  • Premiere CC 2014 GUI renders very slowly

    Hi there
    I'm using Premiere CC 2014. It worked very well and I did a lot of stuff with it. But since today the GUI renders very very slowly (look at my video). I didn't change any system settings, I didn't installed a program and there was no update.
    Thanks for your help,
    Samuel

    Which Mac os?  10.9.3 or 10.9.4 or ???
    next link says After Effects, but check YOUR permissions !!!
    -http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
    -Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
    -Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    -more Mac 10.9.3 https://forums.adobe.com/thread/1491469
    -and https://forums.adobe.com/thread/1507936

  • Does Premiere CC 2014 use OpenCL acceleration in H.264 encoding or just for rendering?

    It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?

    Kenneth Badertscher wrote:
    It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?
    Transcoding is entirely CPU-bound.  It's not something that can easily be parallelized, so there's no win in trying to send it to the GPU.  The GPU can be used in exporting if you've added accelerated effects, or if you scale the video to a different resolution.  Things that can be parallized fairly easily.  Changing from one video format to another isn't one of those things, unfortunately.

  • "Adobe Premiere Pro 2014.1 has stopped working" Open Project Error

    Hey, everyone.
    I recently tried to re-open a project file that I created earlier today. As soon as it loads, the familiar "Adobe Premiere Pro 2014.1 has stopped working" window comes up.
    I created a new project file and it seemed to work fine. When I first started this project, I was having trouble using a ".m2ts" AVCHD movie file (PPro would crash in a similar manner), so I used Media Encoder to change it to a ".mov" Quicktime file. Seemed to work fine after I did that. This new issue only arose once I tried to re-open the project file after shutting down the computer.
    Got any suggestions?
    -Ross

    Correction - I converted the ".m2ts" file to an ".mp4" file, not an ".mov" file.

  • Blurry / Pixelated R3D images in Premiere CC 2014

    FYI, for anyone else (like me) who has experienced pixelation / blurry images when viewing certain R3D files on the timeline or in the source window in Premiere CC 2014: this issue can be solved by right clicking on the problem clip(s) in the timeline or in the project files panel, selecting "Source Settings," and clicking "Save to RMD." You'll see the image become fully sharp again immediately.
    This blurriness happens even when the still and playback resolution settings are set to "Full" in the program and source windows, and it isn't fixed by adjusting sequence settings. It was still visible even after exporting to Quicktime files, which created a huge headache for us as we tried to figure out what we were doing wrong in our sequence or export settings. Turns out both of them were fine, it was just this "Save to RMD" glitch.
    An Adobe staff member replied and said they will fix this in around a month: Red footage pixelated on Import into AE.

    Update: Unfortunately it's not all good news.
    Trying to render out to H.264 wiht Mercury CUDA still gives a crash rendering with the typically uninformative 'Unknown Error'. Software rendering does not, but it's very slow.
    Miraizon Codec and the Premiere native Cineform also crash with 'unknown error'. However I can render out using Cineform Mov at 12bit using my registered copy of Cineform. Not fast, about 1/8 real time.

  • After effects error: rendering error while writing to file. Disk full.

    Hi,
    I tried to render a video in AE CC 2014, with RGB + Alpha as I wanted to keep the background transparent (rotoscoped) so that I can then use it in Premiere.
    I chose to export in Quicktime, with uncompressed 8bit.
    After it rendered it for a little while I had a window pop-up saying
    After effects error: rendering error while writing to file "E:...blabla". Disk full. The file may be damaged or corrupted. (-1610153463).
    I read a thread posted in the forums but i do not understand the solution provided there.. What is a POD??
    I have a Win7 Ultimate, x64. Plenty of disk space, and 16 Go ram.
    Please help, I canoot go further in my project with this bug...
    Jaywaii

    Is the drive you are rendering to formatted FAT32 by any chance? If so you can only render up to 4Gb for one file. Try rendering out a TIFF sequence instead. Litte tip - push the LZW compression tickbox in format options for a lossless compression, this will keep you file size way down.

  • Premiere cc 2014+ENCODER cc 2014

    ЗДРАВСТВУТЕ появился вопрос:используя Premiere cc 2014 вместе с ENCODER. при экспорте в него и выводе образуются офлайн кадры!
    какова вероятность, что это глюк или я не правильно настроил что-то не так?  ENCODER cc 2014 - обновился до версии где голубой интерфейс, а Premiere- нет!

    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 CC 2014 on mac pro OS 10.8.5

    Hi,
    I've installed Premiere CC 2014 on my MacPro 5,1 running OS 10.8.5 and have had difficulties getting it working properly. 
    At first the transport controls weren't working at all.  Seemed to have fixed that by repairing permissions in the users folders etc.
    Then I couldn't get video out to my reference monitor via BlackMagic MiniMonitor PCI card.
    Most of the issues I'm seeing on the forum deal with either the newest MacPro, or Mavericks.  Have there been issues with older systems?
    System Specs:
    24GB Ram
    2.4GHz Octo core
    GTX 680 4Gb
    GT 640 2Gb
    CUDA Version 6.0.51
    NVidia Web Driver 313.01.04f01
    BlackMagic Desktop Video 9.9.3
    I'm also running Resolve v10, and FCP v7.  The monitor works in both those apps, and I am loathe to upgrade to the newer BlackMagic drivers as I believe it breaks FCPv7 (which I occasionally still have to use).

    I am on my 12th version of a project. I have tried turning off GPU acceleration (that worked for encoder crashes) but had a crash shortly after turning it off.
    Most bothering is that the crashes will occur without any typical action, it will happen while rendering, while moving a clip in the timeline, importing footage, viewing footage in the source window, pouring myself a cup of coffee while not even touching the computer... it is mind boggling. I have also had crashes in After Effects and Speed Grade. I have worked with footage on a G-Raid connected by Thunderbolt with running the project file on the same drive, different drive and locally. I am sticking with running it locally (with all associated files on the external) for now as I continue to troubleshoot.
    My system specs:
    Example error report from Premiere:
    20140206-Premiere_Error - Google Docs
    Example error report from Encoder (pre-acceleration shut off):
    20150205-EncoderError - Google Docs

Maybe you are looking for