From anaxagramma at gmail.com Thu May 20 08:22:04 2010 From: anaxagramma at gmail.com (Naxa) Date: Thu, 20 May 2010 08:22:04 +0200 Subject: [Matroska-general] Congratulations! Message-ID: Dear all Matroska people out there, I wish to congratulate you for the greatest format, Matroska, that you have developed, the format that we love with all the friends here. I've finally heard about the great news that mark the success of it - at last. This is a happy year for us all! Thank you for creating Matroska and for sharing it with us - the best container format, which also has the most hearth-warming name! Kind regards, Kristof Nacsa From netmonitoring at mail.ru Fri May 21 09:36:15 2010 From: netmonitoring at mail.ru (netmonitoring) Date: Fri, 21 May 2010 11:36:15 +0400 Subject: [Matroska-general] Representation of a Matroksa file [building the right structure for the file in mkv format] Message-ID: Hello, ???????? developers team. I have a question about representation of a Matroksa file. In http://matroska.org/technical/diagram/index.html Matroska diagram shown, that sequency of structures must be: Header, Meta Seek Information, Segment Information, Track, Chapters, Clusters, Cueing, Data, Attachment, Tagging. As shown, the "Meta Seek Information" must going after "Header" and before "Segment Information". Like this sample: movie.mkv { EBML { DocType DocTypeVersion DocTypeReadVersion } Segment { SeekHead Void Info Tracks Cluster Cues } } To make it, i must reserve some space for "Meta Seek Information" before i create "Segment Information" structure, and replace reserved space with "Meta Seek Information" at the end of file. It is not convinient and perspective, because "you do not know how much space you need". Reminds the story about AVI OpenDML container memory reserving for the file size. The question is: is it neccessarily to reserve space and replace it with "Meta Seek Information" structure later or it's possible to put "Meta Seek Information" at the end of "Segment Information" without reserving space? The Matroska file structure will not be distorted? If my file structure is like this: movie.mkv { EBML { DocType DocTypeVersion DocTypeReadVersion } Segment { Info Tracks Cluster Cues SeekHead } } From douglasjordan at hotmail.com Thu May 27 23:30:30 2010 From: douglasjordan at hotmail.com (Douglas Jordan) Date: Thu, 27 May 2010 17:30:30 -0400 Subject: [Matroska-general] splitter not unloading Message-ID: I have loaded 1.10.175.0 but see the same problem I have seen for a while. When loading multiple MOV files in the same process and releasing the graphs the splitter does not release and multiple icons remain in the system tray of the taskbar. This occurs in XP or 7. The splitter is loaded by intelligent connect with CoreAVC or the decoder in Win7 and is not specifically loaded by my code. Is this a know issue or will it be addressed? The CoreAVC is a good product but this problem makes it unusable. Regards, DJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From aelschuring at hotmail.com Mon May 31 19:12:10 2010 From: aelschuring at hotmail.com (Arno Schuring) Date: Mon, 31 May 2010 19:12:10 +0200 Subject: [Matroska-general] rationale for tagging system? Message-ID: <4C03EDEA.7040205@hotmail.com> Hello list, Can anyone point me to a more in-depth explanation about how the mkv tagging system should be used? I've already read both the specification at matroska.org and reviewed the dtd files (from mkvtoolnix - which do not match the specs btw), but so far I have no information about its purpose or intended use. Some of the more easy questions: - what's the significance of an EditionEntry (or what type of file would have more than one EditionEntry)? - regarding the Tag element: it acts as both a container element and a divisive element, but what's the BCP regarding its use? Should I give each SimpleTag element its own Tag element, can I just use one Tag element for all SimpleTags? What's the semantic difference between the two? - regarding TagLanguage/ChapterLanguage: I don't understand why there is a separate element to indicate the language of a (non-nested) element. The official recommendation is to use the xml:lang attribute for such cases, what's the reason for not following it? In my current blissful state, I feel like I'm stabbing in the dark here. Is there any recommendation (or an overview) of how an application (= player software) treats (or preferably, "should treat") any of the information contained in Matroska tags? I'd be grateful for any pointers, Regards, Arno Schuring From slhomme at matroska.org Mon May 31 22:57:23 2010 From: slhomme at matroska.org (Steve Lhomme) Date: Mon, 31 May 2010 22:57:23 +0200 Subject: [Matroska-general] rationale for tagging system? In-Reply-To: <4C03EDEA.7040205@hotmail.com> References: <4C03EDEA.7040205@hotmail.com> Message-ID: On Mon, May 31, 2010 at 7:12 PM, Arno Schuring wrote: > Hello list, > > Can anyone point me to a more in-depth explanation about how the mkv > tagging system should be used? I've already read both the specification > at matroska.org and reviewed the dtd files (from mkvtoolnix - which do > not match the specs btw), but so far I have no information about its > purpose or intended use. > > Some of the more easy questions: > > - what's the significance of an EditionEntry (or what type of file would > have more than one EditionEntry)? > Editions are about Chapter editions. It's used to hide parts of a Segment or even order it differently. The tags could differ between the editions (the title for example). > - regarding the Tag element: it acts as both a container element and a > divisive element, but what's the BCP regarding its use? Should I give > each SimpleTag element its own Tag element, can I just use one Tag > element for all SimpleTags? What's the semantic difference between the two? > Did you check these examples ? They are good starting points for best practice: http://www.matroska.org/technical/specs/tagging/example-audio.html http://www.matroska.org/technical/specs/tagging/example-video.html > - regarding TagLanguage/ChapterLanguage: I don't understand why there is > a separate element to indicate the language of a (non-nested) element. > The official recommendation is to use the xml:lang attribute for such > cases, what's the reason for not following it? > EBML and Matroska are not XML based, they resemble it, but have some differences (or shortcomings). Each tag value should be matched with a TagLanguage value. There can be more than one variant of the same Tag in different languages in the same file. Same thing for Chapters. > In my current blissful state, I feel like I'm stabbing in the dark here. > Is there any recommendation (or an overview) of how an application (= > player software) treats (or preferably, "should treat") any of the > information contained in Matroska tags? > > > I'd be grateful for any pointers, > I hope those above help. -------------- next part -------------- An HTML attachment was scrubbed... URL: