Copy link to clipboard
Copied
I keep getting this error message (amecommand Initilization error 1), when I try to render a video in Photoshop & Photoshop Beta, both the newest versions.
I uninstalled and reinstalled Photoshop, Bridge & Media Encoder, but still doing the same thing. I restarted laptop (macbook pro), restarted the apps, uninistalled the apps then did a laptop restart before reinstalling, and still.. no luck.
I tried to open Bridge to render through there, but Bridge keeps force quittiing before it even fully loads the app, so that's of no use. Older versions of Photoshop and Bridge did not work either and produced the same out come (photoshop still gives error message when renderinig video and Bridge force quits when app is is loading up)
SOS
Copy link to clipboard
Copied
Are you able to launch Adobe Media Encounter on its own? Are you able to export video from it?
Copy link to clipboard
Copied
i trried but i cant even get to the render settings to open it in encoder. I did trry dropping the PSD file into Media Encoder to see if maybe it could do it but it didn't work, it only rendered the first frame of the video sequence (I have the PSD set up to be frame by frame timeline
Copy link to clipboard
Copied
but to answer your question directly, Media Encoder launches fully and works when I import video files into it to render. I haven't tried doing a render from something like AfterEffects because the video im making is a stop motion and it's jst quicker in Photoshop.
Bt also, I cant tell if it's a Photoshop issue, Bridge issue or both, because the fact that I can't get Bridge to fully launch is strange
Copy link to clipboard
Copied
When you work in Photoshop, it is just sending the file over the Media Encoder. The error you are seeing is telling us that Media Encoder is no responding the way Photoshop expects. If you can't work with the same file in Media Encoder itself, then it tells us the Media Encoder is more closely tied to the issue. It would be a good idea to post a message in the Media Encoder forums. Also, we have separate forums for Bridge as well, to deal with what is happening there. It is possible that both issues are related and fixing it for one will fix it both.
Copy link to clipboard
Copied
Exporting the PSD thru the media encoder rendered the animation fine. However, when trying to do it thru Photoshop again, the amecommand failed. The crash reporter revealed this:
Application Specific Information:
abort() called
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.
Thoughts?
Copy link to clipboard
Copied
That sounds like there is a security error when trying to send the file from one application to another. I can only find two references with regards to Adobe applications: 1. Acrobat Reader and the security certificates it uses, and 2. Premiere Pro and a third-party plugin. I can't find any referenece to anyone else encountering it with Photoshop or Media Encoder. Most of the time this error seems to occur when developing apps and the security components installed on the system for doing coding.
So that brings up the questions: are you doing coding on this machine? and do you have any third-party content installed (plugins or otherwise) within Photoshop and/or Media Encoder?
Copy link to clipboard
Copied
neither, I dont even have Premiere on my laptop. Been relying on screen recording now because i still cant get any video rendering from photoshop *insert eye twitch*
Copy link to clipboard
Copied
Hi @paige.corkery Thank you for reaching out! We're sorry to hear about the problem you're facing. Could you please share more details like your system Information? A screen recording of the whole issue would be really helpful as well. You can share via Google Drive, WeTransfer, or another public file-sharing platform with your response.
While we wait, you can try these steps below and see if they fix anything.
1) Hardware Acceleration Conflicts:
a) Photoshop: Photoshop > Preferences > Performance... Try unchecking "Use Graphics Processor."
2)Check for Corrupted AME Presets or Cache:
a) Open Adobe Media Encoder (if it can open independently, though Photoshop is calling it via amecommand).
b) Go to Media Encoder > Preferences > Media.
c) Under "Media Cache Files," note the location and click "Clean." Also, check the "Media Cache Database."
3) Manually Clear AME Folders (if AME won't open or for a deeper clean):
a) Close all Adobe applications.
b) In Finder, Go > Go to Folder... and navigate to the following locations. Delete the contents of these folders (or move them to a backup location):
Let us know how this goes.
Cheers!
Find more inspiration, events, and resources on the new Adobe Community
Explore Now