Mikko Haapoja

@Halishen sorry the version of the [after-effects](https://www.npmjs.com/package/after-effects) module that this module uses did not support Windows. If you'd like to create a PR introducing the newest version of [after-effects](https://www.npmjs.com/package/after-effects) I'd...

This maybe due to paths of transitions having the exact same duration. This is a hard issue to solve or to know the best route of attack.

Unfortunately I did not have % translations in mind when writing this module. I think in order to implement this feature you'd require to watch the dom element and get...

This may in fact be in regards to a footage/video layer having a filter/effect applied to it. To double check I've added a video layer to the test AE file...

As far as I know it is not possible. I would Google running After Effects headlessly but I can't imagine that being an option.

@adri I am all for React Native support. Actually I think an older version of `react-f1` would have worked perfectly with React Native where only props were modified. For performance...

I know the `after-effects` module has now been open sourced. Might not be a bad thing to contribute to the module and ensure it's transpiled before it being published.

Honestly I've never thought about this. It's an interesting idea.

I likely won't be working on this. I currently don't even have an adobe subscription. (too much $)

Sorry I do not. This module also currently works via Apple Script.