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.
Similar Messages
-
CS4 media encoder crashes if On2, 2 pass selected
Hi,
I have tried this with several .mov files of different sizes,
both in pixels and in duration. (from 6 minutes to 5 seconds)
When I encode to F4V everything is fine.
When I encode to FLV with ON2 and 1 pass everything is fine.
When I encode to FLV with ON2 and switch on 2 pass the
progress bar stops at the half way point for a while and then Media
Encoder closes. A zero byte file is left in the directory.
I am using CS4, on windows XP. I have downloaded all updates
for my Adobe products. I have restarted my computer. None of these
things make any difference.
It crashes every time with 2 pass on.
Addition to post.
I have now reinstalled flash pro CS4 and media encoder.
BEFORE checking for and installing any updates I tried encoding a
completely new file and experienced exactly the same crash when set
to ON2 2 Pass.
I then installed all updates again. No change, same crash of
Media Encoder.
MarkHi Mark,
I tried encoding a source mov file to On2 VP6 with 2 pass and
it worked for me for both CBR as well as VBR case. This was on
Windows XP and I have Premiere Pro and AME installed on the system.
If you import the file directly into AME (instead of sending
it via Flash) and then encode, do you still get the crash?
Thanks
Aurobinda -
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. -
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, -
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> -
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.sysSome 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 -
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 Issues After Upgrade from CS4 to CS5
I've been running CS4 and doing encoding to .flv and .f4v formats for sometime now without any issues. I downloaded Photoshop CS5 and then the entire design CS5 suite soon after. Since then, I can not encode videos properly. Both CS4 Media Encoder and CS5 Media Encoder export audio with no video.
Any ideas of what might have happened? Your help will be greatly appreciated.
Thanks!
JustinYou shouldn't be running version 5.5 of the Camera Raw plug-in in CS4 either. Update to ACR 5.7 ASAP.
One should ALWAYS run the LATEST release of ACR for your version of Photoshop, no exceptions. Each new release brings unheralded, unannounced and sometimes even unacknowledged bug fixes and improvements, beyond support for newer cameras.
Staying with an older version just because your camera is already supported by it is a very<euphemism>unwise</euphemism> decision. -
Windows 7, CS4 Media Encoder freezes when queue starts with sequences from Premiere. However, sequences opened from Media Encoder's "Add Sequence" export fine. Have re-installed (without first un-installing), issue is ongoing. I have several important deadlines fast approaching, please help! Media cache has been cleared (both automatically and manually), computer has been defragged and scanned for disk errors... I am absolutely stumped!
I've checked the anti-virus (I didn't think of that!), but it doesn't seem to make any change.
I've had Window Task Manager running while trying to export, it would seem that the problem occures when PProHeadless.exe opens. If I manually close it right before clicking "Start Queue", AME doesn't freeze until PProHeadless.exe re-starts once more.
Any information on forums regarding PProHeadless.exe seem more to do with an error message, not that the application itself is causing problems. I've tried multiple different sequences, all with different footage, different types of files and all with the same result.
Would a complete reformat or Windows and CS4 be the only answer? I dread the thought but I'm getting desperate. -
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-06Mea 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. -
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
AndreaI 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! -
CS4 Media Encoder doesn't render Quicktime at all
The CS4 Media Encoder will render H.264 and FLV, but doesn't render any form of Quicktime at all.
The Queue loads the project, pretends to render, but does not show progress frames. Seconds later (way too early!) there is a green checkmark that the render completed successfully. The log file looks successful with essentially the same content as for H.264 and FLV.
For example this log file shows a 1-minute sequence "rendered" in 30 seconds -- normally takes 3 minutes -- and no .mov was created.
10/29/2008 7:09:16 AM : Queue Started
- Source File: C:\DOCUME~1\MARATH~1\LOCALS~1\Temp\happyValleyBeijingMoreHighlights_5.prproj
- Output File: C:\Documents and Settings\Marathon Runner\Desktop\china\finished\happy valley beijing\more highlights\Sequence 01.mov
- Preset Used: NTSC DV
- Video: 720x480, 29.97 [fps], Lower, Quality 100
- Audio: 48000 Hz, Stereo, 16 bit
- Bitrate: DV/DVCPRO - NTSC
- Encoding Time: 00:00:00
10/29/2008 7:09:45 AM : File Successfully Encoded
10/29/2008 7:09:46 AM : Queue Stopped>always save the project before you export
Very good advice.
I would also say, save your project after any edit that you feel you can't afford to lose.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ -
Using Adobe Media Encoder with After Effects and ExtendScript
Hi,
I'm trying to automate the process of encoding a video using the Adobe Media Encoder. The project I'm working on includes allowing a user to upload a video and having that video then be encoded in different formats. I'm very new to After Effects and ExtendScript, but the two ways I see of doing this are:
1) Use ExtendScript to fire the Adobe Media Encoder through After Effects, using the 'Add to Adobe Media Encoder Queue' function. I'm not sure if this is possible or not.
2) Bypass After Effects all together and use the 'watch folder' function in Adobe Media Encoder and upload the files directly to that folder.
I'd prefer to go route 1, if that's possible, but I'm not sure it is. I was thinking that I could write a script to work with Adobe Media Encoder to encode a given video, but from what I've read, ExtendScript isn't currently supported by Adobe Media Encoder? This is true? What would be the best way to go about accomplishing this?
Thanks.I think you will have a much easier time just using option 2. I have to ask, why do you want the files to go through After Effects anyway? If you are just taking a file and converting it to ## different formats...the watch folder setup in AME would be super easy to setup.
All you need to do is ensure the user submitted files end up in a certain directory -- make that folder your watch folder and create a second folder within that one called 'encoded' or something along those lines. That way as long as AME is online and watch folders are active....you won't have to do a thing. -
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: fa9f59f642d335ee71c6667e52000d39I 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.
Maybe you are looking for
-
Getting following error on reciever RFC side Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.
-
Authentication error while exporting the SSRS reports to excel from a timer job.
Below code written in the timer job Execute() method to render the reports and get the byte array but it works fine when the application run in windows authentication, but throw error when the application extended to Form based authentication in Shar
-
-1 (Minus One) Wireless Client Rate for networked PCs with Ariport Express
Trying to figure out connection problems... Under Airport Utility > Advanced > Logs and Statistics > Wireless Clients... My MBP gets a Rate 54Mbps when I am beside it in my room, but sometimes drops down to 11 or so and then goes back up. I think thi
-
My MacBook is just a few days old and I purchased the Mountail Lion software earlier today. However the icon on the launchpad just keeps saying waiting and occasionally if it does begin to download will not progress and the download will eventually s
-
MP Related Logs and IIS Virtual directory not created After re_installation of SCCM 2007
Hi We have re-installed the IIS and SCCM secondary site. tried to intsall the MP role and DP role but it has not created any logs or IIS virtual directory in the secondary site server which is in WAN link. Trouble shooting: - checked the ports 443,44