Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

Hi there,
Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
Just updated the CUDA driver to 5.0.45 but this has not changed anything.
Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Similar Messages

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
How do I around this problem?

We need to know a lot more if we're going to help you.
What happens when you try? Do you get an error message? If so, exactly what does it say?
What version of Premiere Pro? Have you installed the recent updates? What operating system?
Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

Exporting from Premiere Pro CS4 using Media Encoder gets stop error

I am trying to export my timeline from Premiere Pro CS4, using the Adobe Media Encoder CS4 to export my timeline as an MPEG2 HDTV 1080 24, and it goes for about fifteen minutes then I get the blue screen and my computer restarts, telling me the program had a stop error. Is there a way to go around this step? Another method to get the mpeg2 without losing quality? Anything I can do?
Please offer any knowledge you have before I scream at my computer again.
Thank you

as I know Adobe products are buggy no matter what hardware you have.
I am sorry, but my experience has been the absolute opposite of what you have heard, or experienced. I have used many, many Adobe programs for almost 2 decades (maybe even more than 2 decades?), and have never observed such. I do have to admit that over those many years, I have always had a "state of the art" computer, but have made plenty of $ using Adobe software. Even with my now aging workstation, things work great. Time to upgrade though.
When troubleshooting issues, they shake out like this:
1.) system
2.) Assets
3.) Project
4.) OE
5.) Bugs
This is after troubleshooting Adobe issues from almost the time that PS hit the PC, when they were only NNTP, in what, 1985?
Now, I am not saying that your issue IS hardware, but only that that is the most likely issue, given a BSOD. Also, system is the #1 cause of issues, so that is where I start.
Good luck,
Hunt

Premiere Pro CC / Adobe Media Encode CC not using GTX980 EVGA

Generation of movies using h.264 encoding is not using GPU. Based on the logs from video card there is no usage even if the selected renderer is Mercury Playback Engine GPU Acceleration (CUDA). How can I enable its usage?

Hi mate, same here.. I can't do it work, simply.. I select GPU in Premiere and AME (gtx 970 in my PC and gt755M in my laptop, neither is working), GPU is 0% of use to do a simple video conversion.
To show that is a Adobe problem, this guy create his own exporter plugin ( SHAME ON YOU ADOBE!). With it AME work very, very fast, but i have issues too when change the video format to MP4.
NVidia GPU-accelerated H264-encoder plugin, ready for public testing
I don't know what i do. I think Nvidia and Adobe messed up very bad this feature.. Nice Adobe, i have a good GPU but i have to wait very long times (1hr videos conversion) because you guys can't do a simple exporter plugin that use GPU power.. So, stop collecting our money only and GO TO IMPLEMENT OUR NEEDS! Have a nice day.

Horrible video output quality with Premiere Pro CS4 + Adobe Media Encoder

I am trying to make some changes to a DV format file, and output as the same DV format. When the video is brought into Premiere, it looks crisp in the left-hand video box. But, when playing it on the right window and when encoding it, it comes out as a mess with substantial compression artifacts.
What confuses me is, I have experimented with a lot of codecs--even uncompressed AVI. There is no change in the video resolution--source is 720x480, as is output. I am keeping all the pixel aspect ratios the same as the source footage.
What is creating this distortion? I have no scaling of the video whatsoever in the sequence...
Is there some compression box I'm not seeing here?
I've attached a screenshot of a still from the video. As you can see, substantial artifacting around the lettering, making the text unreadable.

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Exported HD video from Premiere Pro CS4 via Media encoder Freezes mid way through video

Hi,
I couldnt find this raised by anyone else so thought id start a new thread. Ive tried a couple of times to export an edited project only to find the video is all good up until roughly half way through the video at which point the video freeezes, the time keeps moving along as if its playing but no video. It looks like the encode failed at this point. I have no problems if I split up the video and export it in smaller pieces but obviously this isnt good enough
Any ideas as to the cause?
Additional info:
Im patched upto CS4.1
Source footage is AVCHD
Project goes for just over an hour
Cheers

That suggests some failure somewhere in the encoding process. It could be something in your timeline around 43 minutes, maybe a blank space (even for a single frame), a disk hiccup causing some part to go missing, other hardware problems. It could be a myriad of things going wrong. What background processes are running, what is your hardware setup, what are the temperatures during encoding, etc. Check the second part of this link: If you need help quickly...Guideline for posting an effective question

