Re: Extension to Matroska for use in a real life bike trainer film

--===============8462105868650517617==
Content-Type: multipart/alternative; boundary="000000000000ea577f05dbd8ba6d"

--000000000000ea577f05dbd8ba6d
Content-Type: text/plain; charset="UTF-8"

On Tue, 5 Apr 2022 at 02:14, Brendan Ball via Matroska-general <
[email protected]> wrote:

>
> Things to consider:
> - GPS data for a video would just be another track in the media that is
> synced with the video
> - GPS data for the complete video should be easy to extract since it's
> very common to show a preview profile of the elevation of the entire video
> to help the user choose a video. Other metadata like complete distance is
> also either extracted or calculated before playing the video
> - Other data might be captured as well from sensors like a gyroscope,
> accelerometer etc.
> - The Matroska file should be playable as is by existing video players
> (even though it contains extra data like GPS). This makes it easy to use
> the same files for previewing the video without needing a special app. This
> might be especially beneficial when having a collection of videos on a
> website to preview before downloading.
>
>
> Brendan Ball
>
>
In the more general case, a track that includes GPS position and time of
the camera and azimuth/elevation would be useful. The information could be
used to combine different camera views of an event in a static or moving
montage.
-- 
Jeremy

--000000000000ea577f05dbd8ba6d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Tue, 5 Apr 2022 at 02:14, Brendan Ball=
 via Matroska-general &lt;<a href=3D"mailto:[email protected]=
.org">[email protected]</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><br></div><d=
iv>Things to consider:</div><div>- GPS data for a video would just be anoth=
er track in the media that is synced with the video</div><div>- GPS data fo=
r the complete video should be easy to extract since it&#39;s very common t=
o show a preview profile of the elevation of the entire video to help the u=
ser choose a video. Other metadata like complete distance is also either ex=
tracted or calculated before playing the video</div><div>- Other data might=
 be captured as well from sensors like a gyroscope, accelerometer etc.</div=
><div>- The Matroska file should be playable as is by existing video player=
s (even though it contains extra data like GPS). This makes it easy to use =
the same files for previewing the video without needing a special app. This=
 might be especially beneficial when having a collection of videos on a web=
site to preview before downloading.</div><div><br></div><div><br></div><div=
>Brendan Ball</div></div><br></blockquote><div><br></div><p>In the more gen=
eral case, a track that includes GPS position and
      time of the camera and azimuth/elevation would be useful. The
      information could be used to combine different camera views of an
      event in a static or moving montage.<br>
    </p>
    <div class=3D"gmail-moz-signature">-- <br></div><div><span style=3D"col=
or:darkslategray;font-size:large">Jeremy</span>=C2=A0</div></div></div>

--000000000000ea577f05dbd8ba6d--

--===============8462105868650517617==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Matroska-general mailing list
[email protected]
https://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-general
Read Matroska-General on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.general

--===============8462105868650517617==--