Friday, July 03, 2020


NOTE: I am still updating this page.

How to publish VR180


VR180 Creator

Introducing VR180 Creator, simplifying the video editing process

VR180 cameras allow creators to shoot three-dimensional, immersive photos and videos using affordable cameras that are small enough to fit in your pocket.

And to make it even easier for you to create and edit high quality VR videos, we’re launching VR180 Creator on Mac and Linux. This desktop tool lets anyone edit VR180 footage with existing VR video tools.

VR180 Creator currently offers two features for VR videos. “Convert for Publishing” takes raw fisheye footage from VR180 cameras like the Lenovo Mirage Camera and converts it into a standardized equirect projection. This can be edited with the video editing software creators already use, like Adobe Premiere and Final Cut Pro. “Prepare for Publishing” re-injects the VR180 metadata after editing so that the footage is viewable on YouTube or Google Photos in 2D or VR.

Convert your VR180 footage into a standardized format so you can edit it with leading editing tools like Adobe Premiere and then re-inject the appropriate metadata for publishing.   DOWNLOAD HERE

VR180 Creator release notes

Google’s VR180 Creator Tool Makes it Easier to Edit VR Video on Linux

DNxHR was listed as an output option instead of mpeg4. This is something I wasn't familiar with.
I have yet to try it on anything.

Avid DNxHR, which stands for "Digital Nonlinear Extensible High Resolution", is a lossy UHDTV post-production codec



Kandao qoocam

VR180 Video Format

1. Introduction

VR180 cameras are a new category of VR camera that use two wide angle cameras to capture the world as you see it with point and shoot simplicity. This document describes the video format output by these devices. The choice considers the following aspects:

FOV: VR180 cameras capture sub-360 FOV rather than full 360. It is important to retain the original pixel density of the camera sensors in order to provide high pixel density for VR viewing.
Projection: Different versions of VR180 cameras may have different lens and different camera projections. As such the file format should be camera-independent.
Motion: The cameras can often be non-stationary due to unintentional shakes or intentional motion, for example, handheld capture of events or people. To avoid motion sickness, camera motion metadata should be saved for stabilized playback.
Playback: The file format should be friendly enough for local playback so that manufacturers can easily build their apps. Android and iOS should have an easy way to play the raw video.
VR180 videos contain two types of metadata to jointly define the projection from video frames to their partial viewports within a spherical coordinate system.

A global static projection that defines the mapping from the pixels to local spherical coordinate systems, typically to only a sub-180 FOV part. The Spherical Metadata V2 Spec is adopted here to encode this global metadata. (See details in section 2).
A dynamic orientation stream that defines the rotation between the local coordinate system of each frame and the world coordinate system. A new Camera Motion Metadata track is created for encoding such per-frame metadata. (See section 3).

Spherical Video V2 RFC

This document describes a revised open metadata scheme by which MP4 (ISOBMFF) and WebM (Matroska) multimedia containers may accommodate spherical videos. Comments are welcome by discussing on the Spatial Media Google group or by filing an issue on GitHub.

Metadata Format
Spherical video metadata is stored in a new box, sv3d, defined in this RFC, in an MP4 (ISOBMFF) container. The metadata is applicable to individual video tracks in the container. Since many spherical videos are also stereoscopic, this RFC also defines an additional optional box, st3d, to specify metadata specific to stereoscopic rendering.

As the V2 specification stores its metadata in a different location, it is possible for a file to contain both the V1 and V2 metadata. If both V1 and V2 metadata are contained they should contain semantically equivalent information, with V2 taking priority when they differ.

Stereoscopic 3D Video Box (st3d)

No comments: