similar to: handling multitrack Ogg

It sounds like you're on the right track. There are 2 places I would start looking - DVD's, and Quicktime. Quicktime is mature and the container is the basis for mp4 and 3gp. Can you find a way to transcode to Ogg maintaining the track information? As someone who makes videos, its beyond me to translate audio to other languages, but I would be interested in doing commentary tracks.

On Tue, Feb 2, 2010 at 1:47 PM, Silvia Pfeiffer <silviapfeiffer1 at gmail.com>wrote: > On Wed, Feb 3, 2010 at 5:07 AM, Frank Barchard <fbarchard at google.com> > wrote: > > It sounds like you're on the right track. There are 2 places I would > start > > looking - DVD's, and Quicktime. > > Quicktime is mature and the container is the basis for mp4

On Wed, Feb 3, 2010 at 11:21 AM, Chris Double <chris.double at double.co.nz> wrote: > Excerpts from Frank Barchard's message of Wed Feb 03 13:11:15 +1300 2010: >> >> Yes, and its good to learn from DVD's too. DVD is a subpart of MPEG: http://www.mpucoder.com/DVD/vobov.html, http://dvd.sourceforge.net/dvdinfo/dvdmpeg.html . Uses the same functionality for tracks, iiuc.

What would the creation of a AVI or MPG with 2 audio tracks tell me that I don't know yet? I can just use normal ffmpeg for that - ffmpegx is just a GUI transcoding tool based on ffmpeg and the latest ffmpegx release is more than 2 years old. Anyway, I did look at the AVI spec after this email (http://msdn.microsoft.com/en-us/library/dd318183%28VS.85%29.aspx) and found that while each track

DVD has the UI and the low level meta information. The API you propose is the glue between the 2. It also has practical content. Could a DVD like UI be implemented on top of your API? It may need more exploration features? Could your API be used on DVD content asis? Do your APIs have 1:1 relationship with meta information in the files? multiple languages requires language codes match up. Your

On Mac the ffmpegx tool supports 2 audio tracks. Maybe worth checking out? http://www.ffmpegx.com/index.html - Creates AVI or MPG files with two audio tracks. - *Supports subtitles* in VobSub, SubRip, MicroDVD, SubViewer, Sami, VPlayer, RT, SSA, AQTitle, JACOsub and MPsubt formats On Tue, Feb 2, 2010 at 5:40 PM, Silvia Pfeiffer <silvia at silvia-pfeiffer.de>wrote: > On Wed,

Hi all, Discussions about a need for an extension to Skeleton to cater for multi-track media files has been going on for a while. In a recent thread here, in discussions on IRC, and at FOMS between Jan, Ralph, Viktor and I, we discussed some fields. Viktor and I continued that discussion to make more specific recommendations on what fields to add. We now have a wiki page at

Daniel, these are all good ideas and worth progressing. However, it may be better not to merge too many goals in one format (MPEG-7 did that and ended up as a big mess). So, I suggest to start by structuring the types of things you want - then finding out which parts belong where into existing formats such as vorbis comment, Skeleton and CMML, and only then start to develop a new format. For

What I've gotten out of this discussion so far: 1) we need to introduce a means in which to do captions; this could be done through adding a "caption" element to CMML, or in another time-continuous annotation format; so far I am not sure which would be the better way 2) we need a XML annotation format for audio - in particular for music - that is more structured than vorbiscomment

> Right. This was, in fact, one of the roles of "chaining" where you'd > mark such changed components with a chain boundary, at which such > things are explicitly allowed to change. The drawbacks are the > overhead of resending all the setup data for configurable codecs like > vorbis and theora, and the semantic conflict between 'chain boundary > flags an edit

On Thu, 25 Aug 2011 20:01:11 +1000 Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote: > Hi BCXA, > > CMML is deprecated. You should use KATE instead. > > Cheers, > Silvia. ok i admit this statement came as a surprise for me. cmml is about metadate/annotations, how can it be replaced by KATE ( which is mainly about subtitles as far as i can see? startx

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

(Sorry, Sylvia, about the duplicate, hit the wrong reply button.) On Fri, 2009-06-05 at 08:07 +1000, Silvia Pfeiffer wrote: > Hi Elaine, > > I flipped through some of the code but wasn't really about to > determine this: Do you also support Skeleton in libogg++ ? Hi, Silvia. I studied your multi-track work when I was working on ALingA. It was a valuable guide. No, libogg++ tries

Hi Daniel,, > I really have to ask you: Have you even tried to describe media using the > excising solutions? I don't mean adding subtitles and editing stuff. I mean > really say what a Ogg file contins. There is no working wheels for this. > Vorbis comments--used in FLAC too--can describe content with a very limited > field names (and badly enforced standards). I have and I

Interesting discussion happening over at whatwg! S. ---------- Forwarded message ---------- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com> Date: Oct 8, 2007 10:14 AM Subject: Re: [whatwg] Video, Closed Captions, and Audio Description Tracks To: Chris Double <chris.double@double.co.nz> Cc: "whatwg@whatwg.org List" <whatwg@whatwg.org> Hi Chris, this is a very good

On 15-Feb-08, at 10:11 PM, Conrad Parker wrote: >> Lang: <locale> > > generally I think we should go with existing HTTP and email headers > where possible, eg. Content-Language 'k >> Description: <string> > > I kinda feel that this kind of human-readable metadata better belongs > in CMML; the skeleton tells you where to go (for each locale), the

Well, actually most OGM files do have a subtitle track, often in multiple langauges. Also, re 2. Keyframe seeking in OGM is generally a bit rough because ogm files can contain almost any codec as the video track, usually xvid or divx. re 1. As a general rule you shouldn't be trying to make any more ogm files :) So chances are the ogg muxer is not accepting the connection, because it

We have new drafts of CMML 4.0 as a text codec and ROE as an xml stream abstract, subsuming the authoring support in CMML 3.1 and earlier. Another thing we talked about at LCA is a how to specify relationships between the various streams in Ogg so that a server, muxer or player can make intelligent decisions about the contained tracks. The general idea is to use the (http-style) Message