Setting parameters in Adobe Media Encoder?

Hi,
I've been trying to encode a video using Adobe Media Encoder, but it seems that when I change the parameters (eg. such as when I change the frames-per-second from 30 fps to 15 fps), it doesn't make any difference to the size of the output file. What am I doing wrong?
Thanks! Any advice you can offer would be very, very much appreciated.

Profile & Level also affect overall bitrate and it looks like you have yours set at the highest setting: Profile: High & Level: 5.1
Try turning on Match Source for these two properties. At a frame size of 460x530 you'll probably get Profile: Main & Level: 3.1
The lowest manual setting I can set for a frame size of 460x530 is Profile: Baseline & Level: 3.0

Similar Messages

Setting datarate in Adobe Media Encoder CC

Hi there. I am working on a Mac OSX, using After Effects CC, Media Encoder CC. I am creating 1-minute animations in After Effects timed to vocals. These animations are entirely imported mini animations put together by layers in Illustrator and imported into After Effects where they are timed to the vocals using quite a bit of Enable Time Remapping. These videos are 15 frames/sec. The pixel area is 460 x 530.
The client for these animations has requested a datarate of 200 kbps. In Media Encoder, I have the target bitrate set to .2 mbps. When I check Movie Inspector in Quicktime, the datarate is anywhere between 300 and 500.
My question is where can I set the datarate in Media Encoder? Does the target bitrate take care of this? If so, how do I achieve a datarate of 200 when Media Encoder does not allow a lower target bitrate of .19?
I have included a screenshot below of settings in Media Encoder:
Thanks for your help!

Profile & Level also affect overall bitrate and it looks like you have yours set at the highest setting: Profile: High & Level: 5.1
Try turning on Match Source for these two properties. At a frame size of 460x530 you'll probably get Profile: Main & Level: 3.1
The lowest manual setting I can set for a frame size of 460x530 is Profile: Baseline & Level: 3.0

Adobe Media Encoder CS5 Watch Folders

I'm not sure if this is the right place for this, but I couldn't find an Adobe Media Encoder forum, and since we purchased After Effects to get Media Encoder I figured this might be a good place to start.
Basically, we have a dedicated computer set up with Adobe Media Encoder, and we set up several watch folders on a network drive. We have several files that must be several different codecs, so Media Encoder is really an awesome solution to this problem. However, the only problem we've been running into is sometimes Media Encoder doesn't actually watch a folder. For example, we have a "For web" folder and a "For VOD" folder. The for web folder has had absolutely no problems as far as watching and pulling in goes. The "For VOD" will sometimes not pick up files, but if media encoder is closed and then reopened, it picks up all of the files in that folder, but then again, will not pick up additional files in that folder.
The Media Encoder machine is running on Windows 7 (due to one of the codecs being Windows only), while all of the other machines in the department are macs. I have tested setting up the same system on one of our macs and we get the same problem. We are using an SMB network, but also have DAVE clients on all of our macs.
My initial theories are that it's either: A.) Something with the network, or B.) Something on the computer interupting the network connection. One of the IT guys briefly checked out the situation, changed around some network settings, and concluded that it must be an issue within Media Encoder itself.
Also, as a side note, I did check for updates with Adobe updater and everything is up to date.
Any ideas would be fantastic! And sorry if I'm leaving out crucial information in order to solve our situation, I'm not sure what all would be relevant, but just let me know what you would need!
Thank you!

Typically, Adobe apps do not work as well in a networked environment. You might try moving the watch folders to a local drive on the Win 7 machine and see if that makes any difference. If it does, there's your solution.

Set CABAC option exporting mp4 h264 with Adobe Media Encoder cc2014

hello everyone!
i would like to be sure that i'm setting an mp4 h264 video with the CABAC option.
in the video settings of the Adobe Media Encoder cc2014 i didn't find this option.
i know that i have to put the profile at Main, and i did! somebody can tell me where i can set or verify that CABAC option in On?
thank you!
pier

