Media Encoder crashing at end of rendering - why?

I've had issues with Premiere Pro and Media Encoder CC 2014 (on an iMac) crashing at the end of rendering for several months. I've found that PP is more reliable than ME. I've tried clearing the cache and other tips from various forums.
Today I tried rendering a modest 1.5GB file (720p @ 3mbps), and after over 2 hours of rendering, ME crashed again. I am left with an .aac and an .m4v file; the crash almost always happens when the files are to be combined.
This is ridiculous for professional-grade software, and very annoying.
Adobe, why is this happening, and is there a solution please?

After over 9 hours of failed renders, the last one failed again just 4 minutes before the end (see Screenshot). Can anyone help please?
Premiere CC and Media Encoder CC
iMac 27" 2011 with 12 GB RAM, running OSX Yosemite

Similar Messages

  • Premiere Pro, Media Encoder Crashing When Exporting/Rendering

    For the longest time if I ever tried to export or render a video longer than 5 minutes, my Premiere Pro or Media Encoder crashes. I don't know why but it is EXTREMELY irritating when attempting to make lengthened gaming videos. I have tried 15 different methods all online, to no avail. It always crashes around the 40% mark in Adobe Premiere and it isn't a corrupt project. I have literally tried everything to no avail and I finally decided I would turn here to ask for help. I reset the preferences, tried copying and pasting into a new sequence, tried reinstalling Premiere... the whole bit. My technical specifications are not the issue at hand I don't believe, but just in-case the list is provided below. Please make any response swift, my intent was to upload the video I have in Premiere by tonight!
    Technical Specifications:
    OS Name
    Microsoft Windows 7 Home Premium
    Version
    6.1.7601 Service Pack 1 Build 7601
    Other OS Description
    Not Available
    OS Manufacturer
    Microsoft Corporation
    System Name
    FRITZ-PC
    System Manufacturer
    MSI
    System Model
    MS-7821
    System Type
    x64-based PC
    Processor
    Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz, 3400 Mhz, 4 Core(s), 4 Logical Processor(s)
    BIOS Version/Date
    American Megatrends Inc. V1.1, 5/3/2013
    SMBIOS Version
    2.7
    Windows Directory
    C:\Windows
    System Directory
    C:\Windows\system32
    Boot Device
    \Device\HarddiskVolume1
    Locale
    United States
    Hardware Abstraction Layer
    Version = "6.1.7601.17514"
    User Name
    Fritz-PC\Fritz
    Time Zone
    Eastern Standard Time
    Installed Physical Memory (RAM)
    8.00 GB
    Total Physical Memory
    7.95 GB
    Available Physical Memory
    5.97 GB
    Total Virtual Memory
    15.9 GB
    Available Virtual Memory
    12.4 GB
    Page File Space
    7.95 GB
    Page File
    C:\pagefile.sys

    Some general questions/ideas...
    More information needed for someone to help... please click below and provide the requested information
    -PPro Information FAQ http://forums.adobe.com/message/4200840
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    For Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
    What are you editing?
    Codec & Format information, read both links in reply #1 http://forums.adobe.com/thread/1270588
    Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
    http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
    Free programs to find file information for PC/Mac
    Have you tried the NEW ITEM process to insure your sequence matches your video?
    See a link on page #5 at http://forums.adobe.com/message/2276578
    And, finally, for shutdowns, you MAY have a hardware heat problem
    Read Bill Hunt on BSOD shutdowns http://forums.adobe.com/thread/772169
    -win32k.sys BSOD http://forums.adobe.com/thread/1404938?tstart=0
    -and an Encore fix http://forums.adobe.com/thread/1060443

  • Premier Pro CC and Media Encoder crashing on long file export.

    Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
    I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
    I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
    I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
    From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
    to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
    to .mov  Prores 422HQ  1080P                         22 Minutes
    to .mov H.264  1080P                    22 Minutes
    to .m2v Mpeg 2 1080P                                                22 Minutes
    From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
    to .m2v Mpeg 2 720x480 format                         13 Minutes
    to .mov  Prores 422HQ 1080P                             13 Minutes
    to .mov H.264  1080P                                                             14 Minutes
    to .m2v Mpeg 2 1080P                                                            14 Minutes
    Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
    I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
    Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
    I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
    Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
    And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

  • Media Encoder crashes when exporting from Premiere Pro

    Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
    Any idea why Media Encoder will crash?

    Try turning off GPU acceleration.

  • Premire Pro CC 2014 and Media Encoder Crash During Launch

    Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.0.169
      Application Timestamp: 536f4f89
      Fault Module Name: ImageRenderer.dll
      Fault Module Version: 8.0.0.169
      Fault Module Timestamp: 536f2c18
      Exception Code: c000001d
      Exception Offset: 00000000001f5382
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 1033
      Additional Information 1: 0b2d
      Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
      Additional Information 3: fa9f
      Additional Information 4: fa9f59f642d335ee71c6667e52000d39

    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.

  • Media Encoder crash in Windows 7

    I just finished building a new machine to take the place of my old one. I'm using CS4 Master Collection. I don't use the video tools a lot but last summer I put together a presentation using Premier and created an avi file from it using Media Encoder. I worked on this for a couple of months and it always worked fine.
    Well a coule of days ago I decided to see how fast things would run on my new box so I ran the same project. I opened it up, clicked "export" and then "media" (I think that's it, I don't have it up and running at the moment). Media Encoder opens up at that point. About 20 seconds into it, my computer crashes and reboots. No BSOD, no freeze up, just pow, shut down and restart on its own. I've tested this a few times and even chose mp4 output to see if that made a difference. None. Same deal. One time when I opened up Premiere the whole machine froze but mostly I can get to that but Media Encoder crashes the system.
    I read that this was a problem in the RC days of Windows 7 but I figured the Adobe updates would have handled this by now (I did run the update so everythings current - CS4 and Windows 7). I've run several stress tests (Prime95, memtest, furmark, etc, including thorough drive tests with WD diagnostics) before loading up my programs and done a lot of stress testing after that too. in fact I'm running Prime95 now and no problems.
    What's going on with this? Anyone know? (I want to submit this to Adobe bug support as well but can't find a link for that)
    Here's my system:
    OS = Windows 7 Ultimate 64 bit
    Motherboard = GIGABYTE GA-X58A-UD5 (BIOS v 5)
    CPU = (1) Intel Core i7-930 Bloomfield 2.8GHz LGA 1366
    RAM = (12GB total) CORSAIR XMS3 6GB (3 x 2GB) DDR3 1333 (PC3 10666) 7-7-7-20 Model TR3X6G1333C7 G
    Cooler = Noctua/XION NH-U12P SE2 (2 fans)
    Video = (1) EVGA 512-P3-N871-AR GeForce 9800 GTX+
    Sound = HT | OMEGA CLARO Plus+
    Case = LIAN LI PC-P80 or PC-A77F
    PSU = CORSAIR CMPSU-HX1000
    Storage = (2) Intel X25-M 80GB SATA II MLC SSD RAID 0 (on the Intel controller)
    Storage = (4) yet to be determineed HDD's (probably going to use WD7502ABYS) RAID 10 (on the Intel controller)
    Storage = (1) Western Digigal WD1001FALS 1TB HDD for my DVDs
    Storage = (1) Western Digigal WD5001AALS 500GB HDD partitioned in 3 parts for clones of the OS drive in case of emergencies (this is in addition to clones and backups that are on spare drives outside the box)
    Optical = (2) LITE-ON DVD Writer - Bulk - Black SATA Model iHAS224-06

    Mea Culpa.
    I misread the big 7 as meaning PR7. Sorry to mislead you and to have misread your post.
    It could be a myriad of things, but look at the second link in this link: Some suggestions...
    There is some info requested, like Process Explorer (not Task Manager) and DXDIAG. Maybe that will shed some light, but temps and voltages are the first suspects.

  • MEDIA ENCODER crash error: c:ame820_win\releases\external\adobe\mediacore\mediafoundation\api\  PLEASE HELP

    WORKSTATION HP Z600
    XEON E5645 12GB RAM NVIDIA QUADRO 2000 WIN 8.1 64bit
    BLACKMAGIC DESIGN ULTRASTUDIO SDI
    good morning,
    I have some problems with premiere pro cc 2014 release 2
    the most important is that Media Encoder crashes and the following error:
    c:ame820_win\releases\external\adobe\mediacore\mediafoundation\api\
    The second problem is that when I open the software you group all the windows on one side.
    Does anyone know what I need to do to solve these two problems?
    please help
    Andrea

    I do have a 64 bit OS - Win 7. The RAM does provide a noticable difference in performance - things are much more "snappy" now, which I'm enjoying, but hasn't eliminated my problem.
    The encoder does not stop at the same point, it seems to be quite random. I can view the files that I've exported (up until the point they cut off) and there's nothing going on in the clip that would be any sort of red flag - in other words, it is not stopping the coding at a point where a new color correction or title is being introduced, it had all happened previously. This is my first large project on CS4, and I don't have anything else to export at the moment!
    I'm not running premiere in multi-monitor mode: I've got a 24" widescreen monitor that is my sole monitor.
    I have COMBED the interwebs trying to find a resolution to this issue, and I am no where... I'm currently installing CS4 on a XP machine that I have that is pretty robust, and am going to try encoding on that, just to see if I get a different result.
    Any suggestions at all would be MOST appreciated!
    Thanks!

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • Adobe Media Encoder crashes when I open a file

    Adobe Media Encoder crashes when I browse to open a file.
    I have a Creative Cloud subscription.
    I have uninstalled and reinstalled the program through the Creative Cloud service. No change.

    Thanks for responding.
    Yes, I am trying to utilize Photoshop CS (8.0) and I run Windows 7.1. I installed this from Adobe's Creative Cloud. The program opens, and I am able to open a Photoshop file with it, but then Windows tells me that there is a problem and is shutting down. I'm not sure would the problem might be.

  • Media Encoder Crash on Launch- ?

    Media Encoder crashes on launch. It's a brand new install on a MacPro 3.1 with a brand new MacOs10.8
    It runs through the list of plugins and resources that it loads with the Logo Screen but halts and crashes on loading CoreAudio...
    Please help?
    In desperation I deleted it with the hope to re-install, but can't seem to find an option for the install through Cloud...
    Thanks!

    Stumbled across this at around 3am today while still troubleshooting. Sad to see no new replies yet. I'm having the same issues as well FireTrigger. (and, at a new job to boot, my employers are starting to wonder if I'm worth my salary at this point, haha!)
    Fresh install of 10.9 with CC - AME crashes on startup with a coreaudio issue on thread 0.
    Fresh install of 10.9 with CS6 - same deal
    Fresh install of 10.8 with CC - same deal
    Fresh install of 10.8 with Cs6 - same deal
    Seems like it's a permissions issue, as from the error report, it looks like it's trying to create a folder (or write to one maybe) for coreaudio.
    Tried trashing and resetting prefs. No good.
    Tried resetting PRAM. No good.
    Log out of CC, log back in - No good.
    Unistall, reinstall, retry - No good.
    Reboot, check for updates, etc., you name it. - No good.
    Repaired permissions with disk utility and Onyx - No good.
    There's no plugins, no other software, no installed fonts aside from system standard fonts. This is a completely empty install of OSX with Premiere on top of it.
    I've wiped the whole machine out and re-installed on a clean drive about 10x now, no luck, same issues across the board.
    The hell of it is that I dont even need AME for my workflow, but because it's obviously broken, I can edit a job inside of PP all day long, but there's no way to export it, premiere crashes
    System specs:
    Mid 2010 MacPro
    12 (2x6 core) Xeon 2.8GHz
    48 gigs crucial ram
    ATI Radeon 5870 1GB
    1TB WD internal (stock)
    3x 3TB seagate7200rpm internals.
    My next steps in troubleshooting = going to yank all the internal drives and install a fresh, 3TB bare drive and start over, we'll see what happens.
    If no luck, I'll move over to testing on a trial copy of PrP CS6 absent the creative cloud if possible. I'm beginning to wonder if that's the source of it all.
    I'll report back, and will edit this post with a URL to pastebin with some error reports. Would add now but had to run into the office for some meetings.
    Good luck with this one y'all. Really nasty issue here, never experienced anything like this with adobe's stuff, and I've been a power user since CS2.

  • Media Encoder Crashes constantly

    I have Masters cs5. I have tried on several occasions to convert something and everytime i try with almost any format to any format, media encoder crashes.
    Is there some type of maintenance or trouble shooting i could do for this?

    Have you installed the recent updates?

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Premiere Pro and Media Encoder crash while rendering H.264

    Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
    It's only while rendering H.264 - other formats seem to work fine.
    And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
    It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
    I've tried disabling CUDA and my overclock to no avail. Please help!

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • CS4 Media Encoder Crash after rendering - two files, help?

    I'm not a professional so I would appreciate any advice you can offer.  I was encoding a WMV HD video (edited in Premiere Pro from CS4) that was just under 2 hours long.  On an i7-920 with 9GB of RAM, it took just over 16 hours.  At the end of the encoding, the Media Encoder bar displayed 0:00:00 time left.  But it then froze at that point for about 30 minutes.  Then the program crashed.  I planned to take these WMV files and put them, via Encore, onto a dual-layer DVD with a few other special feature-related videos. 
    I now have two versions of the file in the destination folder, one that has the title I gave it and another that has a "._00_" before the title.  Both files are .wmv files and the one with the normal name is 6.64 GB whereas the one with the ._00_ before the name is 6.60 GB.  Both have problems if I try to play them beyond the 60% or so point.
    Is there a way to salvage these files without another 16 hour render? 
    How long should I expect, on a normal/successful render, for Media Encoder to continue to process the file after the countdown reaches 0:00:00?
    Thanks.  Any advice for this very untrained editor would be appreciated.

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • Premiere Pro CS5 - Media Encoder Crash when Exporting to MPEG-2

    System:
    Core i7 920 @ 3.8 Ghz
    Gigabyte X58A-UD3R
    12GB DDR3 1600
    External Sound Card - M-Audio ProFire 610
    OS Drive - 2x300GB WD Raptors - Raid 0
    Project Drives - 3x300 WD Raptor - Raid 0
    Video Card - Geforce GTX 285 1GB
    Adobe Premiere Pro CS5 and Media Encoder CS5 continually crashes or hangs every time I try to export to MPEG-2.  I can successfully render to every other codec without any issue, but need the MPEG-2 for an Adobe Encore Project.
    The project is approximately 38 minutes long and contains AVI and MP4 files, all of which were ripped from DVDs as I'm producing a reel for a producer who provided his DVDs for me to rip and use as content.
    Possible issues:
    1.   Currently have Magic DVD Ripper and DVD Fab installed (codec conflicts?)
    2.   Originally ripped the DVDs at 630x360 (my mistake - hadn't really worked with a DVD ripper before and was the largest avi pre-set) and I'm exporting to MPEG-2 standard 720x480 Widescreen)  (I know I should've just ripped them as the original lossless MPEG-2 files - I'm a tool)
    2.   Blank space in the timline (there are a number of these)
    I would like to get some input before I try to export to MPEG-2 again as I blew a capacitor on my old mother board (Gigabyte x58-ud3r) after I had gotten my computer to start rendering a MPEG-2 after about 50 tries to export/launch media encoder set on MPEG-2.  I just installed my new motherboard to replace it.  Clearly MPEG-2 taxes the system more so than any other codec (from what I can tell).  However, I thought the issue with the blank space/no media in the timeline was fixed with CS5.  I saw in a previous post that someone thought that ffdshow was conflicting with AME.  I don't have ffdshow, but I believe that's a ripper program like Magic and DVDFab.

    I experienced this at one point.  Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime.  (I have no idea why the quicktime player would have an impact.)  However, reverting to an earlier version of Quicktime fixed the problem.  Search this board using quicktime as a search phase.  The quicktime web site allows you to download the earlier versions.  I'm not at my editing machine, but I believe that I am at version 7.5.2.

Maybe you are looking for

  • Advantages of JAVA stack on ECC 6.0

    Hi There Can any one please make me clear about the adavantages of  JAVA stack on ECC6.0, how does it helps our business, as tehre are no JAVA relaetd components in our environment , now we are on ECC6.0 ABAP stack, if this is the case how to  go ahe

  • Adobe Acrobat 9 Announced today!

    lots of fun and serious features! http://www.adobe.com/products/acrobat/ Jon

  • Some websites are loading without images

    I recently upgraded Firefox, and since doing so some sites have not been loading correctly. They load fine in other browsers, but in Firefox they show up in a strange format of bullet points and the information appears in a very simple, list format.

  • Problems installing Oracle 9i Release 2 in windows xp prof.

    When I choose an instalation type for example: Personal, the installation dies in 31% (phase: copying installation types). Then the installer fails. Please help me

  • Table for GL Carry forward balance

    Hi Can any one tell me the table where the carry forward balance of GL is stored.  Actually when we do faglgvtr the system will carry forward the previous year balances to the current year.  I want to know in which table those balances are stored . t