Skip to main content
Participating Frequently
December 19, 2019
Question

I/O Error when loading an ExternalObject (dll) in Extendscript

  • December 19, 2019
  • 2 replies
  • 1917 views

I've been experimenting with the ExternalObject feature because I want to integrate a c++ library with my After Effects script. I started with the SampleLib found in the path:

C:\Program Files (x86)\Adobe\Adobe ExtendScript Toolkit CC\SDK\Samples\cpp\build\samplelib

I used VS 2019 to build the solution and got a dll file out of that. Then when I try to load it with:

var lib = new ExternalObject("lib:SampleLib.dll");

 What I get is:

I/O error

I'm not sure what to do at this point. The documentation does not even mention this as a possible error. I've looked everywhere on the internet but I can't seem to find anyone with a similar issue. It seems to work fine for everyone.

 

Any help would be appreciated!

This topic has been closed for replies.

2 replies

Justin Taylor-Hyper Brew
Community Expert
Community Expert
December 20, 2019

Loading custom ExternalObjects are uncharted territory. I've spent a few days down this path with the same issues and haven't had a chance to get back to it. I'd reach out to Bruce https://community.adobe.com/t5/user/viewprofilepage/user-id/7743763 on this.

Participating Frequently
December 21, 2019

Thanks! I will. Is this a common issue? Are there any others who have this IO error? I wonder what could be the cause..

Justin Putney
Known Participant
February 20, 2020

Any luck on this? I'm having a similar issue.

Mylenium
Legend
December 20, 2019

I would assume that it has a lot to do with system security stuff. You know, that thing about DLL loading policies on Win 10 and the usual stuff with protected folders, user permissions and whatnot. Conversely, double-check your ExtendScript settings for network access and other such things that may prevent the sandbox from loading external files.

 

Mylenium

Participating Frequently
December 21, 2019

Hi Mylenium,

Thanks for the suggestions.

For the first assumption: I'm unfamiliar with any "loading policies", and I don't know what protected folders or user permissions have to do with this issue. I did try to change the project configuration from Debug to Release in VS2019 but that didn't work either.

And for the second one: I didn't find any Extendscript settings for this type of thing. I'm quite sure that "network access" has nothing to do with loading dll files.

 

Yahia