search for: oggskeleton

hi, vorbis-tahseen is the branch I'm using for my soc project regarding OggSkeleton support in libvorbisfile. After adding an initial support of OggSkeleton, I attempted to also add support for handling vorbis stream in a theora file. As it now seemed a bit more involved work, I've stopped working on that for the moment. The present version of vorbis-tahseen only supports OggS...

I have made a patch to support libvorbis to allow parsing a vorbis bitstream in an ogg bitstream containing additional bitstreams. The patch is attached in the given ticket http://trac.xiph.org/ticket/925#preview from my experiment it successfully decodes a normal vorbis file and a vorbis+skeleton+cmml file. thanks in advance for reviewing it. -------------- next part -------------- An HTML

...uping in chunks of eight, but that works. The problem then becomes where to put the metadata. The metadata could still go in the (multiple) FLAC streams, as you suggested, but should more logically be up in the Ogg container. Currently, the only place available in Ogg is as name-value pairs in an OggSkeleton stream. After OggSkeleton has become well supported then metadata can go into its own stream, but we are not there yet. There does not seem to be a neat solution. Regards, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web: http://members.tripod.com/martin_leese/

...eview the changeset here: >> >> http://trac.annodex.net/changeset/3801 > > I'll test this shortly. great, thanks > My only initial concern is about the definition > of granule_rate. My intention is to add some guidance to the oggdirac > mapping spec on how to apply oggskeleton. This raises the slight > problem for me in that i don't find the specification of skeleton > particularly rigorous[1]. > > Actually, i don't even know what the definition of granule_rate applies > to when a granule_shift is present[2]. Is it the whole number or the higher...

2008/11/15 David Flynn <davidf+nntp at woaf.net>: > On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: >> It seems oggz chop, merge and sort will need some attention to deal >> with the Dirac granulepos and dependency ordering, so let's leave them >> for the next release. > > ok. -- may be worth having them 'warn' if they are operating

...t; >> I'll test this shortly. Ok, i've tested muxing some audio and video together and that works fine. woo. >> My only initial concern is about the definition >> of granule_rate. My intention is to add some guidance to the oggdirac >> mapping spec on how to apply oggskeleton. This raises the slight >> problem for me in that i don't find the specification of skeleton >> particularly rigorous[1]. >> >> Actually, i don't even know what the definition of granule_rate applies >> to when a granule_shift is present[2]. Is it the whole n...

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo

...about codecs. As I understand it, the Ogg format is inherently multi-track, but does not mandate any particular multi-track protocol. > > If you are creating multitrack Ogg files, they should contain a > skeleton track to identify the different contained tracks. > http://wiki.xiph.org/OggSkeleton ALingA is a multitrack format (http://www.ihear.com/dtds/ALingA/0.1/ALingA.dtd) which has a skeleton track (what I call the co-ordinating stream), but one that is very specific, and based on the notion of a Manifold. It is implemented in the separate library libalinga, subclassing libogg++ to do th...

...gt; It includes the fixes for handling skeleton on big-endian hosts. I > think it would be a good idea to use this version everywhere else that > that skeleton.c file is used, ie. in vorbisfile, ffmpeg2theora, > oggenc, speexenc/speexdec as listed at: > > http://trac.annodex.net/wiki/OggSkeleton > > As far as I understand, that file is simply duplicated in each source > tree. It would be great if you could update it in each. > > cheers, > > Conrad. > > > ------------------------------ > > Message: 4 > Date: Sat, 02 Feb 2008 13:44:34 +0530 > From: j...

Hi everybody, I posted here about two years ago about the initial release. This is a release that fixes many bugs, and has enhancements that make it possible to support a multi-stream format, ALingA, which I will mention briefly later. It also supports a PCM format, Neuro, both as part of the multi-stream codec, and stand-alone. libogg++ is a C++ library implementing Ogg. It is designed to be

