Load & Play Lottie animated files (JSON & .lottie)

Hi there ;)

Was wondering. Wouldn't it be cool if Vuo could load & play Lottie files ? (lottiefiles.com)

Seem to be quite a big way nowadays for light animations as opposed to the old GIF images.
Would allow to use some animations made with Adobe After Effects in Vuo and export into apps, screensavers, vids & plugins (new tools coming out to create them as well).

I guess it would be good to load and play both .json & .lottie file formats (dotlottie.io).

In what kind of renderer would / could we render them in to though ? Layers ? Or will we have to wait for SVG import to be added into Vuo since these are vector based ?

Also hope the license would be compatible with Vuo.

Thanks

Some links :
https://github.com/LottieFiles
https://github.com/airbnb/lottie
https://github.com/mnkd/LottiePlayer (a simple macOS Lottie player)

Some example : Liquid Blobby Loader (converted to a mp4 below to be able to embed here in the text since iFrames are not supported)

Component: 

Tags: 

WebAssembly / Compile Compositions for Browsers

Open for better suggestions, but I think Vuo can hold it's own in the generative community. And future proof Vuo for Web3. Is WebAssembly a viable option to compile compositions for browsers?

Here's an example of openGL and C++ compiled through WebAssembly:

https://ipfs.io/ipfs/QmVjh4xBTTrSKKPsNAgUYw9j2s4nACh5cYjAV4miB8UyQg/

Component: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●●● — Many months of work

Potential: 

●●● — Opens Vuo to a new audience

Knob for Faster Expressive Results

jersmi's picture

This is about supporting creativity and expression. Vuo lacks tools for working quickly -- it can be difficult to set something up and see expressive results right now. In one sense this is a UX/UI issue -- modular software is particularly difficult when it can cover so many use cases -- how do you decide what to highlight?

Scenario: say I have a creative thread I wish to follow, a sketch, a seed. Like having a sketchbook close by, I want to be able to set up and explore possibilities ASAP.

To this end I wish I could load a simple 'knob' -- a Share Value in the form of a knob UI element, could just be a float value normalized to 0 to 1 range. Then I could quickly refine it with Calculate to set up an expressive range.

This idea applies to a majority of Vuo scenarios, here's a simple example: say I want to play with thin line widths on a 3D Object, say a Make Grid Lines Object -- I wish I could load a knob and quickly type an expression into Calculate, knob * knob * .01, connect and go. Two things get in the way -- event flow and parameter ranges on modules. The more parameters a module has, the more difficult it is to use as an expressive object. A tool like this would help.

Features (in order of importance):

  • Don't need to consider event flow because it will just work.
  • The knob could simultaneously be published (for creating comps to load in other software, VDMX, CoGe, Resolume) and still be used in a running Vuo comp.
  • The knob could be assigned to an external source via either OSC or MIDI.

Some think all parameters in modular software should be normalized. In lieu of this, it would be great to have some solution that considers these basics. Pretty sure these concepts have been hashed out a kajillion times by now from various directions....

Component: 

Export Vuo projects as OFX plugins

OFX is an open standard for compositing software. BlackMagic Design's DaVinci grading/compositing software now has a couple of pretty advanced non-linear editing modes, and there's a free version of DaVinci that anybody can use.

I used Adobe Premier Pro and After Effects and would really like to be able to export plugins for those Apps too, but perhaps OXF is more accessible to the community given free version of DaVinci Studio. For plugin developers I expect that the Adobe plugin market is bigger than OFX so I'll FR that to and see what gets more votes.

here's a page of info about comping/editing tools that support the OFX plugin API. And OFX plugins and more.

Component: 

Apply image filter protocols to movies (rotoscoping)

Implement "Image Filter" protocol for movies and "Filtered Movie" export option. Would pass the audio track through unchanged.
For the Community Edition, the same 1280x1280 image-size restriction as the current movie export feature would apply.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●●○ — Could expand community

Pages

Subscribe to RSS - Vuo Interoperation