Just upgraded to Mavericks and patched AE to work.
But cannot drag Comps from the project window to the AME Queue.
I can add via the + but it's very slow to load.
Dragging comps from the Project panel in AE CC to AME's Queue panel is successful for me on Mac OS X 10.9.
Make sure that your AE project has been saved at least once. If the project is unsaved, there is no reference on disk for AME to use. There is a bug that AME does not produce an error message in this case, so it might appear as if nothing has happened.
We have fixed this behavior in the soon-to-be-released After Effects CC (12.1) update, so that you are not required to save the project first. AE will create a temp file for an unsaved project and send it to AME. More detail on the 12.1 update is here:
Does the Add To Adobe Media Encoder Queue command (in the Composition menu) work?
I would check the permissions on the folder the project file is in, and make sure that write access is allowed for Everyone. AE will write temp files into the project directory (into a folder named [project name]_AME) when you send a comp to AME. There have been reports that folder permissions are set incorrectly after upgrading to 10.9, preventing AE from writing or modifying files that worked fine in the previous OS.
Other miscellaneous troubleshooting off the top of my head:
Ok, I finally worked it out.
A few folders the root I had an '&' in a folder name
Now I know these are allowed in OSX, I don't know about windows... or perhaps it's a bug?
I know it's not great practice to use those sort of characters anyway.
Thanks for leading me to it!
Glad to hear you've resolved it. Sorry about the hiccup there.
I reproduced the problem with having an ampersand (&) character in the file path, and filed the bug. It also applies to the less-than (<) character. I wasn't able to dig up any others. It's a very curious bug because it's only those characters, and only applies when the comp is dragged from AE to AME; adding the comp to the AME queue by other methods (the Add To AME Queue command in AE, or choosing the project from AME) does not result in this bug. In any case, good find, and thanks!