...-09 at 00:12 +1000, Silvia Pfeiffer wrote: > On Sat, Jun 6, 2009 at 6:23 AM, ter<et at ihear.com> wrote: > >> If you are creating multitrack Ogg files, they should contain a > >> skeleton track to identify the different contained tracks. > >> http://wiki.xiph.org/OggSkeleton > > ALingA is a multitrack format > > (http://www.ihear.com/dtds/ALingA/0.1/ALingA.dtd) which has a skeleton > > track (what I call the co-ordinating stream), but one that is very > > specific, and based on the notion of a Manifold. It is implemented in > > the separat...

...trunk/src/tools/skeleton.c It includes the fixes for handling skeleton on big-endian hosts. I think it would be a good idea to use this version everywhere else that that skeleton.c file is used, ie. in vorbisfile, ffmpeg2theora, oggenc, speexenc/speexdec as listed at: http://trac.annodex.net/wiki/OggSkeleton As far as I understand, that file is simply duplicated in each source tree. It would be great if you could update it in each. cheers, Conrad.

...f Code student application deadline extended to March 26th (26th/27th midnight UTC) there is still enough time to prepare a good application and there are some XiphQT-related ideas. Speex and FLAC encoding support would be good to have (podcasts?, high-quality content?) but other functionality like OggSkeleton or CMML support could be useful, as well. I guess, any Xiph.Org SoC project will have positive impact on XiphQT this way or another, so if you still hesitate for some reasons - don't! The Xiph.Org SoC project ideas can be found at: http://wiki.xiph.org/Summer_of_Code Regards, Arek

...trunk/src/tools/skeleton.c It includes the fixes for handling skeleton on big-endian hosts. I think it would be a good idea to use this version everywhere else that that skeleton.c file is used, ie. in vorbisfile, ffmpeg2theora, oggenc, speexenc/speexdec as listed at: http://trac.annodex.net/wiki/OggSkeleton As far as I understand, that file is simply duplicated in each source tree. It would be great if you could update it in each. cheers, Conrad.

...leshift, it seems to > be working. You can review the changeset here: > > http://trac.annodex.net/changeset/3801 I'll test this shortly. My only initial concern is about the definition of granule_rate. My intention is to add some guidance to the oggdirac mapping spec on how to apply oggskeleton. This raises the slight problem for me in that i don't find the specification of skeleton particularly rigorous[1]. Actually, i don't even know what the definition of granule_rate applies to when a granule_shift is present[2]. Is it the whole number or the higher word. If we assume it i...

Hi Elaine, I flipped through some of the code but wasn't really about to determine this: Do you also support Skeleton in libogg++ ? If you are creating multitrack Ogg files, they should contain a skeleton track to identify the different contained tracks. http://wiki.xiph.org/OggSkeleton And if the files aren't audio or video files, you should then use the extension .ogx http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions . You may already be doing all of this - I just wasn't able to verify, therefore the question. Cheers, Silvia. On Fri, Jun 5, 2009 at 6:57 AM...

...it, the > Ogg format is inherently multi-track, but does not mandate any > particular multi-track protocol. > >> >> If you are creating multitrack Ogg files, they should contain a >> skeleton track to identify the different contained tracks. >> http://wiki.xiph.org/OggSkeleton > ALingA is a multitrack format > (http://www.ihear.com/dtds/ALingA/0.1/ALingA.dtd) which has a skeleton > track (what I call the co-ordinating stream), but one that is very > specific, and based on the notion of a Manifold. It is implemented in > the separate library libalinga, subc...

On Sun, 24 Aug 2014, Silvia Pfeiffer wrote: > It's well possible there are bugs. I don't know when the code was last > updated. The last commit was in May, so it looks like it is being worked on... I've gone ahead and raised three bugs, one for the offset, one for more helpful error messaged, and one for subsequent streams of a given type needing different roles+names.

...f Code student application deadline extended to March 26th (26th/27th midnight UTC) there is still enough time to prepare a good application and there are some XiphQT-related ideas. Speex and FLAC encoding support would be good to have (podcasts?, high-quality content?) but other functionality like OggSkeleton or CMML support could be useful, as well. I guess, any Xiph.Org SoC project will have positive impact on XiphQT this way or another, so if you still hesitate for some reasons - don't! The Xiph.Org SoC project ideas can be found at: http://wiki.xiph.org/Summer_of_Code Regards, Arek