From slhomme at matroska.org  Wed Sep  1 13:36:02 2010
From: slhomme at matroska.org (Steve Lhomme)
Date: Wed, 1 Sep 2010 13:36:02 +0200
Subject: [Matroska-general] TrackOperation
Message-ID: <AANLkTinVtbQARr5+JbpRO2fWkV4L9Mx95d932m17ugwH@mail.gmail.com>

Hello everyone,

Following the recent discussions on 3D video in Matroska and the inclusion
of S_DVBSUB, I combined the 2 issues into a single solution. There is now a
new element in Matroska TrackOperation that allows defining a track as the
"sum" of other tracks.

http://www.matroska.org/technical/specs/index.html#TrackOperation

This important that the TrackEnabled element is repected in the future,
especially for S_DVBSUB as individual parts are not meant to be used
separately.

Here are basic examples of how the TrackOperation works:

3D video track #4 is the sum of planes from
 left   = track #1
 right  = track #2
 backgroundd = track #3

Track #4
TrackOperation
 Track3DCombine
   Track3DLeft = #1
   Track3DRight = #2
   Track3DBackground = #3



DVBSub track 4 is the sum of blocks from
 particular = track 1 (disabled)
 common     = track 2 (disabled)

Track #4
TrackOperation
 TrackJoinBlocks
   TrackJoin = #1
   TrackJoin = #2

DVBSub track 5 is the sum of blocks from
 particular = track 3 (disabled)
 common     = track 2 (disabled)

Track #5
TrackOperation
 TrackJoinBlocks
   TrackJoin = #3
   TrackJoin = #2

It's almost set in stone now. But comments are welcome.

The next phase will be to produce files using these elements and have
something to play them back...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.matroska.org/pipermail/matroska-general/attachments/20100901/d1e0d5af/attachment.html>

From slhomme at matroska.org  Sun Sep  5 10:38:14 2010
From: slhomme at matroska.org (Steve Lhomme)
Date: Sun, 5 Sep 2010 10:38:14 +0200
Subject: [Matroska-general] TrackOperation
In-Reply-To: <AANLkTinVtbQARr5+JbpRO2fWkV4L9Mx95d932m17ugwH@mail.gmail.com>
References: <AANLkTinVtbQARr5+JbpRO2fWkV4L9Mx95d932m17ugwH@mail.gmail.com>
Message-ID: <AANLkTimvCjmh-ta+36xB9kYfCsQn4ktm0L=+ymtJTh3b@mail.gmail.com>

I modified the system for the 3D tracks so that each track can be defined
with more details. Here is how it works:

3D video track #4 is the sum of planes from
 left   = track #1
 right  = track #2
 backgroundd = track #3

Track #4
TrackOperation
 Track3DCombine
   TrackPlane
     TrackPlaneUID = #1
     TrackPlaneType = 0 (left eye)
   TrackPlane
     TrackPlaneUID = #2
     TrackPlaneType = 1 (right eye)
   TrackPlane
     TrackPlaneUID = #3
     TrackPlaneType = 3 (background eye)

I will also add some more information on how it's all supposed to work in
the Specification Notes page.
http://www.matroska.org/technical/specs/notes.html

On Wed, Sep 1, 2010 at 1:36 PM, Steve Lhomme <slhomme at matroska.org> wrote:

> Hello everyone,
>
> Following the recent discussions on 3D video in Matroska and the inclusion
> of S_DVBSUB, I combined the 2 issues into a single solution. There is now a
> new element in Matroska TrackOperation that allows defining a track as the
> "sum" of other tracks.
>
> http://www.matroska.org/technical/specs/index.html#TrackOperation
>
> This important that the TrackEnabled element is repected in the future,
> especially for S_DVBSUB as individual parts are not meant to be used
> separately.
>
> Here are basic examples of how the TrackOperation works:
>
> 3D video track #4 is the sum of planes from
>  left   = track #1
>  right  = track #2
>  backgroundd = track #3
>
> Track #4
> TrackOperation
>  Track3DCombine
>    Track3DLeft = #1
>    Track3DRight = #2
>    Track3DBackground = #3
>
>
>
> DVBSub track 4 is the sum of blocks from
>  particular = track 1 (disabled)
>  common     = track 2 (disabled)
>
> Track #4
> TrackOperation
>  TrackJoinBlocks
>    TrackJoin = #1
>    TrackJoin = #2
>
> DVBSub track 5 is the sum of blocks from
>  particular = track 3 (disabled)
>  common     = track 2 (disabled)
>
> Track #5
> TrackOperation
>  TrackJoinBlocks
>    TrackJoin = #3
>    TrackJoin = #2
>
> It's almost set in stone now. But comments are welcome.
>
> The next phase will be to produce files using these elements and have
> something to play them back...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.matroska.org/pipermail/matroska-general/attachments/20100905/2d79f435/attachment.html>

From slhomme at matroska.org  Sun Sep 19 17:05:36 2010
From: slhomme at matroska.org (Steve Lhomme)
Date: Sun, 19 Sep 2010 17:05:36 +0200
Subject: [Matroska-general] Misc News
Message-ID: <AANLkTikx_U-FG=gcLOiHwwAPsGQ9+bm80fhCu=CJRmZZ@mail.gmail.com>

It has been a while since I emailed about what's going on in the
Matroska world. I often put news [1] on the website and even more
often on Twitter [2]. But there may be some of view who don't follow
these channels. So here is a recap of what has happened lately.

The biggest and most important news of all is the suite of 8 test
files [3] we produced. They are made to test players for correct
Matroska compatibility/scalability. Make sure you test your devices
and let us know what you find out. It's also important to let the
manufacturer know where there are issues so they can fix them early in
the product life (deprecated products won't be updated and you will
not be able to play some perfectly valid Matroska files in the
future).

We now have 3D support in the specs via the StereoMode and
TrackOperation fields. Check in the specifications [4] and the
specification notes [5] for more details. There is currently no tools
to make such files, or even play them. We are going to work on that in
the coming weeks, especially in mkvmerge and VLC.

There is a new guideline for cover art [6] in Matroska as there has
been many demands and everyone seems to be doing their own
incompatible thing. So now people have some rules of what they should
expect from Matroska files and how they should put their cover arts in
there.

The order guideline [7] changed a little recently by recommending to
put attachments at the front of the file. This is better for fonts and
for cover art.

mkclean and mkvalidator are progressing nicely and produce good
result. But they are still consider beta tools until they reach
version 1.0.0. This is the same with libebml2/libmatroska2 on which
these tools are based. The internal code can change here and there
before it's considered stable. It shouldn't be long anymore as there
aren't so many things left to be done for version 1.0.0.

[1] http://www.matroska.org/news/index.html
[2] http://twitter.com/MatroskaOrg
[3] http://www.matroska.org/downloads/test_w1.html
[4] http://www.matroska.org/technical/specs/index.html
[5] http://www.matroska.org/technical/specs/notes.html#3D
[6] http://www.matroska.org/technical/cover_art/index.html
[7] http://www.matroska.org/technical/order/index.html