PP 2014.1 - Broken link to Media Encoder

Using a project created under PP 2014, I have been able to change the Lumetri via Dynamic Link to Speed grade, but I cannot Export the Sequence to Media Encoder.
Process used is as under previous version of PP:
Select sequence
Go File - Export - Media - select existing export format for DVD
Queue
AME opens but the file does not show.
PP is Not Responding
So End Task and restart same project in PP and this time use Export instead of Queue and it works.
Dynamic Link to AME is now broken!
Now I have to wait unable to use PP while each sequence is exported.
Is there a fix for this new problem?

Nothing new under the sun. Every release of an update requires several months of bug fixes before it becomes somewhat stable.
There is a reason why many choose not to update at the earliest moment, but wait 6 months or longer for the first bugs to be resolved.
This is especially true with CC, now that Adobe appears to have moved the beta-testing phase to the end-user, meaning you and other early adapters have been promoted to 'guinea pig', whether you like it or not.

Similar Messages

After Effects not dynamic linking with Media Encoder 2014

Hi
I updated from an older version of Media Encoder to Media Encoder 2014, and now it won't link with AE. I've updated AE also.. and yes, have tried turning my computer on and off again.
Am I missing something here in a preference setting or is this a known issue?

Running OSX 10.9.3 on 3.5Ghz i7 iMac
Transfer comp to AME via Composition drop-down menu , comp settings (for argument sake) are 1920x1080p 25 fps.. although this has never affected the dynamic-link until I updated AME.
I'm picking because it's a 'new app' rather than an updated one in CC that it's not being recognised/picked up by AME2014.
Seems like it'll be a preferences setting that I can't seem to find, but open to helpful suggestions.
Cheers

Media Encoder CC 2014 Exports larger file than Media Encoder CC with same settings

We like to deliver final exports to most of our clients with the following settings:
Format: Quicktime
Codec: H.264
Quality: 100
1920x1080, 23.976, progressive, square pixels
use maximum render quality
audio: uncompressed, 48khz, stereo, 16 bit, single track
When I used to export a ~5 minute video using these settings with Premiere or Media Encoder CC (7.2.2.29), I would get a file ~1GB. If I export a ~5 minute video using these settings in Premiere or Media Encoder CC 2014 (8.0.1.48), the result is ~ 4GB.
Any thoughts on why this might be? I assume it's a user error but I can't nail down what it is.
Thanks for your help!

Hi matthewrichie88,
I used the same settings that you have mentioned above on a Windows 7 computer and got the same file size with both versions of Media Encoder. Please specify if you have a Mac or a Windows and which OS exactly? It would really help if you can post screenshots of your export settings with both versions. Give more details about the source files as well.
Thanks!
Rameez

Adobe Media Encoder CC 2014 has NEVER opened on my computer.

Can somebody please help with this?
Process:         Adobe Media Encoder CC 2014 [468]
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:         ???
Code Type:       X86-64 (Native)
Parent Process: launchd [174]
Responsible:     Adobe Media Encoder CC 2014 [468]
User ID:         501
Date/Time:       2014-08-28 07:43:01.054 +0100
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 50100364-D4BE-B73C-C1BB-D5ADEEFB650C
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE
Referenced from: /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Reason: no suitable image found. Did find:
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
Binary Images:
    0x7fff6f3ef000 -     0x7fff6f422817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld
    0x7fff8ff53000 -     0x7fff8ff53fff com.apple.Carbon (154 - 157) <45A9A40A-78FF-3EA0-8FAB-A4F81052FA55> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff92ed5000 -     0x7fff92ed5fff com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff92faf000 -     0x7fff92faffff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff92fc7000 -     0x7fff932c5fff com.apple.Foundation (6.9 - 1056.13) <2EE9AB07-3EA0-37D3-B407-4A520F2CB497> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff96923000 -     0x7fff9698ffff com.apple.framework.IOKit (2.0.1 - 907.100.13) <057FDBA3-56D6-3903-8C0B-849214BF1985> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff97732000 -     0x7fff9798cff9 com.apple.security (7.0 - 55471.14.8) <EA03E140-2509-3A07-8440-2DC97C0D478B> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff9951c000 -     0x7fff9951cfff com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f6
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: M4-CT512M4SSD2, 512.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
I, of course, have no idea what any of the above means. Please help.

