search for: vorbose

Just out of curiosity, did someone write a tool that dumps in a human-readable form the audio content of a vorbis file ? -- Giuliano. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject

Hi, When I built libogg2 for testing the new vorbose utility, gcc 2.96 stumbled over a portion from stream.c that mixes variable declarations with statements. The patch below fixes this. -Carsten. Index: stream.c =================================================================== RCS file: /usr/local/cvsroot/ogg/src/Attic/stream.c,v retrieving revi...

Can I fix the checksum with a hex editor? Sent from my iPhone On Jun 25, 2009, at 3:23 PM, Monty Montgomery <monty at xiph.org> wrote: > Confirmed--- the checksum on the second page (the comment page where > the album art was added) is incorrect. Vorbis players are not allowed > to decode any stream in which one of the setup headers is corrupt, and > a bad checksum counts as

Vorbose -v reports the following for the beginning of the file: INFO page: Capture pattern OggS, format version 0 Flags: first page of logical stream Granule position: 0x0000000000000000 Stream serialno : 0x490f5cff Sequence number : 0 Ch...

...id vorbis stream (1) Warning: Could not decode vorbis header packet 2 - invalid vorbis stream (1) Warning: Could not decode vorbis header packet 2 - invalid vorbis stream (1) Warning: Could not decode vorbis header packet 2 - invalid vorbis stream (1) So it seems the codebooks are corrupt; perhaps vorbose can shed some light on what's wrong here. Monty, could you try running hogg-reconstructed.ogg through vorbose? Another clue is that the file hogg-reconstructed.ogg is 113 bytes shorter than unfixed_corrupted.ogg. Comparing the page offsets of the two files $ hogg pagedump unfixed_corrupted.og...

Monty Montgomery wrote, on 6/25/2009 1:10 PM: > Vorbose -v reports the following for the beginning of the file: > > INFO page: Capture pattern OggS, format version 0 > Flags: first page of logical stream > > Granule position: 0x0000000000000000 > Stream serialno : 0x490f5cff >...

Is there a utility available that will dump the codebook information for a given Vorbis file. This would be useful to compare my own implementation against as a benchmark. Actually, a utility that would dump all of the Vorbis metadata would be quite useful as a development tool.

We are working on OggVorbis encoder. In the porting effort we are trying to convert it to fixed point code (both 32 and 24 bit fixed point). Now the issue is how we do the testing. What should be the criteria for our testing. Does anybody has any idea how compliance testing (i.e. some objective tests) is done at encoder side? What is the criteria of testing at the encoder side? If anybody

hi , As i had stated before , i am having problems with ov_open() which returns -132 error. i have uploaded the project file in rar format. it is a vc++ project file, can someone please check out the error and tell me where i am going wrong... http://sr2.mytempdir.com/89384 Thanks and regards sam

Do anybody know, from where I can get an Ogg Vorbis File, which uses floor0 coding. I know that the current encoder doesn't use floor0. Anyway, to be fully compliant with the Vorbis Specification the decoder still must be able to decode floor0. I am working on a Vorbis port to a DSP. I want to go sure, that if the need of floor0 decoding will again occur, this also will work properly.

Conrad Parker wrote, on 6/20/2009 10:24 PM: >> How about another approach -- is there a tool that will verify the page >> checksums? oggz-validate doesn't seem to do this. If the page checksums >> are okay, then doesn't that suggest the streams are also recoverable? > If the page checksums are bad then the page will get rejected by > libogg, and oggz-validate

...ious Issues of Ogg Traffic 1 Status Updates 1.1 Monty Monty was busy finishing up the optimizations of the Neuros firmware, which he delivered to Digital Innovations for integration into their official firmware. More details on the Neuros are below. Monty also found time to code Vorbose, which is a verbose Vorbis stream analyzer. Now that the Neuros work is finally out of the way, Monty's plans for the immediate future include a Vorbis 1.0.1 bugfix release, which is planned for early September, and resuming work on the OggFile API. 1.2 Jean-Marc Valin Jean-...