similar to: [xiph-commits] r15288 - in trunk/ogg: debian doc

On 25-Jun-08, at 3:23 AM, ivo at svn.xiph.org wrote: > * correctness: make oggdec output help text on stdout instead of > stderr Hmm. Doesn't oggdec output the decompressed audio to stdout? IIRC the help goes to stderr to avoid clobbering that. If 'corretness' is the windows issue, could it be compile-time switched? -r

On 11-Feb-08, at 12:37 PM, ivo@svn.xiph.org wrote: > Author: ivo > Date: 2008-02-11 12:37:13 -0800 (Mon, 11 Feb 2008) > New Revision: 14479 > > Patch by Christian Weisgerber to fix possible problems in 64bit > systems with "int shuffle" and "int repeat". I'm confused. How does making these long help? -r

I don't agree with the s/Ogg Vorbis/Vorbis/. vorbiscomment does edit Ogg Vorbis files, not Vorbis streams in any other encapsulation. -r On Mon, Nov 19, 2007 at 07:01:43AM -0800, ivo@svn.xiph.org wrote: > Author: ivo > Date: 2007-11-19 07:01:43 -0800 (Mon, 19 Nov 2007) > New Revision: 14188 > > Modified: > trunk/vorbis-tools/vorbiscomment/vorbiscomment.1 > Log:

On 5/24/08, Conrad Parker <conrad at metadecks.org> wrote: > The magic is not always char[8] -- it's an arbitrary number of > characters, and as far as I know there is no official limit. I was under the impression that 8 was the limit. Thus the extra white space JM adds on Speex and CELT magics. I may be wrong, though. > So it's 7 for Vorbis and Theora, 5 for FLAC So

On 5/24/08, Ralph Giles <giles at xiph.org> wrote: > It's supposed to be finalized though there many be some granulepos > issues still in current implementations. I don't expect the BBCD\0 > magic to change. Great. > OggMNG defines the following magics: > > char[8]: "\211PNG\r\n\032\n" png > char[8]: "\212MNG\r\n\032\n" mng > char[8]:

On 11/14/08, David Flynn <davidf+nntp at woaf.net> wrote: > Correct; there is no metadata handling capability in the current > mapping spec. I'd suggest at some point to look into separate stream solution for metadata, perhaps M3F [1]. -Ivo [1] http://wiki.xiph.org/index.php/M3F

Hi all, I am trying to set up the codecs table in the wiki and we have played a bit with Dirac to find out what existing tools write into the header. The Schroedinger implementation by Fluendo uses (or used to use) "KW-DIRAC" as the identifier in the Ogg header. "BBCD" is the identifier of each of the Dirac data packages. More recently, I read that the Dirac Sequence header

On Sun, May 25, 2008 at 2:53 AM, Ralph Giles <giles at xiph.org> wrote: > On 24-May-08, at 9:26 AM, Ivo Emanuel Gon?alves wrote: > > And there's OggY4M which uses char[9]: "YUV4MPEG2" but that's in no > way finalized. I was unable to find any documentation on this on the Web. Would you have a link to the mapping? BTW, I have now finalized a first version of

If you want another opinion, the table currently lists the magic strings in the format they're given in their respective specifications, so it may be less confusing to have the mix of escape styles. If anyone needs to check and you've converted them, they'll have to convert back. And if octal<->hex was a trivial operation for most people, we wouldn't be having this

>From some random dude on Slashdot [ http://yro.slashdot.org/comments.pl?sid=224420&cid=18177356 ]: "Second, whether AVI is better or worse than Ogg is debatable. Any who has ever written an Ogg (de)muxer curses it's name frequently. It's extremely codec-specific, and the format is rather loosely defined, with no consistent standard way to do much of anything.... AVI has

Hi, it seems Ogg keeps track of a packet's size at the byte level, rather than at the bit level (eg, if I encode a packet with just one bit, decode will think there are 8 bits available). Am I right ? Not that it's a particularly important issue, since remaining bits will probably be initialized, but I noticed this while adding some calls to oggpack_look1 at the end of my decode routines

On 10/21/07, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > But I agree that we need to get skeleton support into mainstream > encoders, not just the decoders. That's what I meant, especially now that Skeleton is a (SHOULD) requirement for video/ogg and audio/ogg. Lots of encoders will need to change. ffmpeg2theora, flac (the application), VLC... And CMML... I believe I

On Thu, Feb 28, 2008 at 1:53 AM, Ralph Giles <giles@xiph.org> wrote: > On 27-Feb-08, at 10:44 PM, Conrad Parker wrote: > > > Sure: I'm thinking about Ogg demuxers and seeking implementations. > > These need to know the framerate in order to be able to interpret the > > granulepos in terms of time. If they did not have to extract that from > > the

On 1/10/08, Ralph Giles <giles@xiph.org> wrote: > There have been a couple of > proposals for this; the most popular one right now is to use the > <description> or <caption> tags inside an CMML stream. > > We would like to get this standardized, so let us know how it goes. I think we are likely to settle for CMML for everything text in Ogg. Of course,

Hi Folks, What is the proper way to embed text stream into the Ogg stream? I need to have text information (lyrics as example) recorded together with the audio. Is there a standard mechanism for that? What is the right way to do it? With best regards, Boian Mitov -------------------------------------------------------------------- Mitov Software http://www.mitov.com

On 12/04/2008, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On 4/11/08, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > > > uuencode ^_^ > > > > Hmm... > > Yes! A Vorbis Comment tag called ART or ALBUMART with a Base64 string > would do the trick and it would not choke existing players. No, vorbiscomments are meant to be

On 11-Feb-08, at 6:00 PM, Erik de Castro Lopo wrote: > Personally, I think that change should be reverted and another > cleaner solution found to address that problem. Agreed, although it doesn't make that much differece; the code is broken either way. Ivo, if you don't want to do the alternate patch, you might ask the original contributor? -r

>From some random dude on Slashdot [ http://yro.slashdot.org/comments.pl?sid=224420&cid=18177356 ]: "Second, whether AVI is better or worse than Ogg is debatable. Any who has ever written an Ogg (de)muxer curses it's name frequently. It's extremely codec-specific, and the format is rather loosely defined, with no consistent standard way to do much of anything.... AVI has

I agree - we should use only hex or octal, but not mixed. Cheers, Silvia. On Sat, May 31, 2008 at 2:20 AM, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > I received the following comment regarding the table: > >> The table contains a mix of octal and hexadecimal 'escape sequences' >> for non-printable / non-ASCII octets. >> I strongly suggest to only

FYI: I included video/ogg into liboggplay, too. For audio/ogg, another application would probably make more sense. Cheers, Silvia. On Sun, Aug 17, 2008 at 11:35 PM, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On 7/22/08, Nils Dagsson Moskopp > <nils-dagsson-moskopp at dieweltistgarnichtso.net> wrote: >> (...) the registered mime type application/ogg > >