Skip to main content
gabgren
gabgren
Inspiring
January 21, 2019
Answered

Question regarding Importer

  • January 21, 2019
  • 1 reply
  • 346 views

Hi !

I'd like to build an Importer so I can import custom files into After Effects. I'll call this plugin ImporterA

This will allow users to place my custom file as a layer in a comp, and reference this layer from a Layer selector in another plugin of mine, which i'll call PluginB.

I want PluginB to be able to read the data from the imported ImporterA file, so my question is:

When PluginB selects an ImporterA layer, does it:

1- receive the path to the actual file so it can open it and retrive its data, or

2- ImporterA is the one opening the file and passing its content, or part of it, to PluginB ?

Ideally, i'd like if option 2 was possible, but in the end, both would work.

In the case of option 2, does ImporterA reads the file content every frame or it gets "cached" once imported and then just passed along when asked ?

Also, bonus question: I read Adobe is pushing for Premiere SDK when it comes to building Importers, just want to make sure is it best to use AE's AEGP SDK or Premiere SDK Importer in that case ?

Thanks !

Gab

This topic has been closed for replies.
Correct answer shachar carmi

i'm not sure about the premiere importer, so hopefully someone else will

pick up this question, however, here's the importer->effect interaction:

an importer indeed allows a custom file type to be imported into AE, and

placed in a comp.

from here on, there are 2 possible scenarios:

1. importer plug-ins are expected to parse the file (or files) on demand,

and populate an image buffer. (in the case of image/video, not audio of

course)

if the importer indeed does that, then when the footage is placed in a

comp, it becomes visible just like any other image/video and can be read

from your effect like any other layer source.

advantages: AE can cache the result for faster access on other frame

renders. it also expands usability for your custom file type.

2. instead of using your effect's layer selector to read pixels, you only

use it to get the selected layer's ID. with that you can get the layer's

source project item, and from it you can fetch the source file path.

once you have the file path your layer effect can parse the file instead of

the importer plugin.

advantages: allows for the use of "data" files, which have no graphic

interpretation that can be presented as an image buffer. allows for

selective storage of data, instead of having all the file data take up ram

when parsed fully by the importer.

both scenarios are valid. note that you can both parse the file in the

importer AND fetch the path and parse in the effect. it doesn't have to be

the one or the other.

1 reply

S
Community Expert
shachar carmiCommunity ExpertCorrect answer
Community Expert
January 21, 2019

i'm not sure about the premiere importer, so hopefully someone else will

pick up this question, however, here's the importer->effect interaction:

an importer indeed allows a custom file type to be imported into AE, and

placed in a comp.

from here on, there are 2 possible scenarios:

1. importer plug-ins are expected to parse the file (or files) on demand,

and populate an image buffer. (in the case of image/video, not audio of

course)

if the importer indeed does that, then when the footage is placed in a

comp, it becomes visible just like any other image/video and can be read

from your effect like any other layer source.

advantages: AE can cache the result for faster access on other frame

renders. it also expands usability for your custom file type.

2. instead of using your effect's layer selector to read pixels, you only

use it to get the selected layer's ID. with that you can get the layer's

source project item, and from it you can fetch the source file path.

once you have the file path your layer effect can parse the file instead of

the importer plugin.

advantages: allows for the use of "data" files, which have no graphic

interpretation that can be presented as an image buffer. allows for

selective storage of data, instead of having all the file data take up ram

when parsed fully by the importer.

both scenarios are valid. note that you can both parse the file in the

importer AND fetch the path and parse in the effect. it doesn't have to be

the one or the other.

gabgren
gabgrenAuthor
Inspiring
January 21, 2019

Thanks! Very clear

I might give premiere sek a go since they seem to recommend ot over aegp

Gab

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices