Giter Club home page Giter Club logo

aftereffects_spatial_media_plugins's Introduction


  Gorialis

Hello! I like making tangible software.


My name is Devon and this is where you can view my public projects.

I work in a handful of different disciplines, but my recent work tends mostly towards reverse engineering, DevOps, and graphical/UX design.

Provided nothing goes wrong, this README will dynamically regenerate using GitHub Actions every hour! (it last updated at 10:00 UTC, 2024-05-20)

World clock

JLPT words of the hour

JLPT N1

および

and, as well as

JLPT N2

こうぶつ

mineral

JLPT N3

したがって

therefore, consequently

JLPT N4

しなもの

goods

JLPT N5

さとう

sugar

Other things

🌕 Lunar phase

The moon is approximately 44.21% through its phase (Full Moon).

🖼 Fractal of the hour
⏲ Year percentage bar
2024 [███████▁▁▁▁▁▁▁▁▁▁▁▁▁] 38.37%

aftereffects_spatial_media_plugins's People

Contributors

gorialis avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

aftereffects_spatial_media_plugins's Issues

Use Lanczos or a similar algorithm to anti-alias patches without recalculating perspective

As the title says.

At the moment, it is possible to antialias footage patches by creating a larger composition and scaling it down into a smaller one using bilinear or bicubic interpolation, but this is a slow method of doing this. For 2x SSA antialiasing, this requires 4x the perspective calculations, as well as the scaling method and extra composition as well.

Using Lanczos when sampling pixels from the "Source Layer" footage would remove hard edges and null the need for this kind of workaround in compositions where fine fidelity matters.

I cannot load binaries to AE 17.0

Log from file "Plugin Loading.log":

Loading C:\Program Files\Adobe\Adobe After Effects 2020\Support Files\Plug-ins\equirectangular_to_equirectangular.aex
Loading from disk...
PF_Cmd_GLOBAL_SETUP returned error -1610153865.
No loaders recognized this plugin, so the plugin is set to Ignore.

fatal error U1033: syntax error : '-Dperspective_to_perspective_EXPORTS' unexpected

-DAFTEREFFECTS_SDK="<path to March 2021 version>/AfterEffectsSDK"
-DAFTEREFFECTS_LOCATION="C:/Program Files/Adobe/Adobe After Effects 2021"
Scanning dependencies of target perspective_to_perspective_resources
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29915 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

PiPL.r
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29915 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

PiPL.rrc
CMakeFiles\perspective_to_perspective.dir\flags.make(6) : fatal error U1033: syntax error : '-Dperspective_to_perspective_EXPORTS' unexpected
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29910\bin\HostX64\x64\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.28.29910\bin\HostX64\x64\nmake.exe"' : return code '0x2'
Stop.
[  0%] Built target perspective_to_perspective_resources

Which I believe is this line:

COMMAND cl.exe /I "${AFTEREFFECTS_SDK}/Examples/Headers" /EP "${CMAKE_SOURCE_DIR}/perspective_to_equirectangular/PiPL.r" > "${CMAKE_SOURCE_DIR}/perspective_to_equirectangular/PiPL.rr"

https://github.com/Gorialis/aftereffects_spatial_media_plugins/blob/2495315/CMakeLists.txt#L69

EDIT: In the meantime I cheated with https://github.com/pavelliavonau/cmakeconverter to create a CMakeLists.txt from the MSVC solution. Then I edited it to remove all the hardcoded paths and duplicate branches. Surprisingly it works.

Fix frame overscan & transparency patching

At the moment, the edge of equirectangular patches sometimes get transparent "hems" on "Preserve layer" mode due to the Lanczos blending at the edge of the frame.

Specifically, due to the old method not blending at all, the "Preserve layer" mode only shows the original layer when the alpha channel is 0 (completely transparent), and won't blend on top of the original layer at any other value. This has gone unnoticed because when the alpha channel is 255 (fully opaque), no blending is required.

The correct solution to this would be to always blend with the source layer when "Preserve layer" is on, as this would also fix blending issues in cases where the source content is itself translucent.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.