AME only uses the CABAC option for h.264 so there is no setting to set.

How to set CABAC option with Adobe Media Encoder CC2014

hello everyone
i would like to be sure that i'm setting an mp4 h264 video with the CABAC option.
in the video settings of the Adobe Media Encoder cc2014 i didn't find this option.
i know that i have to put the profile at Main, and i did!
somebody can tell me where i can set or verify that CABAC option in On?
thank you!
pier
[Moved from the generic Cloud forum to the specific Program forum... Mod]

AME only uses the CABAC option for h.264 so there is no setting to set.

Adobe Media Encoder CS4 doesnt allow me to set the bitrate?

I have a Video file that I need to encode to several f4v
files at different bit-rates, but it seems I cannot change the
bit-rate in Adobe Media Encoder CS4?
I used the previous version to encode, but I cannot encode to
f4v, only flv.
Is there something I am missing here?

Sorry, found it,
Didn't realise I could scroll down to find more options in
the Encoder Window

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18 while using Adobe Premiere Pro.
Process:         Adobe Premiere Pro CC 2014
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier: com.adobe.AdobePremierePro
Version:         8.1.0 (8.1.0)
Code Type: X86-64 (Native)
Parent Process: launchd [2538]
Responsible:     Adobe Premiere Pro CC 2014
Date/Time: 2015-01-06 14:04:23.500 -0700
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Crashed Thread: 55 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Customer created test export with 777 permissions and set mount parameters to the following:
mount_nfs -o vers=3,tcp,rdirplus,intr,nolocks,async,rsize=32768,wsize=32768
-- Original mount options:
     General mount flags: 0x40 async
     NFS parameters: vers=3,tcp,nolocks,rsize=32768,wsize=32768,rdirplus
-- Current mount parameters:
     General mount flags: 0x4000058 async,nodev,nosuid multilabel
     NFS parameters: vers=3,tcp,port=2049,nomntudp,hard,nointr,noresvport,negnamecache,callumnt,nolocks,quota, rsize=32768,wsize=32768,readahead=16,dsize=32768,rdirplus,nodumbtimr,timeo=10,maxgroups=16 ,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,nonfc,sec=sys
The pcap shows once the movie is created a lockup call is responded from Isilon with Error: NFS3ERR_NOENT
478         V3 CREATE Call (Reply In 479), DH: 0xea5f731c/QBRSN-0-0-1.mov Mode: UNCHECKED
479         V3 CREATE Reply (Call In 478)
484         V3 LOOKUP Call (Reply In 485), DH: 0xea5f731c/._QBRSN-0-0-1.mov
485        V3 LOOKUP Reply (Call In 484) Error: NFS3ERR_NOENT
V3 LOOKUP Reply (Call In ....) Error: NFS3ERR_NOENT -   This is by design of OneFS, we coalesce files and then flush them out to disk which is why the commit time is accurate but the file is not immediately available. however when an async option is used within the mount options this should be avoided if writing asynchronously to the cluster. Has anyone else seen this behavior lately? (current workaround is to store locally and transfer to the cluster via Finder)

That error can happen for many reasons...one of the reasons that I occassionaly get it is because I try exporting a movie to an external drive that has been formated in the old FAT32 instead of the NTSF standard. FAT32 only allows for file sizes up to 2 gigs. And as soon as it reaches that...I would get that error. I don't know if that is why you are getting that error...but it would be easy to check. 1) are you generating a file that is over 2 gigs? 2) is your drive that you are exporting to FAT 32 (just right click the drive in My Computer and select "properties" then just look for what it says next to "file system".

Adobe Media Encoder CC 7.2.0.43 still crashes after beginning of encoding - bugs for months now!

Adobe Media Encoder CC 7.2.0.43 is still crashing after beginning of encoding! In my case this bug exists for months now and Adobe is not able to get rid of its own programming faults! The user pays a lot of money for the license and doesn't get a functioning software! I spent days to get a solution now, but NOTHING of your suggested help works!
This is my 'support' history beginning in AUGUST (!):
Sent: Thursday, August 15, 2013 ...
Subject: Bug Report
Product: Adobe Media Encoder
Product Version: CC
Operating System : Windows 7
OS version: Service P1
Concise problem statement: Steps to reproduce bug:
1. Go to Premiere Media Export
2. Stating Media Export Parameters for ME
3. Starting ME
4. Define video title and path
5. Start Media Encoder CC rendering
6. ME states 'Preview not available'
7. Rendering aborts after about 15 sec.
8. Media Encoder CC crashes, no matter which kind of video! Every time.
9. Direct 'Export' from Premiere CC is possible with all the same parameters, but CC AME crashes!
10. Also installed Premiere CS 6 Media Encoder WORKS without any problems, but not the CC Media Encoder!!
Expected results: Media Encoder CC WORKING. This is still my expected result as a paying customer!
My steps to solve these problems (with Adobe's help) were / are:
- Cleant every suggested media cashes.
- Tried to render the sequences also without audio.
- Tried to render as one pass.
- Even if I try just to export ONE simple standard SONY PMW EX1 mp4 file which should never cause problems it chrashes, also without audio.
- Also if I clean all preferences and caches before, EVERY file type crashes, no matter if I try to export a video or a still picture.
- This is not happening in Adobe AME CS6 with the same files, but in CC!! CS6 still renders reliably with preview, but CC crashes without being able to show any preview.
- Held the Shift key down while starting AME. This should reset preferences and so on...
- Deleted suggested "7.0" directories as described in other forum posts concerning this topic.
- Logged out of my CC account.
- Deinstalled and reinstalled PPro, After Effects, InDesign, Flash, using Adobe Creative Cloud Cleaner Tool. All is the newest version 7.2.
- Set GPU renderer to "Software Only". Some video cards have issues when GPU is set to "OpenCL" or "CUDA".
- Checked updates available for video driver. Latest is installed.
- Turned off "Enable Native Premiere Pro sequence import" in AME prefs.
- AMEEncodingErrorLog.txt doesn't have any content, not a single line.
NOTHING WORKED OR HELPED!
Windows Crash log: WER3A92.tmp.WERInternalMetadata.xml:
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
    <OSVersionInformation>
        <WindowsNTVersion>6.1</WindowsNTVersion>
        <Build>7601 Service Pack 1</Build>
        <Product>(0x3): Windows 7 Home Premium</Product>
        <Edition>HomePremium</Edition>
        <BuildString>7601.18247.amd64fre.win7sp1_ ... private data erased here ...</BuildString>
        <Revision>1130</Revision>
        <Flavor>Multiprocessor Free</Flavor>
        <Architecture>X64</Architecture>
        <LCID>1031</LCID>
    </OSVersionInformation>
    <ParentProcessInformation>
        <ParentProcessId>9168</ParentProcessId>
        <ParentProcessPath>C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe</ParentProcessPath>
        <ParentProcessCmdLine>"C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe"</ParentProcessCmdLine>
    </ParentProcessInformation>
    <ProblemSignatures>
        <EventType>APPCRASH</EventType>
        <Parameter0>Adobe Media Encoder.exe</Parameter0>
        <Parameter1>7.2.0.43</Parameter1>
        <Parameter2>52a18991</Parameter2>
        <Parameter3>libmmd.dll</Parameter3>
        <Parameter4>12.0.12.2</Parameter4>
        <Parameter5>5073ba44</Parameter5>
        <Parameter6>c0000005</Parameter6>
        <Parameter7>00000000000bfd76</Parameter7>
    </ProblemSignatures>
    <DynamicSignatures>
        <Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
        <Parameter2>1031</Parameter2>
        <Parameter22>4c50</Parameter22>
        <Parameter23>4c50fbaed87d7d2a6adc173c5da6a755</Parameter23>
        <Parameter24>28b8</Parameter24>
        <Parameter25>28b834131666732fe13a476b5fa8febe</Parameter25>
    </DynamicSignatures>
    <SystemInformation>
        <MID> ... private data erased here ... </MID>
        <MarkerFile>1043_ASUSTEK_G74SX_V20_WIN7</MarkerFile>
        <SystemManufacturer>ASUSTeK Computer Inc.</SystemManufacturer>
        <SystemProductName>G74Sx</SystemProductName>
        <BIOSVersion>G74Sx.203</BIOSVersion>
    </SystemInformation>
</WERReportMetadata>
Adobe team, I'm at my wits' end now and don't know how to continue. Can you help me?

https://www.youtube.com/watch?v=oJ0hz9JkLgM

Adobe Media Encoder pausing rendering while working in Premiere Pro

Hello everyone,
So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
Has anyone ever seen that?
I use Windows 8 and Adobe CC.

Hi Rallymax,
Yes I do queue footage by having an Autowatch set up on the directories where the video is written to. I rarely do a direct export unless testing new settings.
Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export. Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
Adobe Media Encoder
The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
I will try the same test as Jason, if I can find any AVHCD video and see what the results are. Will be interesting.

AppV - Adobe Media Encoder not in default location?

I'm virtualizing Adobe Captivate 5, which includes Adobe Media Encoder. During virtualization, when I launch AME, I get a message:
Adobe Media Encoder is not being run from the default installation location. This is not a supported configuration."
I never changed the installation location for Captivate... it's going to wherever Adobe has it set to go.
After I hit OK (that's my only choice, no "Don't show me this message again") the app seems to be OK... so if there's a way to change a registry key or something and just get rid of that message, that would probably be fine.

Unfortunately, video features are not supported for photoshoop cc and cc 2014 on windows 32 bit operating systems.
more info:
https://forums.adobe.com/thread/1320417

New PC, downloaded CC 2014. Flash not showing up as option to rip in Adobe Media Encoder or in After Effects. Help?

Why is .flv not an option in Adobe Media Encoder or Adobe After Effects?
Also, when Adobe Captivate converts the video it looses the Alpha channel.
Help

Thanks for taking the time to answer this question. Knowing this isn't possible at least narrows my options down. It would be helpful to provide some kind of list of what comp settings carry over into AME from After Effects. Is it essentially everything that is enabled in the Timeline? (I know that motion blur settings do.)
I'll put this in a feature request, but yes, we need the other half of After Effects Render Queue in AME in order for AME to be a good replacement for rendering from AE. I'll give you my thoughts on why Render Settings are essential before you would actually want to render with AME instead of doing so because you have to (either because you want to render in the background, or need a codec that has been removed from AE.)
1. Speed: Simply applying a Render Settings preset is much faster than manually setting motion blur, frame blending, work area, etc.
2. Reliability: Not being able to apply a Render Settings preset at the time of render is a recipe for missing a crucial setting buried in a comp, then having to redo a render and wasting time.
3. Features: As noted above, there is no way to approximate Render Queue's ability to change resolutions at render, which results in a lot of wasted time when that feature is needed.
Render Settings I think are crucial to making AME rendering worthwhile for AE users:
1. Rendering resolution
2. Work Area/Entire Composition toggle
3. Field Rendering (wait, does this mean AME can't currently render to fields?)
4. And PRESET ability these settings, so I'm not doing them manually every time.
I realize that your team clearly doesn't spend the same amount of time I do making low res H264 previews and sending final files out in H264 format, so you don't appreciate the impact of the changes you made. Moving to AME for that stuff is a real inconvenience, but implementing the settings above could help soften the blow.
Thanks,
Jerry

Adobe Media Encoder Appcrash in MSVCR90.DLL upon exit

Hello folks,
I didn’t see a forum for Adobe Media Encoder (hereafter referred to as AME), but since we are using AME hand-in-hand with Premiere, I thought I would post this here to see if anyone had any insight to why this is happening. Thank you in advance if you can help me figure this out; I truly appreciate any and all assistance!
I am the computer lab manager for the visual arts department at a community college. We teach video production courses in which we capture audio and video footage into Premiere CS5 and then export that footage to AME CS5. We do this on PC hardware (Dell Optiplex 755 and 780 units) running Windows 7 Enterprise 64 bit.
The way that I configure the master image is to install all software (the Adobe Master Collection) under the administrator account, configure settings within the programs (an example, though it is not related to this, just to give you an idea as to what I do to configure the master image – since our PCs have 2 hard drives, I launch Photoshop and change the scratch disk setting to point to the second drive) and then copy the local admin profile over to the default user profile within Windows so that all students get the same settings configured the way we want it.
Now, before I copy the profile over, I test the system thoroughly to make sure that everything is working as it should. AME functions fine prior to the profile copy. However, once I copy the profile over, and I use Sysprep for this because it is the only Microsoft supported solution for profile copying in Windows 7 that I know of, everything functions perfectly except when you go to close AME, it throws this error:
Problem signature:
Problem Event Name:           APPCRASH
Application Name:    Adobe Media Encoder.exe
Application Version: 5.0.0.402
Application Timestamp:        4b90428a
Fault Module Name: MSVCR90.dll
Fault Module Version:          9.0.30729.4926
Fault Module Timestamp:    4a1750b0
Exception Code:        40000015
Exception Offset:      0000000000042366
OS Version:   6.1.7600.2.0.0.256.4
Locale ID:      1033
Additional Information 1:     8229
Additional Information 2:     822983f92e0fd00f8f437ec0e323139f
Additional Information 3:     285f
Additional Information 4:     285f9b2b24a1e8904affbcc4b711d880
I am assuming that Sysprep resets something when it copies the profile because I can log in as the Administrator during the testing phase and this does not happen. Once I sysprep and log in as Administrator again post-sysprep, this happens not only under Administrator, but under every other account that I log in as, both local and domain, and both with admin and non-admin privileges.
I ran the Adobe Updates to no avail. No matter what, this keeps happening.
This is a minor issue as everything does work, it is just that I am getting complaints from students and instructors that this is happening. Again, thank you in advance for your help. I appreciate it wholeheartedly.

In the past (I do not know if that still applies today) there were problems with the Microsoft Visual C++ libraries that could be solved by downloading and installing the relevant DLL's from the Microsoft website. Beware, there are numerous files and you have to take care to download and install the version for your OS. Adobe tried to alleviate that problem, but may not have solved all the issues. It is worth a try.

Adobe Media Encoder CC constantly crashing during batch encodes

Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

Adobe Media Encoder CS6 Random Crashing Mid-Render

Hello -
I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
Footage:
r3d - Various resolutions, all being cut in a 2048x1152 sequence.
Quicktime mov - ProRes4444 for the most part.
Machine(s):
I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
Software:
AME- 6.0.2.81
Premiere - 6.0
I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
Any help appreciated. Thanks.

Thanks for the reply MMeguro.
Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
What worked for last night's render:
1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
3. Turned OFF GPU acceleration.
So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
Anyway, thanks again for the reply MMeguro much appreciated.

Adobe Media Encoder (AME) won't start!!

Adobe Media Encoder (AME) won't start!!
i have this problem and i can see that many people have it too!!
when you gonna tell us the solution!!!

Yes, i did.
Today, i installed a new OS windows 8.1 Pro x64. i'm also finished setting up my Creative Cloud Desktop App, installed Photoshop CC and i will try again with After Effects CC & Premiere Pro CC.
Any Recommendations !!
i hope my AME works fine after installing AF CC & PP CC.

Setting parameters in Adobe Media Encoder?

Similar Messages

Maybe you are looking for