ffmpeg added a highly generalized metadata framework and automagically takes care of these mappings and limitations. I'm fairly certain that ffmpeg will just use what is supported during muxing rather than throw an error. I found a really good reference.
http://multimedia.cx/eggs/supplying-ffmpeg-with-metadata/
Here is the task http://opencast.jira.com/browse/MH-7745


On 5/18/11 10:42 AM, Christopher Brooks wrote:
Just an FYI that metadata in the container means container specific
work.  E.g. some containers can't store metadata, so this should be
considered (if you send a "title" to a wav file what happens?).

Also, I know how to do this with ffmpeg, but with gstreamer it is
likely different.  So if things could be failure friendly that's great,
otherwise Nejc you might want to watch this work to see how it impacts
the gstreamer encoder.

Sounds great though,

Chris


On Wed, 18 May 2011
10:20:24 -0700 Adam Hochman<[email protected]>  wrote:

As part of the iTunes Distribution work for 1.3, Matterhorn will need
the ability to add relevant metadata to a media's container.  iTunes
relies on this metadata to accurately display information in its
player, but this feature is relevant beyond iTunes as many players
rely on a container's metadata to accurately display information.

I propose that we add this capability and change the Composer API to
accept media packages and/or specific metadata elements.  I am also
looking for help in this area.  If you're interested in participating
in the iTunes/YouTube Distribution work this would be a great place
to contribute.

Thanks,
Adam
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to