Looks like one component in Media Encoder is either missing or corrupted somehow.
Could you uninstall Adobe Media Encoder CC 2014 and please make sure all files are deleted after uninstall? Then, please try re-installing it.

Problem with plugins not rendering from Media Encoder CC 2014

Hi, I am exporting a video made in AE CC 2014 with several plugins, into Media Encoder CC 2014. When I try to render the video in Media Encorder at H.264, at 720PX in an MP4. The video renders but does not show any of the plugins that I had used. Any advice?

These are the plugin that I am using:
“Element, ft-Lens Distortion, FL Out of Focus, Sure Target and Particular.”

Adobe Media Encoder Dynamic Link Server NOT CONNECTING to Premiere Pro

I have Media Encoder CS5, as part of the Creative Suite 5. My programs say that I have no updates to install, so everything is up to date.
I am having an issue with the dynamic link server.
Here's what has happened thus far.
Recently when I have tried to encode a project sequence from Adobe Premiere Pro it DOES NOT work. This is the first time that has happened.
I repeated the process and again, it still happened, unable to connect to the Dynamic Link.
The Error messages that I was getting was "could not read from source. Check if it has been moved or been deleted"
Once, I received this, I went to check to see if all files were linked properly, and they were. Everything was rendered and all was good in the timeline and the project itself.
Yet, again, the error message appeared.
Then I tested a previous project that I knew had been exported and worked through Adobe to Media Encoder. And all the files were linked properly and yet again received the error message I wrote above.
Then I thought the Dynamic Link itself wasn't working properly, so I tested importing an Adobe After Effects Comp into a Premiere Timeline and it DID WORK.
Then I went and tested if a video file of an already exported project would be able to sync to Media Encoder. And this WORKED.
I then went to add the file directly from Media Encoder and when I went to add a sequence from a saved Premeire File, it would take about 5 minutes "Connecting to Dynamic Link Server", to then state, "Connecting to Dynamic Link Server Failed"
My question is, how do I fix the dynamic link between Media Encoder and Premiere? Because, additionally, importing and After Effects Sequence works with Media Encoder.

I've been searching/troubleshooting for days, none of the firewall, new shortcuts in folder, antivirus, you name it I tried it even wiped my system which seemed to work at first..
What did it for me in the end was I had Dxtory (a software recorder, for recording gameplay) running on startup, and somehow it interfered with only Premiere projects in Media Encoder, I could still import AE projects go figure.
Check all the programs you have running or use sometimes, if they have some sort of hook into other programs/deal with video/codecs this could be your problem too!
Thanks to everyone trying to solve this problem!
-JonOfAllGames

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

Media Encoder 6.0.3 : Unable to read from the source

