Ron wrote:
> Which is why I'm suggesting that one option if you want still
> pictures, is to define a generic Ogg mapping for them - which could
> then be used with any other format that also has an Ogg mapping,
> including this one.

I have no objection to adding the pictures in a separate multiplexed
stream; in fact that is my proposal (3).  That is the only one that I
did not specify with enough detail to create interoperable
implementations, because it is a much larger change to the way that
opus-tools currently attaches pictures, and I therefore did not expect
that approach to be favored.  However if there is consensus that that
is the way to go, I can propose something more concrete, and in that
case the only change that I think is needed in the Ogg Opus draft is
to allow these streams in an "Ogg Opus file".  In particular, when
attached pictures are not specifically mentioned, no requirements or
recommendations (such as recommended file extension) should depend on
whether attached pictures are present.

> There may be better ways to do that, but any optimal way should not
> be Opus specific, it should be reusable for any Ogg stream.

Oh I agree completely that this should ideally not be codec-specific.
Not only attached pictures but also tags such as TITLE and ARTIST,
channel mapping, output gain, and loudness/gain required for
normalization would ideally all be maintained by the container and not
be specific to any codec.  The reason that I proposed adding attached
pictures in the codec-specific stream is because Ogg does not provide
metadata at the container level, and all of the metadata I mentioned
is currently being stored on a codec-specific page of the
codec-specific stream.  I would love to see all of this moved out of
the codec-specific stream and into an extensible codec-independent
format elsewhere in the file, and the codec-specific stream reduced to
only what is truly codec-specific, but that is not the direction that
was taken for other metadata.

 - Mark

_______________________________________________
codec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/codec

Reply via email to