On 4/21/2016 9:13 AM, Hendrik Leppkes wrote:
> One developer from Libav is working on defining side-data for this
> spherical data. If you want to push this forward I suggest you join
> those efforts.
> ie. this patch for mov: https://patches.libav.org/patch/60300/ (part
> of a longer series)
Yes,
On Thu, Apr 21, 2016 at 10:10 AM, wm4 wrote:
> On Wed, 20 Apr 2016 19:46:05 -0700
> Neil Birkbeck wrote:
>
>> If you use "spherical-video" and put it in the stream's metadata, it
>> will more naturally agree with location in stream-level tag in mkv:
>> https://github.com/google/spatial-media/blob
On Wed, 20 Apr 2016 19:46:05 -0700
Neil Birkbeck wrote:
> If you use "spherical-video" and put it in the stream's metadata, it
> will more naturally agree with location in stream-level tag in mkv:
> https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md
(Replying to both
That makes sense. I’ve attached a revised patch which will store a
“spherical-video” tag in stream metadata, assuming we have a stream (moov level
uuid atoms shouldn’t have spherical metadata according to the RFC).
This is my first time submitting an ffmpeg patch, so please clue me in if I’m
o
If you use "spherical-video" and put it in the stream's metadata, it
will more naturally agree with location in stream-level tag in mkv:
https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md
On Wed, Apr 20, 2016 at 6:24 PM, Colin McFadden wrote:
> ---
> libavformat/mov.