Media Encoder doesn't start rendering when I queue from Premiere Pro

I have Premiere Pro CC and Media Encoder CC, and it seems the render in Media Encoder never starts or takes a very long time to process.
When I start exporting on Media Encoder, the preview shows up, but the encoding time stucks at 00:00:00 or 00:00:01.
If I export videos using Premiere Pro, the video exports just fine. It just that Media Encoder is not working.
This happens when I use Audio Effects on my audio files. I've been exporting audio separately and re-importing them into my Premiere Pro project so that Media Encoder will export my videos. But this takes more time to make videos.
Anyone having this issue?

[Moved to AME forum.]

Is Adobe Media Encoder included in Photoshop CS6?

Is Adobe Media Encoder included in Photoshop CS6? If it is how do I access it?
Message was edited by: Kevin Monahan Reason: added more descriptive title

No.
Adobe Media Encoder is installed by Premiere Pro, After Effects, SpeedGrade, Prelude, InDesign, and Flash Professional.

Is adobe media encoder in cloud or CS6?

is adobe media encoder in cloud or CS6? ... maybe as part of flash, flash builder or premiere?

Yes - Media Encoder will be installed when you download Premiere Pro, After Effects, or Prelude.
EDIT: Also Flash Pro

Premiere Pro error saying Media Encoder is not installed (it is)

I'm trying to export a sequence from Premiere Pro CC 2014 to Media Encoder CC. After changing all the export settings to what I want in Premiere, I go to select the Queue button and receive the message "Adobe Media Encoder is not installed. Please download and install it to use this feature. Go to https://creative.adobe.com/apps". I have Media Encoder open right now. Any idea why they aren't communicating? I'm using a Macbook Pro btw.

You need AME 8.0.1 to match that version of Premiere. The most up to date for both is 8.2.0. Try clicking on help-updates in each program rather that using CC updater.

Premiere Pro CC and Media Encoder won't start

Hey everyone,
I have a huge problem: My Adobe Premiere CC won't start. I've tried all the solutions I've found in the internet, but nothing seems to work for me
I am using OS X 10.9.3.
Here is a part of my report:
Process:         Adobe Premiere Pro CC 2014 [1153]
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 [235]
Responsible:     Adobe Premiere Pro CC 2014 [1153]
User ID:         501
Date/Time:       2014-12-10 23:51:37.341 +0100
OS Version:      Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 5BE9B722-1F73-691F-5EEF-9775088356E8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
VM Regions Near 0x1650:
-->
    __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
1   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
2   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
3   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
4   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
5   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
6   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
7   com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
8   com.adobe.GPUFoundation.framework 0x0000000109afbeb1 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
9   com.adobe.GPUFoundation.framework 0x0000000109ad521f GF::Device::InitializeContextImpl() + 2479
10 com.adobe.GPUFoundation.framework 0x0000000109ad76ae GF::Device::InitializeContext(bool, void*, void*) + 622
11 com.adobe.GPUFoundation.framework 0x0000000109af141a GF::Initialize(bool, bool, bool, void*, void*) + 2154
12 com.adobe.DisplaySurface.framework 0x0000000111bb7f84 DS::Initialize() + 228
13 com.adobe.Mezzanine.framework 0x000000010636c3cd MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 6173
14 com.adobe.Mezzanine.framework 0x0000000106369874 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
15 com.adobe.Frontend.framework   0x00000001000abe97 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
16 com.adobe.Frontend.framework   0x00000001000aadc8 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
17 com.adobe.Frontend.framework   0x00000001000cdc32 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 226
18 com.adobe.Frontend.framework   0x00000001000d4ea5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
19 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
20 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

