Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal: Integration with 3D Motion Video Editing Software #39

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Proposal: Integration with 3D Motion Video Editing Software #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions dev-docs/vNext/motion-design-export-rfc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
# RFC: Integration - 3D Motion Video Editing Software

* Authors: Chris Gervang
* Date: October, 2020
* Status: **Draft**

## Overview

This proposal outlines a series of features to enable faster and more effective collaboration between engineering and motion design teams. This can be achieved by exporting video assets and data to sync compositions.

## Problem

Currently motion designers can import videos of visualizations created with vis.gl into 3D composition software, such as AfterEffects or 3DS max, but in doing so the visualization is flattened and all metadata about the motion of the scene is lost. This limits a motion designers ability to advance design tools, and also limits an engineers ability to integrate real data sets in edited videos.

Motion designers currently either recreate a rendition of an engineers data, or spend additional effort with the engineer to polish the appearance in code - either way the result is often prohibitively time consuming, and the work is highly specialized.

## Proposal

Export data from the vis.gl ecosystem in a native format for popular motion design software.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

List a few such formats and add references to documentation?

If (part of) that format is in textual form, perhaps show a snippet to illustrate?

Sketch out some "builder API" that covers the information needed by these formats?


- Production designers save time reusing the existing visualizations instead of recreating them from scratch.
- Engineers save time programming polish into their visualizations.
- Stakeholders are offered greater alignment between their audience and technology since the data can speak for itself.

### Camera Data Export

Export camera FOV, keyframes, and coordinates so that designers can sync camera movements between visualization and composition.

### Null Value Data Export

Export 3d position of invisible anchor points on the ground plane so that designers can position new assets into the visualization.

### Layer Mask Shader Extension

Create a layer mask shader so that designers can place new assets behind visualization layers.

A layer mask shader isolates a layer by recoloring the screen black in all negative space and white in a layer's positive space. This can then be encoded videos for use as a mask.

### Alpha Channel Render Procedure

Create a rendering procedure that cycles through each layer, configuring all but one at a time to be visible, and then renders video of each isolated layer with an alpha color channel.

The PNG Sequence and WEBM formats support alpha channels.