I don't know when it happened but sending from Premiere to AME now works

for me again. Wish I knew what happened so I could share but I literally

didn't do anything except try again.

Maybe it had something to do with updating to Mavericks 10.9.4 although

that doesn't make sense to me. But that's the only that's changed since the

last time I tried.

Unfortunately, if that is the solution (and I doubt it), that doesn't help

our Windows-using friends.

On Thu, Jul 24, 2014 at 11:35 PM, Mark Mapes <forums_noreply@adobe.com>

Broken again as of the 2014.0.1 update...

On Fri, Jul 25, 2014 at 9:05 AM, Nicholas Seaney <

In another thread on the same general problem, a user reported that clearing his prefs resolved the issue: Re: Problems with "queue" to Media Encoder, Post #8.

What's up with Adobe? All of a sudden, PP CS6 no longer works with AME. I Queue from Pr and AME launches with file in Queue. I press Render button, and it takes several minutes before anything shows up in a the Encoding tab. When it does, I get an endless "Connecting to Dynamic Link server..." message, before finally, after several minutes, it fails. Log states that it can't read the source file. I suspect this is a Dynamic Link issue, since the source file is exactly where the log says it should be. I've noticed recently that Dynamic Link hung up also when trying to send a clip to Ae to round trip effects back to Pr. I just ended up doing the work in Ae and imported it manually into Pr. So much for the heralded 'interoperability'. You spend a couple grand on CS6 Master Collection to have all the tools, and many of them have all kinds of issues. Au, for example, crashes 75% of the time when I open it. Reopen it again and it works fine. Ae often continually gives me 'program has stopped working' dialog with an option to quit, and many times it is talking about one of many instances it has launched in the background, and when I say 'quit', the main program I see just keeps on working. And now, out of the blue, Pr / AME queuing stopped working. It has worked, but that is the beauty of Adobe products: "life is like a box of chocolates, you never know what you're gonna get", or if it is going to work when you have a deadline to meet. So, has anybody solved this issue? Seems it's been going on for some time now. BTW, I'm on CS6 on an HP Z820. Win 7 Ultimate.

And WTF with that stupid-*** sheep sound when there is an error. Who thought THAT was a good idea. Probably the same idiot who wrote the interface between Pr and AME. I'm so fed up with crappy SW from Adobe. Wish there were other options. And they keep telling me I should RENT this crap?

Hi GrizzlyAK,

Sorry for your issues. This is a post about Premiere Pro CC and AME CC. You may want to start your own CS6 post.

Thanks,

Kevin

Thanks Kevin. I just assumed that ongoing support for CS6 ended with the rollout of 'Creative Cloud'. I don't hold out much hope for getting a resolution any time soon. I suspect that if I wait long enough, it'll start working again, like it did less than a month ago. Keep us guessing...

"Edited by moderator to remove expletive and offensive personal attack. Rant all you like, but try to be respectful to the people behind the programs."

should have read...

"Ignore your consumers all you like, but try to be respectful to the people who actually pay your salaries."

GrizzlyAK wrote:

 

I just assumed that ongoing support for CS6 ended with the rollout of 'Creative Cloud'.

Two things:

1. This is a user-to-user, not an official support channel.
2. If you look around a little bit, you'll find threads going back way earlier than CS6. In fact there's a sub-forum specific to CS4 & earlier.

Yeah, Mark, I get it. Adobe doesn't really support their end-users (directly), they leave it up to us to debug their software for them. As a 25+ year SW engineer, I've seen plenty about how such 'user-to-user' forums work, with company employees lurking about, trying to glean something from reports by users trying to get their SW to work, pleas for help from the company, so they can maybe go and fix it. but hey, this is a 'user-to-user' forum, so we'll have none of that. I worked via email with the lead for Au over a year ago, outside the forum, and there is still no solution to the problem. The program crashes nearly every time with first launch after a reboot. Clearly, Adobe spends far too few resources on actually testing their products before they release them. Adobe is not alone in this practice, unfortunately. And why would they be, when you have thousands of users to do the testing for you and you can just sit back and watch the 'forums' to gather your debug input. Nice.

I've resolved my problem thanks to post by @gagneh on this forum. It turned out to be the NVidia nView Desktop Manager applet found in the Control Panel. It was enabled, and I believe it has been enabled for a long time. I don't know if something in a recent update broke things, but as soon as I disabled the Desktop Manager, my dynamic link started working again in all aspects. Give it a try. Good luck.

Just wanted to chime in and say this is a REGULAR occurrence over here with me. Costs us a lot of time. Late-2013 MacBook Pro running Yosemite and latest version of Premiere Pro CC 2014. This also happened on 10.9 (Mavericks).

Hi,

I'm sending the comps from After effects to AME. I've found a solution to "STAT QUEUE not working".  In the preferences box of AME, I checked the "Start queue automatically when idle for ...Minutes". And the queue starts. Till Adobe finds a solution, it's a workaround. But each time, I close the AME, it's hanging and I force quit.      

MAc Osx 10.8.5

adobe cc updated to recent versions

Hi... Go to preferences, try checking the box and put one to start in 10 seconds, it worked for me

Hey Mark,

My native import setting and checkbox has disappeared. I have tried uninstalling and reinstalling everything as well as all the fixes above. Where would it have gone, and how can I get it back? Thanks.

Blessings,

Kelley

Please post a screenshot of AME's About box.

The Import Sequences Natively option wasn't added until 7.1.