Hi !
I'm using Premiere and Media Encoder in tandem for a while now for a big project, but since last week, something screwed up and I can't export from Media Encoder anymore. Every time I try to encode with Media Encoder, it tries to conect to the Dynamic Link server, and then fails to do so, and shows the error in the title. And since I cannot encode directly in Premiere (it just doesn't work, but that's nothing new), that means my project is on hold until the problem is fixed...
I googled my problem and find some solutions. I tried to create shortcuts to Premiere in the dynamiclink and the Keyfiles/dynamiclink folder, but that didn't work.
I uninstalled and reinstalled CS6 two times (the second time with the CC Cleaner Adobe provides to clean after uninstalling CS6), but that changed nothing.
I tried to unlock the permissions to the folders of my project, but that didn't help to solve my problem.
Now I'm out of ideas, so I post here, hoping for an answer. I'm almost certain the problem is from the Dynamic Link with Premiere, as the link between Premiere and After Effects doesn't work either (anything not related to Premiere works well though, After Effects can link with Media Encoder, but Premiere won't. The file is still being transfered to Media Encoder, but it can't start the encoding).
I previously had CS5.5 on my computer (and maybe CS4, but I don't remember), but I'm almost sure all of them are all wiped now, with the CC Cleaner and all.
I should mention that I'm using these softwares as part of the CS6 Master Collection (everything is up to date according to the Application Manager) on a Windows 7 x64 hardware

Update : I created a new account on my computer to test if the problem still occurs. And surprisingly, it doesn't occur... I'm able to use the dynamic link properly, and all is up and running.
It works as a workaround for now, but I would seriously like to solve the problem on my main account. So something is wrong on my main account. I checked my firewall, but that seems okay (no results even when my firewall is deactivated).
I should mention that the path Media Encoder use to link with Premiere has non-ASCII characters in it (such as é, è, etc.). Could that be the cause ? If so, how can I change that path ? (currently to User/<username>/AppData/Local/Temp). Is there an option, or even an environment variable for that ?
I've also noticed that the file created for the cache on my main account is slightly smaller than the one on my test account (749 ko on main and 778 ko on test). This should be the same file, so the weight should be the same... Could it be some kind of corruption that prevents dynamic link for working ?

Media Encoder Crash

Hello, I downloaded the 2014.2 version of Adobe Media Encoder, but I can not open the program, an error occurs immediately during the program startup load.
I've tried installing and desisntalar the program several times with the CC, but still the same error occurring.
My operating system is Windows 10 Pro Tecnical Preview.
If anyone knows how to help me, I'll be grateful!
Massochin, Tiago.
sorry for my english...

What version of AME are you running?
What is the source file? PPro project or a single asset?
Pick another project or asset to convert to Youtube preset. Does it still crash?
Was this working before and it just started recently?

Adobe Media Encoder CC 2014 + Dynamic Link = no audio!

When exporting to any file from AE via Adobe Media Encoder CC 2014 (8.0.1) rendered file has no audio at all.
When importing AE comp with audio to Premiere CC 2014 imported track doesn't have audio.
Problem is somewhere in dynamic link.
How can we export, for example to H.264, from AE if Media Encoder have problems with Dynamic Link?

Hi Dmitri,
In AE project I have JPG sequence footage and sequence of ten MP3 audio tracks. I have created WAV file from those ten tracks and tried it in AE instead of MP3 files, but result was same - no audio in file, rendered from AME.

Media Encoder 2014 - Dynamic link Premiere/AE - refresh problem

Hello,
I'm working on a edit with AE compositions into Premiere linked by the dynamic link. When i change something in AE it's updated in my Premiere timeline as expected.
Now i want to export my edit to Media Encoder. But sometimes the export doesn't show the last change in AE !
The only way i found to get this AE change in the Media Encoder is to quit Media Encoder and send again my edit.
Is there a easier solution ?

Kevin, the link work different whether you send from AE or load the comp into AME. ie you can see the full path to the original comp when you load direct to AE.
Ideally for the items loaded direct into AME there needs to be a right click "reload updates from last saved AE file". Now that would be expected behavior

Media Encoder CC 2014 using cached versions of Precomps in AE and Nested Sequences in Premiere?

I'm seeing this weird thing where Media Encoder is using older versions of certain assets when exporting a Premiere Pro CC 2014 sequence. I'm seeing issues with nested sequences...Media Encoder uses an old version of a linked AE comp or it doesn't render a certain video track. With linked AE comps...I'm seeing Media Encoder use an earlier version of a precomp within the main comp.
When I look at the video in the Export Settings dialogue in Media Encoder, the old version of the AE comp shows .
If I look at the Export Settings dialogue in Premiere, it's up to date and looks right.
Anyone dealing with this or found a workaround? Thanks!
Calvin

I don't think I'd call this issue expected behavior...at best it's anticipated behavior that's going wrong. The only reason I wouldn't call it expected behavior is because what I'm seeing is AME reverting to a cached state on a FRESH LOAD of a sequence to render directly from Premiere. Basically, AME isn't open...sequence looks fine in PPro...load into AME via PPro export...look at export settings dialog in AME and note that the sequence is the old/cached version. So, it's not like the export was already in AME and THEN I made changes in PPro. It appears AME might be incorrectly identifying the newly imported sequence for export as an older, cached version.
However, I didn't get a chance to test your original solution so I'll try that the next time I see it happen. I also fixed the issue by clearing out the media cache and databases. NOT an elegant solution at all and TOTAL overkill...but it did work.
Thanks for the links!

How to uninstall Media Encoder CC in Mac OS (after Media Encoder CC 2014 is installed)

Hi,
I would like to uninstall Media Encoder CC as I now have Media Encoder CC 2014 installed.
It is nearly 2GB and I need the space.
There isn't an uninstall shortcut as there is for most of the other CC apps?
I could try dragging it all to the trash but have read that adobe apps should be uninstalled with an uninstaller?
Thanks,
Alan.

Thanks, but which applications (and versions) do use it?
And once they are removed how do I uninstall it as an uninstaller is not listed here as shown in the link you sent.
(https://helpx.adobe.com/creative-cloud/help/install-apps.html#Uninstall apps)
Open Finder and go to /Applications/Utilities/Adobe Installers
Double-click an Adobe product to uninstall
Follow on-screen instructions

Premiere, After Effects, Speedgrade, Media Encoder and... the dynamic link

My feeback after working with the dynamic link these days. Basic project. Editing, color correction, animated titles.
I'm using a 3.5Ghz iMac 24GB Ram and a GTX 780 4GB. (2014 versions & last updates).
Rendering the timeline in Premiere is sometimes extremly slow (with AE comps). Need to quit and reload the project to get a good speed.
Too long delay of refresh for the AE compositions inside Premiere (with the dynamic link). Need to go in AE then back to Premiere to get the refresh.
When i export to media encoder i need sometimes to save then send it 2 or 3 times to get the last edits in the export.
Even worse with the AE compositions. If i change something in AE then export from Premiere i need to quit and reload Media Encoder to get the last changes.
Really fast export from Premiere to Speedgrade and from Speedgrade to Premiere.
But !!! Lumetri fx is not compatible with AE. And Speedgrade doesn't support BlackMagic but only this nVidia Sdi thing.
And why we could not export h264 from AE anymore ???
Quiet disappointing :-(

Using Premiere Pro CC 2014.0.1 (build 21) and Media Encoder 2014.0.1 (build 8.0.1.48) on OS X 10.8.5
If I Export a video from Premiere, I can continue using Premiere, but if I Queue an export, returning to Premiere produces the beach ball of death. If I give it time, the beach ball goes away and the arrow returns, but trying to click anywhere in Premiere simply returns the beach ball. There is nothing to be done but Force Quit Premiere. I can leave Premiere and run any other application, but if I leave to execute the Media Encoder queue, I cannot return to Premiere and use Premiere. I can visit Media Encoder (call it to the foreground) and return to Premiere after the queue is done.
My current workaround is to use Export from Premiere and not use Queue from Premiere.

Adobe Media Encoder CC renders do not reflect changes to Dynamically Linked After Effects Comps

When rendering a Premiere timeline with a dynamically linked After Effects composition, Adobe Media Encoder will sometimes use an older version of the linked composition (even after I have saved changes in the After Effects comp).
For example, if I correct a spelling mistake on some text in After Effects, save the composition, and then add the sequence to the render queue in Premiere, the final output from media encoder still has the old spelling.
If I do a straight export from Premiere instead of adding to render queue, the output is always correct. I've noticed this problem on several different Windows 8.1 systems.
All versions of the software are up to date as of today.
Why is this? Is it something to do with the disk cache in After Effects? Does media encoder have it's own cache that I need to clear?

Hi, I've been having this same issue. Here are some additional things I've noticed about it:
Changes are reflected properly when played back on timeline in Pr CC 2014.
Happens regardless if the dynamic link file was rendered or not, thus deleting the render files does not fix the issue.
The issue can persist through saving, closing, and reopening both AE and Pr.
I'm using OSX 10.9.4, so this is not just a PC issue.
Other than manually watching for every change to be reflected in the render, there is no way to know a problem has occurred. Needless to say this can be incredibly costly.
Please address this quickly, it's completely unacceptable that what we render out could be a different version from what we see on the timeline.
PS Some additional things I will be testing:
Does the issue persist through closing all CC apps, including Media Encoder.
Does rendering directly out of Pr, i.e. not using Media Encoder, fix the issue.

PP 2014.1 - Broken link to Media Encoder

Similar Messages

Maybe you are looking for