AND Media Encoder won't start as well!!
Process:         Adobe Media Encoder CC 2014 [1284]
Path:            /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Identifier:      com.adobe.ame.application
Version:         8.1.0.122 (8.1.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [235]
Responsible:     Adobe Media Encoder CC 2014 [1284]
User ID:         501
Date/Time:       2014-12-10 23:59:55.226 +0100
OS Version:      Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 5BE9B722-1F73-691F-5EEF-9775088356E8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
VM Regions Near 0x1650:
-->
    __TEXT                 0000000100000000-0000000100088000 [ 544K] r-x/rwx SM=COW /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff93a9a292 __kill + 10
1   com.adobe.dvacore.framework   0x00000001003a28ea (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 410
2   libsystem_platform.dylib       0x00007fff9195b5aa _sigtramp + 26
3   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
4   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
5   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
6   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
7   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
8   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
9   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
10 com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
11 com.adobe.GPUFoundation.framework 0x0000000109ef7b01 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
12 com.adobe.GPUFoundation.framework 0x0000000109ed0e6f GF::Device::InitializeContextImpl() + 2479
13 com.adobe.GPUFoundation.framework 0x0000000109ed32fe GF::Device::InitializeContext(bool, void*, void*) + 622
14 com.adobe.GPUFoundation.framework 0x0000000109eed06a GF::Initialize(bool, bool, bool, void*, void*) + 2154
15 com.adobe.DisplaySurface.framework 0x0000000107845f74 DS::Initialize() + 228
16 com.adobe.ame.application     0x00000001000376e7 AME::app::MCInitializer::MCInitializer() + 12039
17 com.adobe.ame.application     0x000000010002323a AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 250
18 com.adobe.ame.application     0x000000010000d2ba AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 1802
19 com.adobe.exo.framework       0x00000001057d2bd5 exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1141
20 com.adobe.ame.application     0x00000001000167e6 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 3270
21 com.adobe.ame.application     0x0000000100047828 main + 440
22 com.adobe.ame.application     0x00000001000032f4 start + 52

Can't export (queue) out of ppro into adobe media encoder after update

i just updated everything (cuda, nvidia, os 10.8.2, 6.0.3) and now i can't export from ppro into adobe media encoder. as soon as i export out with any preset across multiple projects and hit play, i get the sheep sound almost immediately. before this gets put in the AME discussion queue consider that AME works fine either when importing an AE composition etc. so it seems to be premiere related. thanks!

Actually I'd recommend uinstalling all the adobe software on your PC if possible. Because truthfully if you have a decently fast internet connection or you have the installer for the suite on your system it really doesn't take that long to do a complete install. Plus when you do a complete install it's much more likely to fix the issue plus then you can use the Adobe CS cleaner tool which makes your odds for success much higher so that is what I'd recommend. If you follow the instructions from this link everything will go smoothly.
http://www.adobe.com/support/contact/cscleanertool.html
I know in the past I have fallen into the trap of troubleshooting something for a few days, only to end up uninstalling then using the adobe CS cleaner tool, then reinstalling and then BAM everything was now fixed lol...
Then I always ended up feeling silly for spending so much time on it instead of just doing a fresh install. Although I had no way of knowing that to begin with unfortunately. Hindsight is 20/20 most of the time.
However you can technically try uninstalling Premiere by itself if you want to try that first. If my memory serves me correctly when you uninstall Premiere it will uninstall Encore and AME as well.

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/

Rendering in Premiere CS5 vs Adobe Media Encoder? Which is better?

Exactly what the question says. Is there a difference between rendering in Premiere CS5 to rendering in Adobe Media Encoder? Leave your thoughs. Thanks!

Then I have made a mistake. I thought that the AV Export function under File>Export had been fully moved to AME. Obviously, I am incorrect.
No, you're correct: there is not Export > Movie command any longer, and hasn't been since CS3. With CS4, that particular functionality was eliminated, as all exports went through AME, and were logged in the AME queue.
Things have changed yet again with CS5. There is still no Export > Movie as there was in CS3 and earlier; everything still must be encoded through AME. However, in CS5, when you initiate the export, you have two options: Export and Queue. The latter option does what CS4 exports did: they go into the AME queue for sequential export. The former option basically launches a "headless" version of AME and exports as a one-off. The export is still being performed by AME; it's just that you don't have the virtue of it working in the background as it does with the Queue button. I've also encountered some weirdness with Export when it comes to cropping and using hardware MPE, but that's a different story. I haven't done any hard-and-fast tests of which is faster--Export or Queue--but I'd take Harm at his word that Queue is the faster option.

Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

Similar Messages

Maybe you are looking for