similar to: oggpcm2 sample rate

Hi, I'd support the view of freezing the main header, since it helps in actually getting some implementation happening and it seems fully agreed on by everyone. FAIK, Zen has already started an implementation and if you, Conrad, implement, too, there is enough code to do validation. What do you expect now to make it an "officially frozen" specification? Publish it on the main

Hi, I also think that outside of the extra headers, OggPCM2 is ready to be implemented. I suggest we make the main part (no extra headers) "officiel" now. We could always add stuff later on by bumping the minor number if really needed. If we go this way, I also suggest we rename it to OggPCM just to make sure it doesn't get confusing with the original OggPCM. Does anyone see a good

Greetings, I am building a data collection system that will ultimately have 28 channels and multi-rates up to 2 M/sec. I need some sort of lossless format framing and header system to transfer the data to a desktop PC over USB. Rather than reinvent, I looked around to see what others are using and for existing tools for testing. Surprisingly, I found few general purpose data formats that can

This is getting very dangerous. We cannot take our flamewar to outside mailing lists without making a complete fool of ourselves. Arc, would you please refrain from doing so in future and rather come to an internal agreement beforehand? Arc, there are a few things you have missed: The discussion on OggPCM2 was friendly and constructive and there were no flame wars and the spec got much further

On Tue, Nov 15, 2005 at 03:10:22AM +1100, Erik de Castro Lopo wrote: > That spec is being superceded by: > > http://wiki.xiph.org/index.php/OggPCM2 The project has been forked, not superceded. Work on OggPCM is continuing, the team working on OggPCM2 is free to submit their own draft but some are not welcome to continue work on OggPCM due to their recent social conduct. I'm

Oggz 0.9.8 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media over HTTP by any web server that supports CGI. liboggz is a C library providing a simple programming interface for reading and writing Ogg

Oggz 0.9.8 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media over HTTP by any web server that supports CGI. liboggz is a C library providing a simple programming interface for reading and writing Ogg

Hi all, The remaining issue to be decided for the OggPCM2 spec is the support of chunked vs interleaved data. Just so that everyone understands what we are talking about, consider a stereo file that gets stored as an OggPCM file. Within an OggPCM packet, the audio samples for the left and right channels can be stored as interleaved where the samples would be: l0, r0, l1, r1, ..... lN, rN

> One obvious thing that seems to be lacking is the granulepos mapping. As > suggested in Ogg documentation, for audio a simple sampling frame number > ought to suffice, but I think the convention should still be spelled > out. I was under the (maybe wrong) impression that the Ogg spec already covered everything that's needed for granulepos. If that's not the case, please

Oggz 0.9.7 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-comment, oggz-scan, oggz-sort and oggz-validate. liboggz is a C library providing a simple programming interface for reading and writing Ogg files and streams. Ogg is an interleaving data container developed by Monty at Xiph.Org, originally to support the

Oggz 0.9.7 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-comment, oggz-scan, oggz-sort and oggz-validate. liboggz is a C library providing a simple programming interface for reading and writing Ogg files and streams. Ogg is an interleaving data container developed by Monty at Xiph.Org, originally to support the

Hi, I'm wondering if the Dirac granulepos parsing in liboggz and display in the oggz tools is currently correct, as I'd like to do a release of these soon. A couple of days ago David Schleef mentioned there were some problems. David, is that currently true (ie. since David Flynn's recent updates to support Dirac), and if so could you please explain what the problems are, or point me

Package: liboggz Version: 0.9.0 Status: Severity: normal [Keep CC if you reply, I'm nt in this list] After porting the package to Cygwin, some binaries do not have accompnying manual pages. ... .inst/usr/share/man/man1/oggzdump.1.gz .inst/usr/share/man/man1/oggzdiff.1.gz .inst/usr/share/man/man1/oggzmerge.1.gz .inst/usr/share/man/man1/oggzrip.1.gz .inst/usr/include .inst/usr/include/oggz

(second try at sending this) --- This is getting very dangerous. We cannot take our flamewar to outside mailing lists without making a complete fool of ourselves. Arc, would you please refrain from doing so in future and rather come to an internal agreement beforehand? Arc, there are a few things you have missed: The discussion on OggPCM2 was friendly and constructive and there were no flame

Hi! I found what liboggz can't read comments for logical bitstreams with OggPCM content, because of in oggz_auto_read_comments () function from oggz_auto.c case entry for OGGZ_CONTENT_PCM is missing. Steps to represent: 1. Generate simple ogg file with content of type OGGZ_CONTENT_PCM and some comments in comments (second) header. 2. Try to read comments via oggz-comments tool.

I made a few updates to OggPCM2 http://wiki.xiph.org/index.php/OggPCM2 reflecting the latest discussions. Could everyone have a look at it and see if they agree. Otherwise, what do you feel should be changed? Anyone wants to speak in support of chunked PCM? For all those that are just tired of this mess like me, please express yourself in the new spec I created: OggPCM3

On Thu, Feb 16, 2006 at 03:25:07PM +0000, Ian Malone wrote: > (You really don't want to know this I'm sure) > I gave this a go this morning on the samples from > <http://wiki.xiph.org/index.php/Metadata>, which > are there mainly for the purpose of breaking things. > They don't validate (which neither surprises nor upsets > me), but I downloaded the oggz source

Hi All, What is the status of the oggpcm project? I'm investigation solutions to the following problem: losslessly encode double-precision mutli-channel timeseries data in a format that is compatible with free (libre) internet streaming technologies and that permits diverse metadata to be encoded with the stream. flac isn't suitable because it only supports integer data, lossy

HI all, John Kkoleszar has asked for the option of storing data. He gave the rational that a) SIMD optimized filters b) Writing filter chains. Conrad Parker supported this say that both Core Audio and Jack operate on multiple single channel buffers. On IRC both Jean-Marc and MikeS argued that if OggPCM supports interleaved, the addition of chunked is hard to justify. My slant on the

HOgg 0.4.1 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the fourth public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on